Layr-Labs / Layr-Labs/devkit-cli
check fork blocknum >= eip1559 hard fork block
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 27
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
chains:
l1:
chain_id: 31337
rpc_url: "http://localhost:8545"
fork:
block: 22475020
url: ""
block_time: 3
If blocknum is zero instead of 22475020, eip1559 gas estimation issue occurs
Script ran successfully.
== Logs ==
Deployer address: 0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266
TaskMailbox deployed to: 0x5FbDB2315678afecb367f032d93F642f64180aa3
## Setting up 1 EVM.
==========================
Simulated On-chain Traces:
[3046021] → new TaskMailbox@0x5FbDB2315678afecb367f032d93F642f64180aa3
└─ ← [Return] 15103 bytes of code
Error: Failed to get EIP-1559 fees; unsupported feature: eip1559
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the EIP-1559 fee-estimation failure with chains.l1.fork.block set to 0, then compare it with block 22475020. Trace the CLI's fork-block configuration and fee-estimation paths; done should include verified behavior for block numbers before and at the EIP-1559 fork threshold.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100