helios

Verify Ethereum state reads with cryptographic proofs against beacon state roots.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/MysticRyuujin/spirens --skill helios
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: helios
Source: https://github.com/MysticRyuujin/spirens/tree/main/helios
Command: npx skills add https://github.com/MysticRyuujin/spirens --skill helios

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helios provides cryptographic proofs for Ethereum state reads by acting as a verifier between an untrusted upstream RPC and your local or private network stack. It clarifies that Helios is not a full node, and that upstreams must support proofs for reads; verification ensures integrity of eth_getProof-backed reads used in ENS and contract lookups.

Core Features & Use Cases

  • Proof-driven reads: verifies state reads with Merkle proofs to prevent tampered results.
  • Trust anchors: uses a checkpoint URL to anchor trust and validate against beacon-state roots.
  • Deployment placement: sits between dweb-proxy and upstream RPC to strengthen end-to-end correctness in read paths.

Quick Start

Configure Helios with a checkpoint URL and an execution RPC, then deploy the stack to enable cryptographic verification of reads.

Frequently Asked Questions about helios

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify Ethereum state reads from an untrusted RPC provider?

To verify Ethereum state reads from an untrusted RPC, you can use a light client verifier that validates Merkle proofs against beacon state checkpoints. This ensures the integrity of your eth_getProof-backed data without requiring a full node.

What is a Merkle proof light client and when do I need it for ENS resolution?

A Merkle proof light client cryptographically verifies blockchain state reads without syncing a full node. You need it for trustless ENS resolution when querying opaque or untrusted upstream RPCs to prevent tampered contract lookup results.

Do I need a full Ethereum node to verify contract read proofs?

No, you do not need a full Ethereum node to verify contract read proofs. A light client verifier can validate state reads by anchoring trust to a checkpoint URL and an execution RPC that supports eth_getProof.

How does a checkpoint URL secure Ethereum light client verification?

A checkpoint URL secures Ethereum light client verification by providing a trusted beacon state root anchor. The verifier validates incoming Merkle proofs against this checkpoint, ensuring untrusted upstream RPC responses match the canonical blockchain state.

What are the limitations of using a light client for Ethereum state verification?

A key limitation is that the upstream RPC must support eth_getProof for state verification to function. Additionally, a light client verifies state reads rather than executing transactions, and it requires a valid checkpoint URL to maintain its trust anchor.

How do I set up trustless Ethereum state verification between a proxy and an upstream RPC?

Set up trustless Ethereum state verification by configuring a light client verifier between your dweb-proxy stack and the upstream RPC. You must provide a checkpoint URL and an execution RPC to enable cryptographic proof validation for reads.