§ Drift Trace Atlas
Drift Trace Atlas Working Notes
Category: Proof integrity
Scope: private index
Rev 0.4
2026-10-04
Pages: map, spec

Drift Trace Atlas

StatusDraftFinal

First divergent byte: 0x01A4

Select two proof runs. Hex output is compared in 4-byte groups and stops at the first byte past your threshold.

Open map
live check · R-003 ↔ R-0040x08

1.Seeded comparison

The pair below is live. Run A is R-003. Run B is R-004. Both outputs are 512 bytes. The rail on the left selects a different pair.

1.1Example

example 1.1 · atlas cli

            
# output prints here

1.2Threshold

A byte pair differs by a delta between 0x00 and 0xFF. Deltas at or below the threshold are recorded in amber. The first delta above it halts the check.

0x08

Default 0x08. This pair halts at 0x01A4 with Δ 0x3C. Set 0x3C or higher and the pair passes. Set 0x04 and it halts at 0x0112.

1.3Hex columns and verdict

verified 4-byte groupchanged byte, Δ ≤ thresholdfirst divergence past threshold

2.Same circuit, new hash, different output

A recompiled circuit can change proof output without failing verification. Drift Trace Atlas diffs each run against the last and records the first offset that differs.

Verification answers one question: does the proof satisfy the circuit. It does not compare two outputs. The atlas does that comparison and stores the result next to both runs.

2.1Requirements

  • R-1The checker MUST read both outputs in 4-byte groups, from offset 0x0000 upward.
  • R-2The checker MUST halt at the first byte whose delta exceeds the threshold and record its offset.
  • R-3Bytes with a delta at or below the threshold SHOULD be recorded as changed, not as divergent.
  • R-4Each run MUST store its circuit hash and its full hex output.
  • R-5An archived run SHOULD leave the map but keep its record.

3.Comparison procedure

3.1Diagram

run n−1out[512] run nout[512] comparegroup[4] bytes Δ ≤ thr ?per byte ✓ next ✕ halt yesno run n−1out[512] run nout[512] comparegroup[4] bytes Δ ≤ thr ?per byte yesno ✓ next group ✕ halt @ off
Figure 1. One pass over two outputs. The loop returns to the next group until a byte exceeds the threshold.

3.2Byte states

Every colour is a state. Green marks a verified 4-byte group. Amber marks a changed byte with a delta at or below the threshold. Red marks the first byte past the threshold. Grey bytes are unchecked.

4.Explorer map

Each node is one proof run. Edges point from a run to the run it was diffed against. Edge colour is the result at the current threshold. Select two nodes to open the comparison.

Open map

5.Chain reference: NEAR Protocol

The figures in this section are read from the NEAR Protocol chain. They are not illustrative. Each carries its source and the block or time it was read at.

5.1Top pools

#PoolDEXVolume 24hReserveBuys / sells 24h

5.2New pools

    5.3Sources

      A.Share card

      § LINKS
      X Telegram
      CA TBA