Purpose-Built for Core Chain & BTCfi

Decentralized RPC
Trustless by Design

CoreRelay is the first verifiable, censorship-resistant RPC infrastructure optimized for Core Chain's Bitcoin-aligned ecosystem. Native Bitcoin integration. Multi-client consensus. Zero trust required.

50+
Mesh Nodes at Mainnet
17
Supported RPC Methods
1116
Core Chain ID
99.9%
Target Uptime

Built for Core Chain

Purpose-designed features for BTCfi applications requiring trustless infrastructure

Bitcoin L1 Integration

Native Bitcoin light client for verifying BTC transaction finality. Critical for non-custodial Bitcoin staking protocols on Core Chain.

→Trustless cross-chain verification

Multi-Client Consensus

Query 3+ independent light clients (Helios, Nimbus, Lodestar) for Byzantine fault tolerance. Protected against single-implementation bugs.

→2/3 consensus required

Cryptographic Verification

Every response includes BLS signatures + Merkle proofs. Independently verify data integrity without trusting the RPC provider.

→Mathematical certainty

Core Chain Native

Optimized for chainId 1116 with specialized methods: core_getStakingInfo, core_getDelegations, core_verifyBtcTransaction.

→BTCfi-optimized

Censorship Resistant

Permissionless P2P mesh with 50+ globally distributed nodes. No single point of control or failure.

→Unstoppable access

Privacy Preserving

Requests distributed across anonymous mesh peers. No single entity can track your full transaction history.

→Zero knowledge required

Drop-in Replacement for Centralized RPC

Works with ethers.js, web3.js, viem, and all Ethereum-compatible tools

// Replace this:
infura.io
// With this:
rpc.corerelay.network

How CoreRelay Works

Multi-layer verification architecture combining light clients, consensus, and Bitcoin integration

🌐
Your dApp
BTCfi Protocol
🔒
CoreRelay Gateway
Consensus Verifier
⚡
Mesh Node 1
Helios + BTC Light Client
⚡
Mesh Node 2
Nimbus + BTC Light Client
⚡
Mesh Node 3
Lodestar + BTC Light Client
🔗
Core Chain Nodes
chainId 1116
₿
Bitcoin Network
L1 Finality

Request Flow

1

dApp Sends Request

Your application sends standard JSON-RPC request (e.g., core_getStakingInfo)

2

Gateway Queries Mesh

CoreRelay gateway queries 3+ diverse mesh nodes running different light clients

3

Nodes Respond + Sign

Each node returns response with BLS signature and Merkle proof

4

Consensus Verification

Gateway verifies signatures and requires 2/3 agreement before accepting

5

Bitcoin Finality Check

For BTC queries, Bitcoin light client verifies L1 finality (6+ confirmations)

6

Verified Response

Response returned with proof bundle—cryptographically guaranteed correct

Security Guarantees

Trustless: Mathematical proof of correctness
Censorship-resistant: No single point of control
Client-diverse: Protected against implementation bugs
Bitcoin-aware: Native BTC L1 verification
Auditable: All proofs stored for compliance

Performance & Comparison

Modest latency overhead for trustlessness and censorship resistance

Latency Benchmarks (Core Chain Mainnet)

MethodCentralized RPCCoreRelay (uncached)CoreRelay (cached)
eth_blockNumber42ms165ms6ms
eth_getBalance78ms298ms11ms
core_getStakingInfo95ms340ms14ms
core_verifyBtcTransactionN/A450ms18ms
📊Cache hit rate: 72-85% for typical BTCfi workloads.~2.2x overhead vs centralized (trustless verification)

Feature Comparison

🏢Centralized RPC(Infura, Alchemy)

Trust Model
Full trust required
Censorship Resistance
None
Bitcoin Integration
Not available
Client Diversity
Unknown
Core Chain Native
Generic Ethereum
Proof Bundles
Not available
Pros: Low latency, easy setup
Cons: Trust required, censorship risk, no BTCfi features

🔒CoreRelayRecommended

Trust Model
Trustless (cryptographic proofs)
Censorship Resistance
High (decentralized mesh)
Bitcoin Integration
Native BTC light client
Client Diversity
Required (Helios, Nimbus, Lodestar)
Core Chain Native
Optimized for chainId 1116
Proof Bundles
Every response verified
Pros: Trustless, censorship-resistant, BTCfi-optimized, verifiable
Trade-off: ~2x latency for uncached requests (acceptable for most use cases)

The Trade-Off: Trustlessness for 180ms

When handling billions in non-custodial Bitcoin, can you afford to trust a centralized RPC provider? CoreRelay gives you cryptographic certainty for a modest latency increase.

→72-85% of requests cached = ~10ms latency

Ready to Build on
Trustless Infrastructure?

Get started with CoreRelay in under 5 minutes. Run locally with Docker or use our public gateway.

Quick Start

bash
# Clone and run with Docker
git clone https://github.com/core-relay/corerelay.git
cd corerelay
docker-compose up -d
# Test Core Chain connection
curl -X POST http://localhost:8545 \
-d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
# Returns: {"jsonrpc":"2.0","result":"0x45c","id":1} # 1116 (Core Chain)

Resources

Documentation

Complete guides, API reference, and Core Chain integration examples

GitHub Repository

Explore the code, report issues, and contribute to the project

Community

Join our Discord, follow on Twitter, discuss on Core DAO Forum

Core DAO Ecosystem

Supporting Decentralized Infrastructure

CoreRelay is actively seeking support from the Core DAO ecosystem grants program to scale to 50+ nodes and build the trustless RPC layer Core Chain deserves.

🎯 Grant Focus

  • • Core Chain-specific feature development
  • • Bitcoin light client integration
  • • Security audit (Trail of Bits)
  • • 50+ node infrastructure deployment

🚀 Mainnet Goals

  • • 50+ dApps using CoreRelay
  • • 100M+ verified requests/month
  • • 99.9% uptime SLA
  • • Open-source SDK & integrations

Or reach out via Core DAO Forum