Don't Trust Your RPC. Verify It
Every response from a Verifiable RPC endpoint is signed inside an Intel TDX enclave by an attested node. Swap one line — your ethers or viem client for the vRPC drop-in — and every response is verified fail-closed before your code uses it. Tampered data is rejected. Any chain, no hard fork.
By Ankr — 2.5B+ daily requests70+ blockchains99.99% uptimeSOC 2 Type II
vRPC drop-in · response to eth_blockNumber
HTTP/1.1 200 OKvRPC-Signature: 5072…e704 ← Ed25519, signed in-enclavevRPC-Timestamp: 1782742648090vRPC-Pubkey: 27c6…93ac ← attested key, pinned via registryvRPC-Nodeid: 6a39…cfa2 ← signing node{"jsonrpc":"2.0","id":1,"result":"0x1c86e959"}
verified fail-closed by the drop-in · a tampered reply would have thrown before your code saw it
Verification Built Into Your RPC
Verifiable RPC (vRPC) is JSON-RPC with a cryptographic signature and hardware attestation on every response, verifiable offline by the client.
Proof on Every Response
An Ed25519 signature from attested hardware rides on each answer. Forged or altered data fails verification before your systems act on it.
Zero Integration Lift
Payloads stay byte-identical JSON-RPC. Swap one line — your ethers or viem client for the vRPC drop-in — and every response is verified fail-closed. Microseconds to verify, no extra round-trip, no callback to Ankr.
Evidence Your Auditors Accept
Every read becomes a stored, independently verifiable record, mapped to MiCA audit-trail, SR 11-7 validation, and SOC 2 Processing Integrity language.
Every Chain You Build On
Works across all 70+ chains Ankr operates, EVM and beyond — provisioned for your stack on dedicated TDX capacity.
How Does Verifiable RPC Work?
0 1—Attested Execution
Attested Execution
The signing sidecar runs inside an Intel TDX enclave co-located with the node. Its identity is a cryptographic measurement of the exact binary running — published in a signed public registry.
0 2—Every Response Signed
Every Response Signed
Each JSON-RPC response carries an Ed25519 signature over the request, response, chain ID and timestamp — three plain HTTP headers, no payload changes, works with your existing stack.
0 3—You Verify Automatically
You Verify Automatically
A one-line swap — drop the vRPC client in for ethers/viem, or run it as a verifying proxy in front of your backend. Signature checks are local and run in microseconds. The first response from each node also runs a one-time hardware-attestation check via the Phala verifier (self-hostable); it's cached, so every later response from that node is microseconds too.
ethers:
with-ethers.ts—drop-in, verified fail-closed
// was: new ethers.JsonRpcProvider(url)
import { VrpcProvider } from "@w3tech.io/vrpc-ethers";
const provider = new VrpcProvider("https://rpc.ankr.com/eth", 1);
const balance = await provider.getBalance(address);
// every response is verified fail-closed;
// a tampered reply throws before you see itviem:
with-viem.ts—drop-in, verified fail-closed
import { vrpcHttp } from "@w3tech.io/vrpc-viem";
const client = createPublicClient({ chain: mainnet, transport: vrpcHttp("https://rpc.ankr.com/eth") });Built for Systems That Act on Chain Data
Bridges & Interop
Verify what your DVN / relayer reads before it signs off cross-chain.
RWA Platforms
Tamper-evident reads behind every redemption and NAV calculation, with the audit trail MiCA expects.
Custodians & Exchanges
Settlement and proof-of-reserves on data your auditors can independently verify.
Trading & Risk Systems
Liquidation and pricing engines that refuse forged state instead of acting on it.
Which Chains Does vRPC Support?
Any Chain Ankr Runs — Prepared for Your Stack
Light clients cover one or two ecosystems. vRPC works on every chain Ankr operates — EVM and beyond — because attestation happens at the infrastructure layer, not in the protocol.
Verifiable capacity is provisioned per chain on dedicated TDX hardware: tell us which chains your systems read, and we schedule the rollout for your contract.
Talk to an ExpertTurn Cryptography Into Compliance Evidence
MiCA
Complete Audit Trail
“machine-readable retention”
Signed envelopes are exactly that.
Fed SR 11-7
Model Risk Validation
“validation layers that check outputs against verified data sources”
vRPC is that layer.
SOC 2
Processing Integrity
“deterministic input authentication”
Inputs proven authentic before use.
NIST SSDF / AI RMF
Artifact Integrity
“signed artifacts, tamper detection”
Every response is a signed artifact.
Why Verification Is Now Critical
Forged RPC Responses Stopped Being Theoretical in April 2026 when compromised RPC nodes returned fabricated
eth_call results. The backend had no way to tell — a forged response looks exactly like a real one. Withdrawals were authorized against state that never existed. It cost millions.This wasn't a smart-contract bug or a phished user: the infrastructure itself lied, and nothing in the stack could prove otherwise. Every backend that moves money based on RPC reads carries this exposure today — with every provider.
"Transaction screening can't see this attack. There is no malicious transaction to screen — until the money is already moving."
The gap nothing else coversHow vRPC Fits Your Security Stack
Wallet & Tx Screening
Blockaid-class · app layer
Screens what users are about to sign. Probabilistic, app-layer.
Keep it
Light Clients
where they exist · protocol layer
Verify chain consensus on supported networks. Run them — vRPC composes underneath.
Run them
vRPC
Verifiable RPC
infrastructure layer · every chain & method
Deterministic integrity for the data your machines act on: attested origin, tamper-proof transit, non-repudiable attribution — on every chain and every method, today.
Add it
A Standard, Not a Silo
The wire format is three documented HTTP headers. The SDK is Apache-2.0; the sidecar is AGPL-3.0. The attestation model aligns with IETF RATS (RFC 9334) and is headed to Ethereum Magicians as an Interface EIP — designed to complement protocol-level proof efforts like EIP-7792, not compete with them. Any provider can implement vRPC. We think they should.
Three documentedHTTP headersSDK isApache-2.0IETF RATSRFC 9334InterfaceEIP(Ethereum Magicians)ComplementsEIP-7792
View the Spec & SDK on GitHubBring Your Chains. We'll Bring the Proof
Bring your chains and your read paths. We'll bring a scoped plan and a pilot you can verify yourself.
- 30-minute technical scoping call
- Integration plan for your stack, no code changes
- Reply within one business day
Early access — limited Q3 design-partner slots.
Contact SalesFrequently Asked Questions
Verifiable RPC (vRPC) is an Ankr service where every JSON-RPC response is signed inside an Intel TDX enclave by an attested node. The vRPC drop-in client (a one-line swap for ethers or viem, or a verifying proxy) checks the signature locally in microseconds and rejects tampered replies fail-closed — so applications can prove chain data is authentic and untampered before acting on it, on any chain Ankr operates.
No — it composes. A light client verifies consensus where one exists; vRPC proves the response came untampered from an attested binary, and covers the many chains where no light client is available.
Signing adds milliseconds server-side. On the client, signature verification is local and runs in microseconds. The first response from each node also runs a one-time attestation check via the Phala verifier (one network round-trip); it's cached, so every later response from that node verifies in microseconds.
The registry supports revocation and key rotation, and your SDK can fail-closed on any unknown or revoked key. Worst case, you fall back to unverified RPC — you're never worse off than RPC is today.
One line. Payloads are identical — the signature rides in three HTTP headers. Swap your ethers or viem client for the vRPC drop-in, or run vRPC as a verifying proxy in front of your backend, and every response is verified fail-closed before your code sees it.
Any chain Ankr runs, EVM and beyond. Verifiable capacity is provisioned per chain on dedicated TDX hardware — tell us your list and we schedule it for your contract.
An enterprise add-on scoped to your chains — talk to us for a quote. Public verifiable endpoints with a credit uplift are planned post-GA.
The Rest of Your Web3 Stack
Node API
Reliable RPC endpoints across 70+ chains.
Advanced API
Indexed queries — balances, NFTs, transfers — in one call.
Enterprise RPC
Dedicated capacity, SLAs and regions for production scale.