Agent skill

Verified State

by Nethereum in Nethereum/Nethereum

Help users verify Ethereum state (balances, nonces, storage, code) without trusting their RPC provider using beacon chain light client proofs.

MITAuto-check passedBackend & APIs

Install Verified State

skills CLI
$ npx skills add Nethereum/Nethereum --skill verified-state -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Nethereum/Nethereum verified-state --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Nethereum/Nethereum.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/nethereum-skills/skills/verified-state .claude/skills/verified-state && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
verified-state
GitHub stars
2.3k
Token cost
~2.2k tokens
SKILL.md length
417 words
Files
1
Skills in repo
71
Repo updated
First seen
Licence
MIT

At a glance

Help users verify Ethereum state (balances, nonces, storage, code) without trusting their RPC provider using beacon chain light client proofs.

  • The user mentions trustless queries
  • SKILL.md covers When to Use This, Required Packages, Full Initialization and The Simple Path:…, plus 6 more sections
  • Calls dotnet; reaches mainnet.rpc.url and ethereum-beacon-api.publicnode.com
  • Verified balances

What it does

Verified State is an agent skill from Nethereum/Nethereum. Help users verify Ethereum state (balances, nonces, storage, code) without trusting their RPC provider using beacon chain light client proofs. Use this skill whenever the user mentions trustless queries, verified balances, light client verification, proof verification, Merkle proofs for state, ethgetProof, UseVerifiedState, VerifiedStateService, or wants to verify data from an RPC provider they don't trust.

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs. It works with Ethereum. The repository describes itself as: Ethereum .Net cross platform integration library. The licence is MIT.

When your agent uses it

  • The user mentions trustless queries
  • Verified balances
  • Light client verification
  • Proof verification

Example prompts

  • “/verified-state”

What it can do on your machine

Read from SKILL.md and the folder at commit 229f278. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • dotnet

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • mainnet.rpc.url
    • ethereum-beacon-api.publicnode.com

    Also links to:

    • docs.nethereum.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Verified State loads about 2.2k tokens when it runs. Until then it costs about 107 tokens; SKILL.md has 417 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~107
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Nethereum/Nethereum at commit 229f278, republished under its MIT licence (© Nethereum). 417 words, ~2,222 tokens.

Download SKILL.mdSave it as .claude/skills/verified-state/SKILL.md (or your agent's skills folder).
name
verified-state
description
Help users verify Ethereum state (balances, nonces, storage, code) without trusting their RPC provider using beacon chain light client proofs. Use this skill whenever the user mentions trustless queries, verified balances, light client verification, proof verification, Merkle proofs for state, eth_getProof, UseVerifiedState, VerifiedStateService, or wants to verify data from an RPC provider they don't trust.
user-invocable
true

Verified State Queries — Nethereum.ChainStateVerification

Verified state queries let your application cryptographically confirm that balances, nonces, contract code, and storage values returned by an RPC provider are genuine. Instead of trusting the RPC node, the data is verified against a beacon chain state root using Merkle proofs.

When to Use This

  • Trustless balance checks: Verify ETH balances before signing transactions or displaying in a wallet
  • Nonce verification: Confirm transaction counts to prevent replay or stuck transactions
  • Contract code verification: Ensure contract bytecode has not been tampered with by a malicious RPC
  • Storage proof verification: Read and verify individual storage slots in smart contracts
  • Financial dashboards: Display balances with cryptographic proof of correctness
  • Self-custodial wallets: Eliminate trust in third-party RPC providers

Required Packages

bash
dotnet add package Nethereum.ChainStateVerification    # VerifiedStateService, interceptor
dotnet add package Nethereum.Consensus.LightClient     # Light client protocol
dotnet add package Nethereum.Beaconchain               # Beacon chain API client
dotnet add package Nethereum.Signer.Bls.Herumi         # BLS signature verification (native)
dotnet add package Nethereum.Web3                       # Standard Web3 client

You need two endpoints:

  • Beacon chain API URL (e.g., https://ethereum-beacon-api.publicnode.com)
  • Execution RPC URL that supports eth_getProof

Full Initialization

csharp
using Nethereum.Signer.Bls;
using Nethereum.Signer.Bls.Herumi;
using Nethereum.Beaconchain;
using Nethereum.Beaconchain.LightClient;
using Nethereum.Consensus.Ssz;
using Nethereum.Consensus.LightClient;
using Nethereum.ChainStateVerification;
using Nethereum.JsonRpc.Client;
using Nethereum.RPC.Eth;
using Nethereum.Hex.HexConvertors.Extensions;

// 1. Initialize BLS native library (required for sync committee signature verification)
var nativeBls = new NativeBls(new HerumiNativeBindings());
await nativeBls.InitializeAsync();

// 2. Connect to beacon chain and fetch finality checkpoint
var beaconClient = new BeaconApiClient("https://ethereum-beacon-api.publicnode.com");
var response = await beaconClient.LightClient.GetFinalityUpdateAsync();
var finalityUpdate = LightClientResponseMapper.ToDomain(response);
var weakSubjectivityRoot = finalityUpdate.FinalizedHeader.Beacon.HashTreeRoot();

// 3. Configure for Ethereum mainnet
var config = new LightClientConfig
{
    GenesisValidatorsRoot = "0x4b363db94e286120d76eb905340fdd4e54bfe9f06bf33ff6cf5ad27f511bfe95"
        .HexToByteArray(),
    CurrentForkVersion = new byte[] { 0x06, 0x00, 0x00, 0x00 },
    SlotsPerEpoch = 32,
    SecondsPerSlot = 12,
    WeakSubjectivityRoot = weakSubjectivityRoot
};

// 4. Create and initialize light client
var store = new InMemoryLightClientStore();
var lightClient = new LightClientService(
    beaconClient.LightClient, nativeBls, config, store);
await lightClient.InitializeAsync();

// 5. Build VerifiedStateService
var trustedProvider = new TrustedHeaderProvider(lightClient);
var rpcClient = new RpcClient(new Uri("https://mainnet.rpc.url"));
var ethGetProof = new EthGetProof(rpcClient);
var ethGetCode = new EthGetCode(rpcClient);
var trieVerifier = new TrieProofVerifier();

var verifiedStateService = new VerifiedStateService(
    trustedProvider, ethGetProof, ethGetCode, trieVerifier);

The Simple Path: UseVerifiedState()

The recommended approach. Installs an interceptor on Web3 that transparently verifies eth_getBalance, eth_getTransactionCount, eth_getCode, and eth_blockNumber via Merkle proofs. All other RPC methods pass through unmodified.

csharp
using Nethereum.ChainStateVerification.Interceptor;

var web3 = new Web3("https://mainnet.rpc.url");
web3.UseVerifiedState(verifiedStateService);

// Every balance/nonce/code query is now cryptographically verified
var balance = await web3.Eth.GetBalance.SendRequestAsync(address);

With configuration options:

csharp
web3.UseVerifiedState(verifiedStateService, config =>
{
    config.Mode = VerificationMode.Finalized;   // Strongest guarantee
    config.FallbackOnError = true;              // Fall back to unverified if proof fails
});

Fluent chaining:

csharp
var balance = await new Web3("https://mainnet.rpc.url")
    .UseVerifiedState(verifiedStateService, config =>
    {
        config.Mode = VerificationMode.Finalized;
        config.FallbackOnError = true;
    })
    .Eth.GetBalance.SendRequestAsync(address);

Direct Queries

Call VerifiedStateService methods directly for more control:

csharp
// Verified ETH balance
var balance = await verifiedStateService.GetBalanceAsync(address);

// Verified nonce
var nonce = await verifiedStateService.GetNonceAsync(address);

// Verified contract code
var code = await verifiedStateService.GetCodeAsync(contractAddress);

// Verified storage slot
var storageValue = await verifiedStateService.GetStorageAtAsync(contractAddress, BigInteger.Zero);

Each method fetches an eth_getProof response and verifies the Merkle proof against the trusted state root before returning.

Finalized vs Optimistic Mode

ModeSecurityLatencyBest For
FinalizedStrongest -- economically final, cannot be reverted~12-15 min behind headFinancial operations, balance checks before transfers
OptimisticWeaker -- based on attestations, theoretically revertibleSeconds behind headUI display, dashboards, non-critical reads

Switch to optimistic mode:

csharp
await lightClient.UpdateFinalityAsync();
await lightClient.UpdateOptimisticAsync();

verifiedStateService.Mode = VerificationMode.Optimistic;
var balance = await verifiedStateService.GetBalanceAsync(address);

Use finalized for anything involving fund transfers. Use optimistic for display-only scenarios where freshness matters more than absolute finality.

Show full SKILL.md (152 more words)Show less

Caching

csharp
verifiedStateService.EnableCaching = true;   // Cache verified results per block
verifiedStateService.ClearCache();           // Manual invalidation

Cache is automatically invalidated when the light client advances to a new block.

Error Handling

csharp
try
{
    var balance = await verifiedStateService.GetBalanceAsync(address);
}
catch (Nethereum.JsonRpc.Client.RpcResponseException ex)
{
    if (ex.Message.Contains("missing trie node") || ex.Message.Contains("proof window"))
    {
        // RPC node has pruned state for this block
        // Use optimistic mode or switch to an archive node
    }
}

Common Gotchas

  • Archive node recommended for finalized mode -- Standard nodes prune state beyond ~128 blocks. Finalized blocks are ~96 blocks behind head, near the pruning boundary.
  • BLS native library must be present -- Ensure bls_eth.dll (Windows), libbls_eth.so (Linux), or libbls_eth.dylib (macOS) is in your output directory.
  • Fork version changes with network upgrades -- CurrentForkVersion must match the current fork. Fetch dynamically from the beacon API for production use.
  • Optimistic is not final -- Data verified in optimistic mode could theoretically change during a reorganization.
  • One interceptor per client -- UseVerifiedState replaces any existing request interceptor on the Web3 client.

Verified EVM Calls

For complex queries (e.g., ERC-20 balanceOf), combine verified state with the EVM simulator to run contract bytecode locally against verified storage:

csharp
using Nethereum.ChainStateVerification.NodeData;
using Nethereum.EVM;
using Nethereum.EVM.BlockchainState;

var nodeDataService = new VerifiedNodeDataService(verifiedStateService);
var executionStateService = new ExecutionStateService(nodeDataService);

var code = await verifiedStateService.GetCodeAsync(contractAddress);
var callInput = balanceOfFunction.CreateCallInput(contractAddress);
var programContext = new ProgramContext(callInput, executionStateService);
var program = new Program(code, programContext);
var evmSimulator = new EVMSimulator();
await evmSimulator.ExecuteAsync(program);

Every storage read during EVM execution is individually verified via Merkle proofs.

For full documentation, see: https://docs.nethereum.com/docs/consensus-light-client/guide-verified-state

© Nethereum, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/nethereum-skills/skills/verified-state of Nethereum/Nethereum.

Open the folder on GitHubat commit 229f278

Compare with similar skills

Verified State next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Verified State compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Verified State this skillNethereum/Nethereum2.3k—~2.2kAutomated safety check: PassMIT
NEAR Intents Swap Integrationinternet-court/internet-court-skill6.4k2 repos~939Automated safety check: PassCustom licence
Deposit QrSuperior-Trade/superior-skills2141 repos~1.1kAutomated safety check: PassMIT
Explorer Contract Verificationsablier-labs/evm-monorepo353—~1.9kAutomated safety check: PassCustom licence
Developing Smart ContractsLFDT-Lineth/lineth-monorepo126—~1.4kAutomated safety check: PassAGPL-3.0
Squash BugbotLFDT-Lineth/lineth-monorepo126—~3.3kAutomated safety check: PassApache-2.0

Similar skills

  • NEAR Intents Swap Integration

    internet-court/internet-court-skill

    Builds cross-chain token swaps and bridge flows with the NEAR Intents 1Click API: quotes, deposit addresses, per-chain deposits and status polling.

    6.4k GitHub starsUsed in 2 repos~939 tokens
    Backend & APIsAuto-check passed
  • Deposit Qr

    Superior-Trade/superior-skills

    A skill your agent uses when a user needs a QR code or wallet payment URI to fund a Superior-managed EVM wallet on a specific chain before using Lighter, Polymarket, Hyperliquid, or other Superior…

    214 GitHub starsUsed in 1 repo~1.1k tokens
    Backend & APIsAuto-check passed
  • Explorer Contract Verification

    sablier-labs/evm-monorepo

    Verify smart contracts on Etherscan, Routescan, and Blockscout block explorers.

    353 GitHub stars~1.9k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Developing Smart Contracts

    LFDT-Lineth/lineth-monorepo

    Solidity smart contract development guidelines for Lineth blockchain.

    126 GitHub stars~1.4k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Squash Bugbot

    LFDT-Lineth/lineth-monorepo

    Triage unresolved bot review comments on a GitHub PR. An agent skill from LFDT-Lineth/lineth-monorepo.

    126 GitHub stars~3.3k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Ops Indexer Query

    boundless-xyz/boundless

    Internal — for Boundless team members only. An agent skill from boundless-xyz/boundless.

    193 GitHub stars~3.5k tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed

More from Nethereum/Nethereum

All 71 skills in this repo
  • Aa Batching Paymasters

    Nethereum/Nethereum

    Help users batch multiple calls into a single UserOperation and sponsor gas with paymasters using Nethereum Account Abstraction.

    2.3k GitHub stars~1.5k tokensUpdated 3 days ago
    Auto-check passed
  • Aa Bundler

    Nethereum/Nethereum

    Help users run an ERC-4337 bundler using Nethereum — set up in-process or standalone bundlers with mempool, validation, reputation, and JSON-RPC server.

    2.3k GitHub stars~1.2k tokensUpdated 3 days ago
    Auto-check passed
  • Abi Encoding

    Nethereum/Nethereum

    Encode and decode Ethereum ABI data with Nethereum. An agent skill from Nethereum/Nethereum.

    2.3k GitHub stars~1.3k tokensUpdated 3 days ago
    Auto-check passed
  • Abi Retrieval

    Nethereum/Nethereum

    Fetch contract ABIs from Sourcify, Etherscan, and 4Byte Directory using the composite ABIInfoStorage pattern (.NET/C).

    2.3k GitHub stars~1.5k tokensUpdated 3 days ago
    Auto-check passed
  • Account Abstraction

    Nethereum/Nethereum

    Help users implement ERC-4337 Account Abstraction with Nethereum — send UserOperations, use smart accounts, route contract calls through a bundler, enable gasless transactions, or work with AA in…

    2.3k GitHub stars~1.7k tokensUpdated 3 days ago
    Auto-check passed
  • Address Utils

    Nethereum/Nethereum

    Validate and format Ethereum addresses with Nethereum. An agent skill from Nethereum/Nethereum.

    2.3k GitHub stars~1.2k tokensUpdated 3 days ago
    Auto-check passed

Works with

Categories

Questions about Verified State

What does Verified State do?

Help users verify Ethereum state (balances, nonces, storage, code) without trusting their RPC provider using beacon chain light client proofs. Verified State is an agent skill from Nethereum/Nethereum. Help users verify Ethereum state (balances, nonces, storage, code) without trusting their RPC provider using beacon chain light client proofs.

When should I use Verified State?

Verified State fits situations like: the user mentions trustless queries; verified balances; light client verification; proof verification.

How do I install Verified State in Claude Code?

Run `npx skills add Nethereum/Nethereum --skill verified-state -a claude-code`. Or copy the skill folder (plugins/nethereum-skills/skills/verified-state in Nethereum/Nethereum) into .claude/skills/verified-state in your project. Claude Code loads it when a task matches its description.

How do I install Verified State in Codex?

Run `npx skills add Nethereum/Nethereum --skill verified-state -a codex`. Or copy the skill folder (plugins/nethereum-skills/skills/verified-state in Nethereum/Nethereum) into .agents/skills/verified-state in your project. Codex loads it when a task matches its description.

Can I use Verified State in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Nethereum/Nethereum --skill verified-state -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verified-state, .gemini/skills/verified-state, .github/skills/verified-state and .opencode/skills/verified-state in your project.

What does Verified State need to run?

Going by SKILL.md and its folder, Verified State needs the command-line tools its instructions call (dotnet).

Does Verified State access the network?

SKILL.md names 3 domains. In commands or code: mainnet.rpc.url and ethereum-beacon-api.publicnode.com; the agent is likely to contact these when it follows the instructions. As links in the text: docs.nethereum.com. This is read from the text; nothing was executed.

Is Verified State safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Verified State use?

Verified State is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Verified State use?

About 2.2k tokens (SKILL.md is roughly 8.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Verified State?

Skills that share tags, products or a category with Verified State: NEAR Intents Swap Integration (internet-court/internet-court-skill, 6.4k stars), Deposit Qr (Superior-Trade/superior-skills, 214 stars), Explorer Contract Verification (sablier-labs/evm-monorepo, 353 stars) and Developing Smart Contracts (LFDT-Lineth/lineth-monorepo, 126 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Verified State?

Nethereum (a GitHub organization) maintains it in Nethereum/Nethereum, which has 2,260 GitHub stars. The repository holds 71 skills in this directory. The repository was last updated on October 5, 2026.

Source: Nethereum/Nethereum on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.