Holocene: eip-1559 parameters in extraData#428
Holocene: eip-1559 parameters in extraData#428protolambda merged 2 commits intoethereum-optimism:mainfrom
Conversation
9b2a23d to
4793842
Compare
4793842 to
78552cd
Compare
|
As discussed in discord, updated spec to use extraData instead of nonce. |
edd510b to
9aaaed6
Compare
d700fcf to
ba4c590
Compare
8b8b267 to
1307fde
Compare
dbcae16 to
bb66a8d
Compare
b62a4a8 to
7446d94
Compare
clabby
left a comment
There was a problem hiding this comment.
lgtm. If we want, we can also take this opportunity to address your nitpick in the encoding: denominator, elasticity -> elasticity, denominator.
7446d94 to
f35359f
Compare
Thanks, given the geth impl is all using this order now, may as well leave it be given how minor this is. |
f35359f to
edb127e
Compare
tynes
left a comment
There was a problem hiding this comment.
Looks good to me, would should let @protolambda have a final say before merge
|
Just to clarify, no need to add a new p2p topic correct? |
Correct, we are no longer changing ExecutionPayload since it already contains the ExtraData field. |
1 similar comment
Correct, we are no longer changing ExecutionPayload since it already contains the ExtraData field. |
5cadb47 to
aa33894
Compare
aa33894 to
80af9ce
Compare
fe9fa2b to
b303b06
Compare
Description
EIP-1559 parameters need to be in the ExecutionPayload, not just the PayloadAttributes, to allow geth to properly include the encoded parameters in the block header. So instead of using nonce, we use the extraData field which is already in the ExecutionPayload. This will also reserve nonce to be used for sub-second block times.