Repository navigation
TACET 0.1.1 — verify in the browser
TACET 0.1.1
Second verifier. A TACET proof can now be verified in the browser with nothing installed: /registry/seal/verify/?url=<proof>. site/registry/seal/verify/tacet-verify.js (plain JS on WebCrypto, <300 lines) re-does SPEC §8.5 independently of the Python reference: seal binding, sheet signatures and hash chain, the empty slot under every depth-256 root, observer signatures and RFC 6962 inclusion of each negative snapshot, silence recomputation under the monotonicity rule, witness quorum, plus opt-in network checks (drand round bytes, published trust root). The OpenTimestamps step remains command-line only. Both verifiers run against the same vectors in CI (tacet/conformance/run_conformance_js.cjs).
Conformance.
- Fixture drand rounds are now the real rounds for the fixture epochs on chain
8990e7a9…; a verifier that enforces §8.5 step 2 accepts the vectors. (0.1.0 vectors used placeholder rounds and would be rejected by such a verifier.) - New
wrapped_002_invalid.json: six invalid proofs under a valid outer Seal. A verifier that stops at the Seal signature accepts them; a conformant one must reject every case. Runner: 34 cases.
Spec. §7.3: a predicate MUST state what it does not recognise; the reference predicate 1.0.0 is English-only, stated in the spec, on the TACET page and in #3.
Operator. publish writes shields.io endpoint badges under /registry/data/tacet/badges/ (epochs, models, negative, latest) — live figures for READMEs, defined by CANON §4.
Repository. SECURITY.md states TACET's claims and non-goals; issue forms for verifier failures, predicate proposals and witnesses; roadmap issues #2–#6.
Wire compatibility: unchanged. Sheets, snapshots and proofs from 0.1.0 verify under 0.1.1; generator.version in new seals reads 0.1.1.