// Ritual

The Ritual RPC Provider Builders Ship On

Connect to Ritual Mainnet with low-latency JSON-RPC and full EVM method support. Deploy contracts that call Ritual's onchain AI precompiles, managed from a single Quicknode dashboard.

// Supported networksMainnet
// 99.99% uptime SLA17+ global regions
// Every Ritual Data Pattern

The Full Data Suite.
Every Ritual Data Pattern.

Three ways to access Ritual Mainnet data, from a single eth_call to live block subscriptions. Pick the interface, ship faster.

Ritual JSON-RPC

Standard JSON-RPC over HTTPS on Ritual Mainnet. Every EVM method supported, including eth_call, eth_getLogs, eth_getBalance, and eth_sendRawTransaction, with predictable rate limits.

Debug & Trace API

Trace Ritual execution with debug_traceTransaction and trace_block against full archive state. Inspect internal calls for debugging, indexing, and simulation.

WebSocket Subscriptions

Subscribe to new Ritual blocks and logs over a persistent WSS connection with eth_subscribe. Push updates the moment they land, with no polling.

// Built for EVM Developers

Your Ethereum app runs on Ritual.

Ritual exposes a standard Ethereum JSON-RPC, so ethers.js, web3.js, viem, Foundry, and Hardhat connect to a Quicknode Ritual endpoint the same way they connect to Ethereum. Same methods, same SDK, just a different RPC URL.

Same JSON-RPC methods

eth_call, eth_getLogs, eth_estimateGas, and eth_sendRawTransaction behave exactly as they do on Ethereum.


EIP-1559 transactions only

Ritual rejects legacy type-0 transactions. viem sends EIP-1559 by default; set ethers.js and web3.py to type-2 explicitly, and drop the --legacy flag in Foundry.

  • 01
  • 02
  • 03
  • 04
  • 05
  • 06
  • 07
  • 08
  • 09
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
// Your Ethereum code, pointed at Ritual
import { createPublicClient, http } from "viem";
const client = createPublicClient({
transport: http(QUICKNODE_RITUAL_URL),
});
const block = await client.getBlockNumber();
// Same methods, same SDK. Ritual is EVM compatible.
// Add Ritual to MetaMask

Connect MetaMask to Ritual in seconds.

Open MetaMask, go to Settings, Networks, Add Network, and enter your Quicknode Ritual RPC URL with the details on the right. Save, and MetaMask routes through your private Quicknode endpoint instead of the shared public RPC.

FIELDVALUE
Network nameRitual
RPC URLYour Quicknode Ritual URL
Chain ID784
Currency SymbolRITUAL
Block Explorerexplorer.ritualfoundation.org
// Resources

Build on Ritual quicker.

Docs, guides, and runnable sample apps for every Ritual workload. Clone, customize, and ship.

// Docs

Ritual Documentation

Full reference for Ritual's Ethereum JSON-RPC, Debug, and Trace API methods, plus endpoint setup, security, and error codes.

// Guides

EVM Developer Guides

Ritual is EVM-compatible, so Quicknode's Ethereum guides run against a Ritual endpoint with a URL change. Step-by-step walkthroughs for contract calls, event logs, and transaction submission.

// Sample Apps

Sample App Library

Runnable sample apps and starter kits for EVM chains. Point one at your Ritual endpoint, clone it, and ship.

// Let's Build

Start where you are.

From your first Ritual endpoint to mission-critical production workloads, Quicknode scales with you. Get started in minutes.

// Developers

For builders who move fast.

Spin up your Ritual endpoint and ship. The free tier covers prototyping and small production loads, no credit card required.

Start building for free
// Enterprise

For teams scaling with confidence.

Dedicated Ritual infrastructure, contractual SLAs, priority support, and procurement-ready terms for wallets, exchanges, trading firms, and high-volume protocols.

Contact sales
// FAQ

Frequently Asked Questions

Still have unanswered questions? Reach out to support and the Quicknode team can help you find answers.