Shiden RPC Endpoints & Dedicated Nodes

Shiden Network is a multi-chain decentralized application layer on Kusama Network, supporting Ethereum Virtual Machine (EVM), WebAssembly (Wasm), and Layer 2 solutions. It enables developers to build and deploy smart contracts, DeFi protocols, NFT marketplaces, and other dApps on Kusama.

Why Use Shiden RPC?

To interact with Shiden, applications need access to an RPC (Remote Procedure Call) endpoint. An RPC endpoint is a network URL that allows wallets, dApps, indexers, and backend services to read blockchain data, submit transactions, and execute smart contract functions. Reliable RPC infrastructure is critical for production applications to maintain uptime and performance.

OnFinality Shiden RPC Endpoints

OnFinality provides managed Shiden RPC endpoints with both HTTP and WebSocket transport. Our infrastructure is designed for teams that need stable, authenticated access with usage analytics and clear scaling paths.

• Public Endpoint: Available for testing and lightweight use at https://shiden.api.onfinality.io/public (HTTP) and wss://shiden.api.onfinality.io/public-ws (WebSocket). Note that public endpoints have rate limits and are not recommended for production.
• Authenticated API Endpoints: After creating a free OnFinality account, you can generate an API key to access dedicated endpoints with higher rate limits, request analytics, and archive node support.
• Archive Access: OnFinality offers archive node endpoints for Shiden, enabling historical state queries needed by explorers, analytics tools, and indexers.

Dedicated Shiden Nodes

For teams requiring full control and maximum performance, OnFinality offers dedicated Shiden nodes. You can deploy full, archive, or collator nodes in our global infrastructure with features like:

• Lightning Restore: Rapidly sync a new node from a snapshot in seconds, not days.
• Full Control: SSH access, custom configurations, and monitoring tools.
• Global Deployment: Nodes hosted in N.Virginia (us-east-1) with multi-cloud support.

Dedicated nodes are ideal for high-throughput dApps, validators, collators, and enterprise backends.

Getting Started

1. Sign up for a free OnFinality account.
2. Navigate to the Shiden network page.
3. Create an API endpoint or deploy a dedicated node.
4. Test connectivity using the example method chain_getBlock.
5. Monitor usage and scale as needed.

Use Cases

• dApp Development: Connect your frontend or backend to Shiden via RPC.
• DeFi & NFTs: Reliable endpoints for transaction submission and data queries.
• Analytics & Indexing: Archive access for historical data.
• Collator Operations: Run a dedicated collator node with fast sync.

OnFinality eliminates the DevOps overhead of running your own node, allowing you to focus on building.

Shiden RPC and developer resources

Shiden RPC access is useful when a product needs dependable chain reads, transaction submission, and a clear path from a first request to production infrastructure.

Best fit: mainnet production workflows for parachain apps, collators, and Substrate 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 Shiden RPC/API access for parachain apps, collators, and Substrate backends.
• HTTP and WebSocket support for app, backend, and integration workflows.
• Archive access for historical state, analytics, or compliance-style queries.
• Dedicated node options when shared RPC no longer fits traffic or isolation needs.

Decision notes:

• Environment: mainnet. Protocol family: Substrate JSON-RPC.
• HTTP and WebSocket support 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 N.Virginia.

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