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

v1-only until 2.1

These capabilities exist in Protocol v1 and are not part of v2.0. Until 2.1 they remain v1 capabilities, and any claim that depends on one is a v1 claim.

Capability v1 reference Status in v2.0
SessionToken session fast path v1 §5.13 None. A verifier-held session grant with per-turn request binding is planned for 2.1
Agent-to-agent mutual presentation v1 §11.1 None. Two independent v2 proofs are possible but do not establish one conversation
HTTP transport and registry read bindings v1 §13, §13.1 None. Registry lookup stays deployment code that feeds trust configuration
Geo, speed, and activation constraints (geo_circle, geo_polygon, geo_bbox, max_speed_mps, activation duration) v1 §5.7.2 None. The names are reserved; a v2.0 delegation cannot express a geofence or a speed limit

These v1 capabilities are not coming back:

v1 capability Why v2 drops it
No-expiry sentinel Every v2 delegation has a real expiry, at most ten years. Open-ended grants made revocation the only bound
Empty required scope A v2 request names exactly one valid required scope; a verification that checks no scope cannot be released as authorization
Unsigned or boolean revocation inputs Status must be signed under a separate status key and applied through the anchored journal
PolicyProvider, AuditProvider, PolicyVerdict hooks A hook inside verification let a mutable local result change or stand in for the Protocol result. v2 fixes the result and receipt first; application policy runs after release
AnchorResolver inside verification Metadata lookup is not trust; trust is configured before verification
Identity enrollment objects (HumanRoot, Anchor, AgentIdentity) Enrollment is deployment policy. v2 rests on complete keys and caller-authenticated trust configuration
Self-issued live challenges A live decision needs an authenticated, stored challenge and an atomic claim. A self-issued challenge only supports archival verification

The authoritative lists are in the upgrade guide.