For AI agents: an LLM-friendly Markdown version of every page is available by appending .md to its URL or by sending an Accept: text/markdown request header. The full documentation index is at https://www.ankr.com/docs/llms.txt
Skip to main content

Verifiable RPC: Ankr Confidential RPC in demo phase, trust model and SDK 0.4.0

Ankr Team
Docs Team

Verifiable RPC now has Ankr Confidential RPC mode: every request and answer is encrypted end to end to one attested Intel TDX node, so the Ankr gateway routes and bills the call without being able to read it. Ankr Confidential RPC is live in demo phase on Ankr's production network and rolling out across Verifiable RPC chains. It ships in SDK 0.4.0 as one option in ethers and viem, a ConfidentialClient in @w3tech.io/vrpc-core, and vrpc-proxy --confidential for any other language.

Docs​

  • Ankr Confidential RPC: how a call travels, what each party sees, how to enable it in ethers, viem, core and the proxy, errors, limits, and what the mode does not promise.
  • Trust model: who is trusted for what, what the attestation and the signature prove, attack vectors and defenses, residual risks, and how to verify the published packages and images.
  • Ankr Confidential RPC cryptography: the attested key in its X25519 form, HPKE sealing with Oblivious HTTP and Binary HTTP framing, the signature over ciphertext, and test vectors.
  • Quickstart, Overview and What is verified are rewritten for SDK 0.4.0, with the key-in-header form and the local verifying proxy.

Worth checking on your side​

  • Pass the _vrpc route. The SDK uses your URL as given and derives only <url>/attestation (and <url>/confidential in Ankr Confidential RPC mode); it does not append _vrpc. Use your chain's vRPC route, for example https://rpc.ankr.com/arbitrum_vrpc. A plain route returns unsigned answers and fails with MissingHeader.
  • Runtimes. The SDK needs Node 22.16 or later on 22, or Node 24 or later; @w3tech.io/vrpc-proxy needs Node 24 or later.
  • Error classes changed. Every SDK error now extends VrpcError and carries executed; AttestationFailed and AttestationUnavailable replace the 0.3 attestation errors, an attestation that cannot be fetched or checked right now throws AttestationUnavailable, which is not a VerificationError, and bad options throw InvalidOption. Upgrading from 0.3, read MIGRATION.md, and keep core and the adapters at the same version.

No method limits or rate limits changed for open-mode vRPC on the gateway.