Protocol record · production

Helios

Fast, secure, portable multichain Ethereum light client that turns an untrusted centralized RPC endpoint into a locally verifiable RPC for wallets and dapps.

89readiness / 100

integration: mediumethereumbaseoptimism

Also available as JSON · Markdown

Resources

docsgithub.com sdkgithub.com templategithub.com supportt.me

Good for

wallets and dapps reducing dependency on trusted RPC responses
privacy-sensitive clients that want local verification before using RPC data
Kohaku-style wallet provider abstraction

Avoid for

hiding network metadata by itself; pair with private networking or user-controlled RPC policy
chains or RPC providers that do not expose required proof APIs

Readiness score

89/100

Readiness measures how much verified integration surface exists for builders and agents. It does not mean the protocol is easy to use — integration difficulty is tracked separately.

Docs10/10

Docs URL present

SDK8/8

SDK URL present

Template6/6

Template/quickstart present

Support6/6

Support channel present

Capability depth13/20

Local verifiable RPC: production_surface; WASM/mobile-friendly light client: integration_workflow

Production-ready15/15

Has a production-ready capability

Confidence5/5

Protocol provenance confidence is high

Chain coverage6/10

3 chain(s) (capped at 5)

Freshness10/10

Last verified 6 day(s) ago

No critical issues10/10

No open critical issues

No hard caps applied.

Capabilities

Local verifiable RPC production-ready

Best for: converting untrusted RPC responses into locally verified reads, wallets and dapps that need lightweight Ethereum verification

Private RPC still needs network privacy and checkpoint hygiene; Helios verifies data but does not hide all traffic metadata by itself.

WASM/mobile-friendly light client production-ready

Best for: embedding light-client verification into wallets, Kohaku provider abstraction and privacy wallet flows

Execution RPC provider must support required proof endpoints.

Composes with

kohaku privacy_layer supports

Kohaku-style wallet stacks can use Helios for locally verified RPC reads and provider abstraction.

fluidkey privacy_layer supports

Wallets using stealth-address receiving flows can pair Helios with user-controlled RPC verification policy.

privy wallet_and_identity supports

Privy can handle user onboarding while Helios improves client-side verification and RPC trust assumptions.

Known issues

Helios verifies RPC data but is not complete network anonymity low confirmed Workaround: Use Helios for local verification. Pair it with local nodes, private networking, Tor/VPN policy, or privacy-preserving RPC strategy where metadata leakage matters.

Provenance

Last verified 2026-06-04 by composewith.eth research (Helios GitHub and Kohaku wallet best-practice docs live-verified via WebFetch 2026-06-04) (confidence: high). Score computed by score.v2.