Skip to content
You are reading the Ratify Protocol v2 beta documentation. Protocol v1 remains available at the site root.

Ratify Protocol v2 (beta)

Ratify Protocol v2 is a new, separately versioned protocol for delegated-authority proofs. It keeps the post-quantum hybrid signatures of v1 (Ed25519 plus ML-DSA-65, NIST FIPS 204, where both must verify) and changes what a verifier must do before an application may act: the verifier first commits a Protocol outcome together with a signed receipt, and only a released decision is actionable.

These pages document 2.0.0-beta.2. Protocol v1 (1.0.0-alpha.21) stays at the site root and remains available.

A principal signs a delegation with a typed signer. The verifier issues a one-time challenge and stores it before anyone sees it. The agent signs a presentation over that challenge. The verifier checks the proof, claims the challenge atomically, reads signed status from a separate status key, and commits an outcome with a sealed receipt body. A publisher signs the receipt into a hash-chained log, an independent checkpoint acknowledges it, and only then does ReleaseV2Decision return a released decision. The application gates every side effect on that decision’s action check, run against its own clock immediately before acting.

Quickstarts

One per language: Go, TypeScript, Python, Rust, C. For mobile installation and API use, see Swift and Kotlin. The runnable examples use test-only in-memory stores and are for development only.

SDK reference

Packages, install lines, and entry points per language. All SDKs →

Every v2 program shown on this site is an example from the protocol repository, built and run by the protocol test suite, and copied here at a pinned commit with its SHA-256 checked at build time. No v2 SDK code is written into these pages by hand.