dApp Clients, Indexing and Protocol Operations
Introduction
This always-active branch covers the software around contracts: typed clients, simulation, transaction lifecycle, event-derived views, deployment evidence, verification, dashboards, monitors, alerting, and incident response.
Why It Matters
Users and operators act on derived state. Stale RPCs, reorgs, missed logs, wrong ABIs, misleading simulation, role drift, oracle failure, and alert fatigue can make correct contracts unsafe to use or impossible to recover.
Mental Model
Treat every off-chain view as a projection with provenance and a reconciliation rule. A deployment is a manifest plus bytecode/source/config/role evidence. An alert maps a measurable condition to a rehearsed, authorized runbook.
Questions This Branch Answers
- How does a client communicate simulation, inclusion, reorg, and finality?
- Can derived state be rebuilt and reconciled from canonical inputs?
- Which signal triggers which bounded operational action?
Scope
viem clients/wallets/simulation, receipts/reorgs/multicall, indexing/backfills/reconciliation, manifests/source verification, protocol dashboards, oracle/governance/role monitors, alerts/runbooks/drills, RPC redundancy, upgrade diffs, and postmortems.
Out of Scope
Production SRE guarantees, paid monitoring dependencies, custody infrastructure, frontend aesthetics without protocol truth, mainnet deployment, and pretending an operator dashboard is canonical state.
Dependencies
Begins with Statecraft v0 and integrates every branch; especially reorg/finality, authority, and dependency health.
Candidate Note Roadmap
viem-clients-wallets-and-simulation— Separate public, wallet, test, and transport responsibilities.transaction-receipts-reorgs-and-multicall— Report lifecycle and batching without overstating certainty.event-indexing-backfills-and-reconciliation— Build idempotent projections that roll back and rebuild.deployment-manifests-and-verification— Bind addresses to chain, bytecode, source, compiler, roles, and config.protocol-state-dashboard— Expose balances, liabilities, roles, parameters, and confidence provenance.oracle-governance-and-role-monitors— Detect staleness, privileged drift, queued changes, and broken assumptions.alerting-runbooks-and-incident-drills— Connect actionable thresholds to bounded, rehearsed response.rpc-redundancy-upgrade-diffs-and-postmortems— Compare views, inspect change, and preserve learning after incidents.
Future Project
A Protocol Operations Console with viem, a reorg-aware indexer, deployment registry, state/accounting reconciliation, source/role/upgrade diffs, health monitors, synthetic alerts, and a local incident drill.
Initial Invariants
Derived state reconciles with canonical logs/state at a named block; ingestion/backfill is idempotent; reorgs remove abandoned facts; every address is chain-qualified; privileged and oracle changes surface; runbook actions remain within declared authority.
Initial Threat Model
Dishonest/stale RPCs, missed/duplicate logs, deep reorgs, wrong ABI/address/chain, compromised frontend or DNS, misleading simulation, source-verification mismatch, silent role drift, alert fatigue, leaked credentials, and dangerous automated response.
Primary Sources
viem and Foundry documentation, Ethereum JSON-RPC and log semantics, explorer verification documentation, incident-response references, and SOURCES.md.
Connects to: verification evidence, containment and regression, and every Statecraft version.