docs: add node101 to Unichain node providers - #1156
Conversation
|
Thanks for contributing to Uniswap Docs! 🦄 Quick heads up on how this repo works: the docs you see on developers.uniswap.org are built from a separate source repo. When we accept a change here, we port it over there, so your fix might show up on the live site before it lands in this repo. Updates to this repo come in batches on a regular cadence. When yours is included, you'll be credited as a co-author on the commit, so the contribution counts on your GitHub profile and in Uniswap/docs. We review every PR but can't merge everything. Either way, someone from the docs team will follow up here once we've taken a look. One legal bit: by submitting a PR you agree your contribution is licensed under the repo's MIT license. |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
|
||
| ## node101 | ||
|
|
||
| [node101](https://node101.io/en/rpc/unichain) provides paid Unichain RPC services and managed dedicated nodes for developers, wallets, exchanges, and infrastructure teams. Capabilities include standard JSON-RPC, HTTP and WebSocket access, transaction tracing, Flashblocks API access, and a distributed architecture. The service includes dashboard monitoring of usage, endpoints, performance, and service status, plus incident reports and 24/7 technical support. Archive node services and testnet RPC support are available on request. Dedicated deployments can be scoped across Türkiye, Europe, and the United States. |
There was a problem hiding this comment.
This adds a brand-new external domain (node101.io) and a set of specific service claims (Flashblocks API access, dashboard monitoring, incident reports, 24/7 support, archive nodes, regional deployment in Türkiye/Europe/US). I wasn't able to browse the live page in this session to independently verify these claims against the vendor's site — please have a human confirm the URL is live/correct and that the claims are accurate before merging, per the usual bar for new third-party links/addresses in these docs.
| ### Supported networks | ||
|
|
||
| - [Unichain Mainnet](https://node101.io/en/rpc/unichain) | ||
| - Unichain testnet RPC support on request |
There was a problem hiding this comment.
Nit: every other provider entry lists both Mainnet and Sepolia Testnet as links under "Supported networks." Here the testnet line is plain text ("Unichain testnet RPC support on request") instead of a link, which is a minor formatting inconsistency with the rest of the file. Not a build-breaker, just a style nit.
Review summarySmall, self-contained content addition: a new node101 entry on the Unichain Node Providers page, following the existing structure (heading, description paragraph, plans/contact link, "Supported networks" list). MDX syntax and frontmatter are unaffected and look valid. Findings:
No contract addresses, chain IDs, or code samples are touched. No spam/promotional red flags beyond the normal tone already used for other paid providers (Blockdaemon, Chainstack, QuickNode) in this same file. |
There was a problem hiding this comment.
🟡 Changes recommended
The new entry introduces minor but user-facing documentation consistency issues (notably in the “Supported networks” list and locale spelling) that should be corrected before publishing.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
This PR updates the Unichain “Node Providers” documentation by adding node101 as an additional third-party provider, aligning the entry format with existing provider paragraphs and “Supported networks” sections.
Changes:
- Added a new
node101provider section describing paid RPC and dedicated node offerings. - Added a “Supported networks” subsection for node101 (mainnet + testnet availability on request).
File summaries
| File | Description |
|---|---|
| content/unichain/tools/node-providers.mdx | Adds a new node101 provider entry and supported networks list to the Unichain node providers page. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 2
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
|
||
| ## node101 | ||
|
|
||
| [node101](https://node101.io/en/rpc/unichain) provides paid Unichain RPC services and managed dedicated nodes for developers, wallets, exchanges, and infrastructure teams. Capabilities include standard JSON-RPC, HTTP and WebSocket access, transaction tracing, Flashblocks API access, and a distributed architecture. The service includes dashboard monitoring of usage, endpoints, performance, and service status, plus incident reports and 24/7 technical support. Archive node services and testnet RPC support are available on request. Dedicated deployments can be scoped across Türkiye, Europe, and the United States. |
| ### Supported networks | ||
|
|
||
| - [Unichain Mainnet](https://node101.io/en/rpc/unichain) | ||
| - Unichain testnet RPC support on request |
Summary
Add node101 to the Unichain Node Providers page, using the existing provider paragraph and supported-networks format.
The entry covers paid JSON-RPC and dedicated nodes, HTTP/WebSocket, transaction tracing, Flashblocks API access, monitoring, incident reports, 24/7 support, archive services, and testnet RPC on request.
Type of change
How has this been verified?
Compared the entry with the live node101 product page and existing Blockdaemon/QuickNode/Dwellir entries. Only
content/unichain/tools/node-providers.mdxchanges. The patch applies cleanly to the current main branch, and the complete proposed MDX file compiles successfully with @mdx-js/mdx and remark-gfm. No live endpoint performance test or publishing preview has been run.Applicable screenshots
Not applicable: text-only provider entry.
Anything else reviewers should know?
The RPC service is paid and closed-source, with testnet and archive services available on request. No free public endpoint is advertised. We understand accepted changes are ported into the separate publishing pipeline.