TRANSACTIONAL TRUST · VERIFIED #041

The root signature was valid. The root was retired.

Verified #040 reached constitutional/root recovery. #041 asks whether an old authentic root record can regain live authority after a newer root epoch is already known.

ROOT AUTHORITY ≠ TIMELESS AUTHORITY.

Root history

C3 — historical
epoch 3 / set-R
W25 W26 W27 / threshold 2
authentic ✅
digest = sha256:4378e3e8...

C5 — current
epoch 5 / set-H
W22 W23 W24 / threshold 2
authentic ✅
predecessor = digest(C3)
digest = sha256:07826e04...

Both records remain cryptographically authentic and both local 2-of-3 root-bound quorums validate over the same H9.

The monotonic root checkpoint

root_namespace = resonance-constitutional-root
max_root_epoch = 5
root_record_digest = digest(C5)

The checkpoint stays intact during the attack. This benchmark isolates root-record replay, not checkpoint-storage rollback.

Unsafe replay

C3 authentic = true
QC-root-epoch3 valid = true
H9 authentic = true
root binds H9 = true

→ presented_root_treated_as_current
→ adoption rows = 1
→ HTTP 200
→ effect_count = 1

Safe currentness gate

presented root epoch = 3
trusted root epoch = 5

3 < 5
→ root_authority_rollback_detected
→ adoption rows = 0
→ effects = 0

The record remains valid evidence about history; it no longer carries live authorization.

Fresh control

C5 / epoch 5
presented digest = trusted digest
QC-root-epoch5 valid = true

→ current_root_authorized
→ adoption rows = 1
→ HTTP 200
→ effect_count = 1

I123–I126

• I123 — Root authority ≠ timeless authority.
• I124 — Authentic root below a trusted root high-watermark = rollback evidence.
• I125 — Root currentness binds monotonic root epoch + root-record digest before consequence.
• I126 — A retired root may remain historically valid but must not regain live authority after a newer root epoch is observed.

Evidence

GitHub Actions run: 31621380899
Job: 94196799768
Benchmark SHA:
7590bd8ce2c894d5a72ffb9c639896e87ce3dbfd
Artifact ID: 9151370681
Artifact digest:
sha256:672ef3a413da475bb038989add5d97f109198a5b41cd865da4207823b67f6bf2
Score: 10/10

Boundary

The benchmark uses deterministic HMAC identities and PostgreSQL as a local durable high-watermark. It does not claim rollback-resistant storage, production PKI, hardware-root security, BFT finality or constitutional governance.