# Helios

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

- Readiness score: **89/100** (score.v2)
- Integration difficulty: medium
- Chains: ethereum, base, optimism
- Categories: privacy, rpc, light-client, wallets
- 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)

## Resources

- docs: https://github.com/a16z/helios/blob/master/README.md
- sdk: https://github.com/a16z/helios
- template: https://github.com/a16z/helios/tree/master/examples
- support: https://t.me/+IntDY_gZJSRkNTJj

## 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

## 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.
  - source: https://github.com/a16z/helios (retrieved 2026-06-04, high)
  - source: https://github.com/a16z/helios (retrieved 2026-06-04, high)

---
Canonical: https://composewith.eth/protocols/helios · JSON: https://composewith.eth/protocols/helios.json