Add a commercial RPC provider listing for node101
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- documentation
Research direction
Start with CONTRIBUTING.md and the existing RPC provider table or resource section in the documentation. Check how providers such as Ankr and Chainstack are represented and whether a commercial-provider subsection fits the project's format. Done means the proposed node101 entry has an approved location and follows the repository's contribution conventions.
Written by the indexing model from the issue text.
Description
Hi Scroll documentation team,
We would like to contribute a node101 listing to your developer infrastructure resources. Following CONTRIBUTING.md, we are opening this issue before preparing a PR for review.
Your current RPC table includes providers such as Ankr and Chainstack and contains directly usable public endpoints. node101 offers paid services, so our product URL should be listed as a commercial provider link rather than inserted as a callable public endpoint.
Suggested entry:
node101 provides paid Scroll RPC services and managed dedicated nodes for developers, wallets, exchanges, and infrastructure teams. Capabilities include standard JSON-RPC, HTTP and WebSocket access, transaction tracing, 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.
Would a commercial-provider subsection near the existing RPC resources be appropriate? We can contribute the entry in your preferred format after this issue is reviewed.
Contact: hello@node101.io. The RPC service implementation is closed-source.
- Dominant language
- MDX
- Stars
- 701
- Forks
- 196
- PR merge metrics
- No merged PRs in 30d
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.
More from scroll-tech/scroll-documentation
-
enhancement
Difficulty 1/5 1-3 hours Newbie friendliness 68/100
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
enhancement
scroll-tech/scroll-documentation#427 · 1 comment · 1 assignee ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 35/100
scroll-tech/scroll-documentation#407 · 1 comment · 1 reaction ·
All issues in scroll-tech/scroll-documentation
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
certification
Difficulty 1/5 Under an hour Newbie friendliness 80/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
bisq-network/support#2181 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
tutorial updates Open
Difficulty 1/5 Under an hour Newbie friendliness 80/100
sveltejs/svelte.dev#2241 ·