Crust RPC Endpoint, API Service & Dedicated Nodes

Crust Network is a decentralized storage blockchain protocol that incentivizes storage orders and utilization of IPFS storage nodes. It is one of the largest decentralized storage systems, enabling easy hosting of websites, dApps, NFTs, and personal files. Developers building on Crust need reliable RPC endpoints to interact with the network—reading blockchain data, submitting transactions, and integrating storage functionality into their applications.

Crust RPC Endpoints

OnFinality provides managed Crust RPC endpoints via HTTPS and WebSocket. These endpoints are suitable for production dApps, wallets, DeFi products, analytics tools, games, bots, and backend services. With authenticated access, you get clearer rate limits, request analytics, and a path to higher-capacity plans.

Dedicated Nodes

For teams requiring full control, OnFinality offers dedicated Crust nodes—full, archive, and validator—deployed quickly on managed infrastructure. Lightning Restore can shorten node recovery and sync workflows where supported.

Key Features

• Archive RPC: Access historical data for analytics and compliance.
• Region: Hong Kong (for dedicated nodes).
• Protocol: Substrate JSON-RPC.
• Transport: HTTP and WebSocket.

How to Connect

1. Create or sign in to your OnFinality account.
2. Select Crust from the supported networks list.
3. Create an API endpoint or deploy a dedicated node.
4. Test the endpoint using chain_getBlock.
5. Monitor request usage, errors, and limits before moving critical traffic.

OnFinality’s infrastructure is designed for scale, with request visibility and managed infrastructure options for production planning.

Crust RPC and developer resources

A useful Crust RPC page should make the connection path, supported capabilities, and production planning trade-offs clear before a developer opens the dashboard.

Best fit: mainnet production workflows for Web3 products, integrations, and app backends.

What builders usually check first:

• Read blocks, storage, events, and governance or staking data from Substrate-based chains.
• Support wallets, indexers, parachain apps, collators, validators, and analytics services.
• Plan node infrastructure when the workload needs isolated resources or chain-specific operations.

Supported capability notes:

• Authenticated Crust RPC/API access for Web3 products, integrations, and app backends.
• Flexible HTTP and WebSocket access for app, backend, and integration workflows.
• Archive-capable workflows when the product needs older chain state.
• Managed node options for workloads that outgrow shared endpoint access.

Decision notes:

• Environment: mainnet. Protocol family: Substrate JSON-RPC.
• Flexible HTTP and WebSocket access is listed for supported app and backend workflows.
• Archive support is available for historical state or older chain-data queries.
• Dedicated node options are available when the workload needs isolated resources or more operational control.
• Available regions listed by the network spec include Hong Kong.

A quick connection check usually starts with chain_getBlock, then moves into the exact methods your wallet, dashboard, bot, indexer, or backend service needs.

Planning the next step:

• Shared RPC is usually enough for early integration, prototypes, and moderate app traffic.
• Consider dedicated nodes when traffic becomes sustained, workloads are latency-sensitive, or isolation and monitoring become operational requirements.

Next steps:

• Create or manage RPC endpoints
• Review RPC pricing
• Explore dedicated nodes
• Read the RPC provider selection guide