# evm.execution_state_deltas

One row per artifact-backed execution, step_index, and delta_index. Rows are committed checkpoint transitions, not merely attempted writes.

Canonical HTML: <https://determica.com/docs/tables/evm-execution-state-deltas>

- Kind: View
- Layer: execution_read_model
- Category: Simulation
- Tags: Program, Execution, Public, View

## Contract and lifecycle

**Grain:** One committed checkpoint transition per (execution_id, step_index, delta_index).

**Lifecycle:** run publishes this immutable row set atomically with its owning run. Statement failure or caller rollback publishes no durable prefix; direct DML is unsupported because it can corrupt the documented invariants.

**Status and NULLs:** Interpret nullable payloads only through their owning status fields. Defensive poisoned and engine_error outcomes mean the engine refused to claim a trustworthy normal result; broad view nullability also covers owner alternatives and left-joined evidence.

### Join guidance

- Join evm.executions on execution_id for candidate and run context.
- Use attempt_id to deduplicate physical facts expanded across contextual owners.
- For program owners use step_index; for observation-call owners use observation_index and observation_key.

### Effect semantics

- Access flags describe attempted EVM access, not committed state change.
- Effect facts retain attempted evidence and final committed, reverted, discarded, or poisoned disposition.
- execution_state_deltas contains committed checkpoint transitions only; observation-call effects are excluded from execution_effect_summary.

## Columns

### Identity and ownership

Contextual keys and reusable identities that establish row ownership.

- `execution_id` (UUID; nullable) — Contextual execution association identity; do not use it as reusable artifact identity.
- `execution_artifact_hash` (BYTES32; nullable) — Reusable complete execution-artifact identity when publication produced one.
- `attempt_id` (UUID; nullable) — Reusable physical attempt identity; contextual owners may share this value.

### Chain context

Pinned chain, block, profile, and revision context.

- `chain_id` (UBIGINT; nullable) — EVM chain identifier frozen for the owning execution.
- `chain_profile` (VARCHAR; nullable) — Named chain-rules profile frozen for the owning execution.

### Ordering and cardinality

Stable indexes and counts used to reconstruct deterministic order.

- `step_index` (UINTEGER; nullable) — Zero-based program order; NULL for observation_call attempt owners.
- `delta_index` (UINTEGER; nullable) — Zero-based deterministic order of committed deltas within the step.

### Payload and evidence

Operation-specific inputs, outputs, and authenticated evidence.

- `state_kind` (UTINYINT; nullable) — Stable numeric discriminator for storage, balance, code, nonce, or evidence state.
- `state_kind_name` (VARCHAR; nullable) — Stable public name corresponding to state_kind.
- `address` (ADDRESS; nullable) — Account or storage-owner address described by this fact.
- `slot` (BYTES32; nullable) — Storage slot for storage state, or the documented zero sentinel for non-storage state.
- `value` (BYTES; nullable) — Typed payload bytes for this fact; interpret them with state_kind and cleared.

### Status and disposition

Outcome vocabulary and NULL-controlling disposition fields.

- `cleared` (BOOLEAN; nullable) — Whether the committed delta removes the represented state value.

### Commitments

Hashes and roots authenticating specifications, facts, state, or results.

- `committed_state_delta_root` (BYTES32; nullable) — Commitment to the ordered committed deltas for this step.
- `pre_checkpoint_state_identity_hash` (BYTES32; nullable) — Identity of the retained checkpoint before this committed delta set.
- `post_checkpoint_state_identity_hash` (BYTES32; nullable) — Identity of the retained checkpoint after this committed delta set.

## Linked joins

- `execution_id` → [evm.executions](/docs/tables/evm-executions.md) (`execution_id`) — Contextual execution that exposes this public row.

## Related public objects

- [evm.executions](/docs/tables/evm-executions.md) — upstream

## Verified queries

### Confirm fixture coverage

Confirm that this object has rows owned by the stable seven-candidate public fixture.

```sql
SELECT 'evm.execution_state_deltas'::VARCHAR AS object_name, CASE WHEN count(*) > 0 THEN 'PASS' ELSE 'FAIL' END::VARCHAR AS status FROM evm."execution_state_deltas" o JOIN evm.executions e USING (execution_id) WHERE e.candidate_key IN ('complete-effects', 'later-revert', 'ordered-logs', 'create', 'selfdestruct', 'blockhash', 'transient-access');
```

### Check candidate ownership

Diagnose whether this object remains linked to at least one stable fixture candidate through public keys.

```sql
SELECT 'evm.execution_state_deltas'::VARCHAR AS object_name, CASE WHEN count(DISTINCT e.candidate_key) > 0 THEN 'PASS' ELSE 'FAIL' END::VARCHAR AS status FROM evm."execution_state_deltas" o JOIN evm.executions e USING (execution_id) WHERE e.candidate_key IN ('complete-effects', 'later-revert', 'ordered-logs', 'create', 'selfdestruct', 'blockhash', 'transient-access');
```