Skip to content
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

panic: invalid eip-1559 params in extradata #473

Open
TurtleSnail opened this issue Jan 23, 2025 · 4 comments
Open

panic: invalid eip-1559 params in extradata #473

TurtleSnail opened this issue Jan 23, 2025 · 4 comments

Comments

@TurtleSnail
Copy link

After upgrading to latest geth, broken...

Jan 23 05:14:51 t8 geth[2152521]: panic: invalid eip-1559 params in extradata
Jan 23 05:14:51 t8 geth[2152521]: goroutine 1 [running]:
Jan 23 05:14:51 t8 geth[2152521]: github.com/ethereum/go-ethereum/consensus/misc/eip1559.CalcBaseFee(0xc0017cb680, 0xc0002c3688, 0x67911ced)
Jan 23 05:14:51 t8 geth[2152521]:         github.com/ethereum/go-ethereum/consensus/misc/eip1559/eip1559.go:149 +0x65b
Jan 23 05:14:51 t8 geth[2152521]: github.com/ethereum/go-ethereum/consensus/misc/eip1559.VerifyEIP1559Header(0xc0017cb680, 0xc0002c3688, 0xc003228788)
Jan 23 05:14:51 t8 geth[2152521]:         github.com/ethereum/go-ethereum/consensus/misc/eip1559/eip1559.go:52 +0xfe
Jan 23 05:14:51 t8 geth[2152521]: github.com/ethereum/go-ethereum/consensus/beacon.(*Beacon).verifyHeader(0x5aa5151ba3f79b1f?, {0x28cda48, 0xc0001ff688}, 0xc003228788, 0xc0002c3688)
Jan 23 05:14:51 t8 geth[2152521]:         github.com/ethereum/go-ethereum/consensus/beacon/consensus.go:279 +0x174
Jan 23 05:14:51 t8 geth[2152521]: github.com/ethereum/go-ethereum/consensus/beacon.(*Beacon).VerifyHeader(0xc0003b1ac0, {0x28cda48, 0xc0001ff688}, 0xc003228788)
Jan 23 05:14:51 t8 geth[2152521]:         github.com/ethereum/go-ethereum/consensus/beacon/consensus.go:99 +0x134
Jan 23 05:14:51 t8 geth[2152521]: github.com/ethereum/go-ethereum/core.NewBlockChain({0x28dec28, 0xc0006167e0}, 0x64?, 0x0, 0xc000d11ff8, {0x28d54a8, 0xc0003b1ac0}, {0x0, 0x0, 0x0, ...}, ...)
Jan 23 05:14:51 t8 geth[2152521]:         github.com/ethereum/go-ethereum/core/blockchain.go:469 +0x15ef
Jan 23 05:14:51 t8 geth[2152521]: github.com/ethereum/go-ethereum/eth.New(0xc00023ac40, 0xc000701808)
Jan 23 05:14:51 t8 geth[2152521]:         github.com/ethereum/go-ethereum/eth/backend.go:250 +0x1116
Jan 23 05:14:51 t8 geth[2152521]: github.com/ethereum/go-ethereum/cmd/utils.RegisterEthService(0xc00023ac40, 0x1b2895b?)
Jan 23 05:14:51 t8 geth[2152521]:         github.com/ethereum/go-ethereum/cmd/utils/flags.go:2115 +0x25
Jan 23 05:14:51 t8 geth[2152521]: main.makeFullNode(0xc00055af80)
Jan 23 05:14:51 t8 geth[2152521]:         github.com/ethereum/go-ethereum/cmd/geth/config.go:226 +0x59e
Jan 23 05:14:51 t8 geth[2152521]: main.geth(0xc00055af80)
Jan 23 05:14:51 t8 geth[2152521]:         github.com/ethereum/go-ethereum/cmd/geth/main.go:376 +0x125
Jan 23 05:14:51 t8 geth[2152521]: github.com/urfave/cli/v2.(*Command).Run(0xc000239ce0, 0xc00055af80, {0xc0001d4000, 0x1f, 0x20})
Jan 23 05:14:51 t8 geth[2152521]:         github.com/urfave/cli/[email protected]/command.go:274 +0x93f
Jan 23 05:14:51 t8 geth[2152521]: github.com/urfave/cli/v2.(*App).RunContext(0xc000434780, {0x28c7e98, 0x378c660}, {0xc0001d4000, 0x1f, 0x20})
Jan 23 05:14:51 t8 geth[2152521]:         github.com/urfave/cli/[email protected]/app.go:332 +0x566
Jan 23 05:14:51 t8 geth[2152521]: github.com/urfave/cli/v2.(*App).Run(...)
Jan 23 05:14:51 t8 geth[2152521]:         github.com/urfave/cli/[email protected]/app.go:309
Jan 23 05:14:51 t8 geth[2152521]: main.main()
Jan 23 05:14:51 t8 geth[2152521]:         github.com/ethereum/go-ethereum/cmd/geth/main.go:300 +0x45

System information

./geth --version
geth version 1.101411.4-rc.4-efa05b1b-20241213
Ubuntu Release:	22.04
@protolambda
Copy link
Collaborator

Which chain are you running op-geth on? Was the node synced before starting it?

@TurtleSnail
Copy link
Author

TurtleSnail commented Jan 24, 2025

snax chain... it was synced, we upgraded geth and that happened. we got past this by deleting everything and syncing again.

@tynes
Copy link
Contributor

tynes commented Jan 24, 2025

Perhaps it had custom extradata configured?

@tynes
Copy link
Contributor

tynes commented Jan 24, 2025

It could be a good idea to hex format the extra data in the panic so that we can more easily debug this in the future

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants