docs(nodes): add NOWNodes as Celo RPC provider - #2248
Conversation
…tries AGENTS.md section 4 rules out inflated adjectives and promotional framing. "geo-balanced infrastructure, automatic failover, 24/7 support" is vendor copy rather than something a reader chooses on; the debug-method support is the part that actually differentiates the entry, so that stays. Matches the shape of the Lava and Infura entries. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
GigaHierz
left a comment
GigaHierz
left a comment
There was a problem hiding this comment.
Approving. Both links verified 200 (nownodes.io, nownodes.io/nodes/celo-celo), and the entry follows the existing provider pattern.
Two maintainer commits pushed to your branch:
-
Rebased onto main.
tooling/nodes/overview.mdxwas rewritten by #2291 last week (the thirdweb de-promotion also touched this file), so the branch no longer applied cleanly. -
Trimmed the blurb. AGENTS.md section 4 rules out promotional framing, so "geo-balanced infrastructure, automatic failover, 24/7 support" came out. The debug-method support stayed — that is the part a reader actually chooses on, and none of the neighbouring entries mention it. The entry now reads like the Lava and Infura ones:
NOWNodes is a managed RPC provider. Their Celo endpoints support debug methods.
For the record, the GetBlock entry directly above yours is considerably worse on this ("Tier 1", "lightning-fast", "best-in-class support") and predates your PR. That is not yours to fix and I have left it alone — it wants its own cleanup pass.
If NOWNodes also serves Celo Sepolia, say so and I will add it to the Supported Networks list before this merges.
2 participants
Celo RPC Provider Documentation Update
The hole, and the fix
NOWNodes is currently missing from the list of Celo RPC providers.
This PR adds NOWNodes as a managed Celo Mainnet RPC provider, with a link to the Celo-specific service page and information about supported debug methods.
What this does NOT do / residual risk
Documentation-only change. It does not modify Celo network functionality, node software, or application code.
Judgement calls
None.
Issues
None.
Stacking / conflicts
Branched off main and independent of other PRs.
Verification evidence
Confirmed Celo Mainnet is supported by NOWNodes.
Confirmed Celo RPC access is available.
Confirmed debug methods are supported.
Confirmed the linked NOWNodes Celo product page is available.
No application tests were run because this is a documentation-only change.
Remaining ops steps
None
Checklist
Title is the commit message I want on main
Judgement calls / bundled product changes flagged above (or "none")
README / runbook / .env.example / examples / error strings updated for the world this creates — N/A, documentation-only provider listing
No secrets in the diff
Questions for the maintainer marked clearly at the end (or "none")
Questions for the maintainer: none.