OpenZeppelin / OpenZeppelin/Robust-Provider
Research and implement Beacon Chain API endpoints
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6
- Forks
- 4
- Avg merge
- 15h 52m
- Merged PRs (30d)
- 5
Description
Summary
The Robust Provider currently only supports execution layer RPC methods. Beacon Chain (consensus layer) API endpoints are not supported.
Problem
Users interacting with the consensus layer cannot benefit from the retry/fallback mechanisms that Robust Provider offers.
Proposed Solution
- Research the Beacon API spec
- Determine which endpoints are most commonly used and should be prioritized
- Evaluate whether beacon endpoints fit the current architecture or require restructuring (e.g., separating by namespace)
- Implement priority endpoints with retry/fallback support
- Add tests
Open Questions
- Should beacon endpoints live in the same crate or a separate feature flag?
- How do we handle the different base URL (beacon node vs execution node)?
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 with the Beacon API spec linked in the issue and inspect the current Robust Provider architecture for its execution-layer RPC and retry/fallback handling. Identify commonly used priority endpoints and decide how beacon-node base URLs and namespace separation fit the design. Done means the selected endpoints have retry/fallback support and accompanying tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100