NethermindEth / NethermindEth/juno
No L1 assumptions, expand functionality
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 444
- Forks
- 244
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 78
Description
Currently Juno assumes L1 will always be Ethereum which set restrictions such as what's the address size is (limited to 20 bytes) and which RPC methods it uses to communicate to such L1.
We should improve upon this and assume L1 can be Ethereum or another L2 like Starknet; in this example Juno would be sitting on an Starknet-based L3.
Contributor guide
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 surveying Juno's L1 configuration, address handling, and RPC communication boundaries, then identify assumptions tied specifically to Ethereum. The issue does not name files or tests, so map those areas before proposing changes. Done means Juno can treat an L1 as Ethereum or another L2 without the 20-byte address or Ethereum-specific RPC restrictions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100