smart-byte: the cluster state machine, the state hash it commits at, and its vectors #130

Merged

dcharlot merged 4 commits from smart-byte-cluster-state into main 2026-10-01 07:48:14 -04:00

Conversation 0 Commits 4 Files changed 30 +7990 -268

2026-10-01

Transaction Science

Merge main into smart-byte-cluster-state ...

# Conflicts:
#	smart-byte/conformance/v1/regeneration.md

268171ffd5

• View at this point in history

2026-10-01 06:21:29 -04:00

Transaction Science

smart-byte conformance: the second implementation runs the state machine ...

verify_v1.py now applies state vectors' frames as the cluster state spec
describes. It is written from the spec text, standard library only, and
reproduces all 106 vectors.

Falsified:
- 12 planted defects caught on their own vectors, with and without -O.
- 18 state-machine rule mutations, each caught by a state vector.

regeneration.md records the state machine; VERSIONS.md names its spec.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

ce1a371f8d

• View at this point in history

2026-10-01 06:19:03 -04:00

Transaction Science

smart-byte: the cluster state machine, and its conformance vectors ...

smart-byte-state (new):
- the state and its hash;
- inputs;
- the frame transition;
- checkpoint-and-log persistence. Checkpoints are written atomically, and
  replay refuses a gap or a wrong hash.
- a deterministic demo workload.

smart-byte-lockstep: the cluster runs these state machines in place of the
rolling hash that stood in for the state.

smart-byte-keri-witness: exposes a controller's state and resumes a replay
from it, so the cluster extends a log one event at a time.

The CLI's `cluster simulate` runs real mints and transfers through the
supermajority commit.

smart-byte-conformance: state_vectors.json, 12 vectors. Each is a genesis
state and frames of inputs, with every input's result and every frame's
state and state hash. The founding frame uses kel-001 to kel-003 and
env-001's mint. Planted defects in the state vectors are caught on their
own vectors.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

c4d3a091f3

• View at this point in history

2026-10-01 06:19:03 -04:00

Transaction Science

smart-byte spec: the cluster state, the frame transition, and the state hash ...

cluster_state.md is new. It fixes what treatise §9.4, §15 and §16 leave
open:
- The state: frame number, issuer registry, controllers' key states, and
  each byte's owner and history. Its canonical encoding is the checkpoint,
  and its BLAKE3 is the state hash a frame commits at.
- Inputs: key events, mints and transfers.
- A frame: identical inputs are one input; inputs apply by class, then by
  ascending digest; every check is named, with its error class.
- Key events apply first, so a rotation retires the old keys for everything
  in the frame it lands in.

Departures from the treatise:
- A byte's identity carries no mint frame. With the frame folded in
  (§15.2), a mint replayed in a later frame issues a second byte; §19.3
  concedes "a distinct (and possibly duplicate) byte".
- Issuers are AIDs and rotate through their key-event logs.
- Joule cost stays out of the hashed state: measured energy differs node
  by node.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

898888cbe6

• View at this point in history

2026-10-01 06:19:03 -04:00