Change one byte. Watch the digest stop matching.
Every hash below is computed in your browser with the Web Crypto API at the moment you press a button. Nothing is precomputed or hardcoded.
Demonstration payload (non-secret)
SBBX-DEMO-RECORD/v0 boundary: demonstration payload: non-secret UTF-8 demonstration bytes note: this record is not evidence of any real work event
RESULT: NOT_EVALUATED
Visual state only — it mirrors the demonstration result. This is an interactive browser integrity demonstration, not a production SBBX receipt.
- ORIGINAL_SHA256
- —
- OBSERVED_SHA256
- —
- CHANGED_BYTE_COUNT
- —
- DECLARED_OFFSET
- —
- EXECUTED_AT_UTC
- —
- NETWORK_ACTIVITY
- NONE
- CANONICAL_FILE_MUTATION
- NONE
- RESULT
- —
Browser-only integrity demonstration. It illustrates byte-level change detection and is not a production SBBX verification receipt. The mutation offset is declared by the demonstration harness, not discovered by the verifier.
One byte changes.The evidence changes with it.
A cinematic visualization of the integrity check above.The interactive demonstration remains the source of the result.
An animated visualization shows the original record in cyan entering the SBBX integrity-check engine. A one-byte modification is represented in red. The resulting digest no longer matches the original, ending in an integrity-mismatch state. This description applies only to the animation; the interactive browser demonstration remains the source of the session result.
How to read this result
A mismatch is a byte-level observation, not an explanation.
Supported readings
- · Whether evaluated bytes match expected bytes.
- · Whether an integrity chain verifies.
- · The digests computed in this session differ or match.
Unsupported readings
- · Why a byte changed.
- · Actor intention.
- · Events that occurred outside the captured evidence boundary.