Shibarium RPC Endpoint

Fast, flat-rate Shibarium RPC node provider — free tier, no KYC, HTTP & WebSocket.

Shibarium is an Ethereum Layer 2 network developed for the Shiba Inu ecosystem. It uses a Polygon-style architecture with a Heimdall validation layer and a Bor block-production layer, offering low fees and EVM compatibility.

Network: Shibarium
Type: EVM
Chain ID: 109
Slug: shibarium
Native token: BONE (BONE)
Block time: ~5 seconds
Finality: Soft: a few seconds. Hard: after Ethereum checkpoint
Mainnet: August 2023
Category: Ethereum Layer 2 (Polygon-style, Heimdall/Bor)

About Shibarium

Shibarium launched its mainnet in August 2023 as a scaling layer for Shiba Inu. Its architecture follows the Polygon design: a Bor block-production layer that runs the EVM and a Heimdall layer built on a Cosmos SDK / Tendermint-derived (Peppermint) consensus engine, with checkpoints settled to Ethereum.

Validators participate by staking BONE, which is also used to pay gas on the network. Shibarium is EVM-compatible, so standard Solidity contracts and Ethereum tooling deploy directly, and it serves as the settlement and application layer for Shiba Inu tokens such as SHIB, BONE, and LEASH.

Common Use Cases on Shibarium

  • Low-fee transfers of SHIB and ecosystem tokens
  • DeFi protocols and DEXes
  • NFT minting and games
  • BONE staking and validation
  • Consumer and metaverse applications

Shibarium Ecosystem

The ecosystem is anchored by Shiba Inu tokens (SHIB, BONE, LEASH) and projects such as ShibaSwap, plus games and dApps in the Shib metaverse.

HTTP Endpoint

https://rpc.swiftnodes.io/rpc/shibarium?key=YOUR_API_KEY

WebSocket Endpoint

wss://rpc.swiftnodes.io/ws/shibarium?key=YOUR_API_KEY

Quick Start: Connect to Shibarium

cURL

curl -X POST https://rpc.swiftnodes.io/rpc/shibarium?key=YOUR_API_KEY \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

ethers.js

import { JsonRpcProvider } from "ethers";

const provider = new JsonRpcProvider(
  "https://rpc.swiftnodes.io/rpc/shibarium?key=YOUR_API_KEY"
);

const blockNumber = await provider.getBlockNumber();
console.log("Shibarium block:", blockNumber);

viem

import { createPublicClient, http } from "viem";

const client = createPublicClient({
  transport: http("https://rpc.swiftnodes.io/rpc/shibarium?key=YOUR_API_KEY"),
});

const blockNumber = await client.getBlockNumber();

web3.py

from web3 import Web3

w3 = Web3(Web3.HTTPProvider("https://rpc.swiftnodes.io/rpc/shibarium?key=YOUR_API_KEY"))
print("Shibarium block:", w3.eth.block_number)

Add Shibarium to MetaMask

Network Name: Shibarium (SwiftNodes)
RPC URL: https://rpc.swiftnodes.io/rpc/shibarium?key=YOUR_API_KEY
Chain ID: 109
Currency Symbol: BONE
WebSocket: wss://rpc.swiftnodes.io/ws/shibarium?key=YOUR_API_KEY

Bridging to Shibarium

Assets move between Ethereum and Shibarium through the official Shibarium bridge, with additional third-party bridge support.

Features of SwiftNodes for Shibarium

  • Multiple load-balanced upstream nodes for high availability
  • Health-checked every 60 seconds with automatic failover
  • Free tier available — no credit card or KYC required
  • Flat-rate monthly pricing with no per-request fees
  • HTTP and WebSocket support
  • One API key works across all 75+ supported chains, including Shibarium

Rate Limits

PlanPriceHTTP req/sWS msg/s
Free$0/mo21
Starter$49/mo5025
Growth$89/mo15075
Scale$149/mo300150
Pro$249/mo500250

Frequently Asked Questions: Shibarium

What's Shibarium's chain ID?

Shibarium mainnet is chain ID 109.

What is the gas token on Shibarium?

BONE is used to pay gas fees and to stake as a validator on Shibarium.

What is Shibarium's architecture?

Shibarium uses a Polygon-style design with a Bor EVM block-production layer and a Heimdall validation layer, checkpointing to Ethereum.

Is WebSocket supported?

Yes - SwiftNodes provides HTTP and WebSocket (wss://) endpoints with eth_subscribe support.

Ready to start building on Shibarium? Connect your wallet and get a free API key in 30 seconds. No email or KYC required.