-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(protocol): allow L2 contracts to read L2's parent block timestamp #16425
Conversation
While i understand the mechanics you described, i'd be interested in what would be that "free" or "fair" mint token ? AFAIK TKO will have constant supply (no deflationary, no inflationary) so it must be something else. If something else, what would it be and who would back that token ? or rather what would it give value - so that it incentivizes the liveness ? Should not liveness be incentivized simply by the collected fees ? If that is not enough, proposers should simply wait until they are profitable, even tho txns would be a bit delayed - but this is a known 'issue'. Or it could also be used for off-chain mechanisms (airdrop of TKO) by the DAO to active proposers. (?) |
It is not the TKO token for sure, but it can ben NFTs or another reward token that we can promise will receive some airdrop as part of our trailblazer campaign. One example is: #16408 |
It is pretty much already possible to read the parent's block timestamp by reading it from the parent block's blockhash. And because all L2 blockhashes are stored, that way allows even reading it from any L2 block compared to just the current block. Of course, this does depend on putting the blockheader data corresponding to the blockheader onchain to make it available to be used in a smart contract. |
This is a small feature but it may be very useful for us to incentivize block proposers for liveness. For example, we can allow a fair-mint token that only can be minted by
block.coinbase
for each L2 block but only when the L2's block is x seconds later than the parent's block timestamp. Without being able to read the parent L2 block's timestamp, this is impossible.This tiny feature imposes a very small amount of additional gas cost.