Add BlockVectra to the Celo mainnet RPC providers list
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 85/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- documentation
Research direction
Edit build/tools/nodes/overview.mdx, the Nodes and Services page named in the issue. Read its existing provider sections and follow their format for the proposed Celo mainnet entry. Preview the page and run the contribution guide’s broken-link checks; done when the page includes the provider details and both checks pass.
Written by the indexing model from the issue text.
Description
I maintain BlockVectra and would like to add our Celo mainnet RPC to the existing Nodes and Services page (build/tools/nodes/overview.mdx).
Proposed entry:
BlockVectra provides public HTTP JSON-RPC access to Celo mainnet (chain ID 42220), with no API key required.
https://api.blockvectra.com/v1/celo_mainnet/public
A check on November 10 at 03:40 UTC returned chain ID 42220 and a latest block about 0.1 seconds old. That is one observation, not an uptime or archival-coverage claim. The proposed entry covers Celo mainnet only.
The change would add one provider section and retain all existing providers. I can prepare a small PR with the local preview and broken-link results required by the contribution guide.
- Dominant language
- MDX
- Stars
- 89
- Forks
- 396
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 17
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from celo-org/docs
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
chore priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
celo-org/docs#2362 · 1 comment ·
Maintainers usually reply within 1 day
-
chore priority:medium
Difficulty 2/5 Half a day Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 4/5 3-5 days Newbie friendliness 20/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Maintainers usually reply within 1 day
Similar issues
-
priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
storytold/photocraft#15350 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
docker documentation
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
VincenzoImp/openings-job-search#463 ·
Maintainers usually reply within 1 day
-
source:reader type:content-error
Difficulty 1/5 Under an hour Newbie friendliness 82/100
stephrobert/blog-roadmap#193 ·
-
Needs Triage
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
pandas-dev/pandas#72163 ·
Maintainers usually reply within 2 days