feat (protocol): pre testnet release updates #53
Conversation
| blockMaxProposals: 324_000, | ||
| blockRingBufferSize: 360_000, | ||
| maxBlocksToVerify: 16, | ||
| blockMaxGasLimit: 240_000_000, |
There was a problem hiding this comment.
Limit should be 600MGas given a 3 second block time
| maxBlocksToVerify: 16, | ||
| blockMaxGasLimit: 240_000_000, | ||
| livenessBond: 0.07 ether, | ||
| stateRootSyncInternal: 16, |
There was a problem hiding this comment.
Didnt we say this should be 1?
There was a problem hiding this comment.
On the testnet/mainnet too? Thought we were doing that for the devnet for our convenience
There was a problem hiding this comment.
Given the expected low number of blocks proposed, im leaning towards yes. Let me know if the consequences of changing it would be grave. What kind of extra cost do we expect?
There was a problem hiding this comment.
It's going to 25K-50K extra gas per proof since this change on its own is not very relevant. We add this with the "verify on every proof" change that I spoke about two days ago. So, the entire verification flow is also executed. If we are confident that 16 blocks won't take a huge time to show up, we should keep the Taiko specified constants imo.
There was a problem hiding this comment.
Can we set different values for mainnet testnet. I think for testnet, we can keep the 16, but for mainnet we should set it low as my expectation in the beginning to have very few blocks
There was a problem hiding this comment.
Thinking bout it, since testnet eth is abundant, we can keep it low for both mainnet and testnet
| baseFeeConfig: LibSharedData.BaseFeeConfig({ | ||
| adjustmentQuotient: 8, | ||
| sharingPctg: 75, | ||
| gasIssuancePerSecond: 5_000_000, |
surgefolders under both contracts and scripts.Surge: <change description>