-
Notifications
You must be signed in to change notification settings - Fork 20.5k
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
params,core: add max and target value to chain config #31002
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
app
eth/tracers/internal/tracetest/testdata/prestate_tracer/setcode_tx.json
Outdated
Show resolved
Hide resolved
Made the updates from your review, Marius. Thanks! |
@@ -26,7 +26,7 @@ import ( | |||
"github.com/holiman/uint256" | |||
) | |||
|
|||
var rand = mrand.New(mrand.NewSource(1)) | |||
var rnd = mrand.New(mrand.NewSource(1)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I renamed this because it was playing havoc with my LSP for some reason.
5df556c
to
c3daabe
Compare
params/config.go
Outdated
// requested time. | ||
func (c *ChainConfig) TargetBlobsPerBlock(time uint64) uint64 { | ||
if c.BlobScheduleConfig == nil { | ||
panic("blob schedule not defined") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should try to remove these panics and put a check in the fork order checker.
|
||
// CheckConfigBlobSchedule checks that all forks with blobs enabled explicitly | ||
// define the blob schedule configuration. | ||
func (c *ChainConfig) CheckConfigBlobSchedule() error { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this not in CheckConfigForkOrder
? If we introduce another function we have to call it everywhere. This check is also kind of related to the 'fork order', so it would fit perfectly into the other function.
Implements EIP-7840 and EIP-7691.