Peer-citable papers behind invinoveritas's verification-layer work, hosted on SSRN. Verify against the primary source, not this summary.
Federico Blanco Sánchez-Llanos · 2026-09-12 · SSRN 7450504 · CC BY 4.0
Restates ERC-8299 (WYRIWE)'s Judgment-Execution composition precisely and describes invinoveritas's public verdict ledger as a running production implementation of it: signed pre-action verdicts, Bitcoin-anchored precedence, and disclosed losses alongside wins. Names the specific property the design does not yet achieve -- non-suppression -- and proposes a direction for closing it.
autonomous agents · agent verification · input provenance · judgment attestation · EIP-712 · Bitcoin timestamping · verifiable AI inference
Toshikatsu Oga, Federico Blanco Sánchez-Llanos · 2026-09-07 · SSRN 7425458 · CC BY 4.0
A verifier can be sound on every layer it runs and still return the wrong verdict, because the party being verified was allowed to choose which coordinate got measured; a truthful, reproducible read of the wrong coordinate passes. This paper reports one rule that closes the defect: the verifier derives the coordinate from a source the party being verified does not control and binds the derived value into the verdict as an output a third party recomputes. It shows the rule at four scales in one Bitcoin-anchored record system for agent-facing services: the record (which cost category an estimate is judged against, derived from its own line items), the population (which servers exist to be counted, derived from Certificate Transparency rather than self-declaration), time (when a verdict was created, bracketed by a Bitcoin block-header set the prover cannot choose), and the instant (which day and which tool a conduct measurement samples, derived from a salt committed before the window and a block hash the subject cannot influence). Each instance has a runnable reference implementation, an adversarial harness that holds every sub-layer green while it attacks the coordinate, and an anchored specification whose corrections are appended, never edited. An independent verifier built the counterpart state on his own system, drove three corrections to the operator's time axis, and asked the question that turned a refusal from a sentence in prose into a queryable ledger record; his account is in his own words. The paper also reports what is deployed against what is designed, with the operator as a subject of its own rule: the time check runs from genesis over the peer to peer network on the operator's machine but as a quorum of two among three explorers in the production gate, the census has a live coordinate and no anchored record yet, the record-level guard is a harness not yet wired into the adjudication, and the instant coordinate showed three departures from its anchored design found while this paper was written, one of which the operator's own verifier would have refused; all three were repaired the same day, and the next scheduled sweep produced the first derived verdicts, seven of eight endpoints under one beacon block that the operator's verifier confirmed against a header chain synced from genesis. The limits are named with the claims: determinism is not truth; a quorum buys operator independence, not implementation independence; a refusal proves a contradiction, not which side was honest; the census boundary is structural for private networks and clients that ignore Certificate Transparency.
verifiable conduct records · coordinate integrity · fail-closed verification · certificate transparency · bitcoin anchoring · opentimestamps · commit-reveal · block header validation · adversarial harness · Model Context Protocol · agent-facing services · reproducible research
Toshikatsu Oga, Federico Blanco Sánchez-Llanos · 2026-09-06 · SSRN 7419998 · CC BY 4.0
Tests NENRIN, a public Bitcoin-anchored conduct-record system for agent-facing (MCP) services, against a byte-for-byte independent reimplementation in a different language. All eight published rings reproduced exactly; reports the one canonicalization seam a naive port would have crossed, and the limits of what byte reproducibility does and does not prove.
reproducibility · independent reimplementation · transparency log · agent-facing services · Model Context Protocol · canonical JSON · Bitcoin anchoring · conduct record