Skip to content

PiProof v0.18.0 — The Arbitration Court

Choose a tag to compare

View all tags
@EslaM-X EslaM-X released this 24 Aug 08:25
· 9 commits to main since this release
v0.18.0
54a8951
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

PiProof v0.18.0 — The Arbitration Court: Decentralized Verifiable Adjudication

The Dispute Engine's honest disclaimer — no judge quorum, no challenge
periods, no arbitration market, no on-chain settlement — becomes an honest
implementation of exactly those things.

Highlights

Judges are keys, verdicts are mathematics

  • Judge roster in the registry: Ed25519 keys with declared stake,
    capabilities (judge / referee) and earned reputation.
  • Weighted quorum tallies over signed ballots — every vote is an
    attestation over the exact tally inputs.
  • No single key can settle: a settlement exists only as an
    N-of-panel multi-signature over canonical certificate bytes; strip one
    signature and it stops verifying.

Trustless by construction

  • replayArbitration() re-verifies every signature and recomputes every
    tally purely (no mutation) — tampering anywhere surfaces as a named
    difference, never silence.
  • The v0.18 tests pin this hard: the naive (mutating) re-tally silently
    laundered tampered tallies; the pure split is enforced by test.
  • Challenge periods where a challenge IS a replay: proving corruption
    reopens deliberation; frivolous challenges cost reputation.

The AI division ("agent court")

  • Disputes whose defendant is agent://… get their own fee class and rules.
  • AI referees submit signed advisory opinions, recorded as evidence and
    hash-pinned into settlements — but a referee key can never vote.
  • Constitutional rule, enforced by the capability system, not by policy:
    AI argues; keys decide.

Arbitration market & settlement

  • Deterministic panel assignment by published fee books → reputation → id.
  • Reputation flows: +2 consensus at settlement, −1 rejected challenge.
  • Byte-deterministic anchor payloads (pre-commitment tested) with an
    explicit chain-adapter contract; broadcasting stays a deployment concern.

Surfaces & spec

  • Live UI at /court (strict CSP) · /api/court/{state,demo-case,file,ballot,settle} ·
    pep court-demo CLI walkthrough of a full case.
  • Normative specification: docs/COURT.md.

Verification

149/149 tests · layers clean (26 modules / 72 edges) · 20/20 attacks ·
16/16 canonical vectors ×3 languages · FUZZ OK · conformance 4/4 · TLC green
· all 13 CI checks passed on Node 18/20/22 + Python + Go + TLA+.

Assets 2
Loading