Protocol 1.2 Current
Protocol Releases & Changelog
Ordex strictly adheres to backwards compatibility for all signed order PSBTs and on-chain settlements.
Interactive Protocol Version Diff Tool
Inspect additive capabilities, schema changes, and migration steps between protocol versions.
➔
Ordex Protocol 1.0 Baseline
StableFoundational protocol for portable signed PSBT orders, public asks, independent settlement, and deterministic purchase verification.
Contract Digest: sha256:d8a2f1b0918c8e19c8f619e07891230485918239048102381203810293810293
Capabilities (5):
- Portable public asks with seller signature
- Buyer settlement transaction composition
- Deterministic purchase verifier with sat-flow preservation
- Order lifecycle states: OPEN, RESERVED, SETTLED, WITHDRAWN, EXPIRED
- OpenOrdex Nostr event import and interoperability
Ordex Protocol 1.2 Current Production
CurrentAdds Collection Provenance manifests, Counterparty Heritage Asset UTXO management, Cold-Signing session manifests, and SSE/WebSocket event replay checkpoints.
Contract Digest: sha256:a7bfe9b1232047ac390a6505b0d4384616435b22b658d839352ec77fba11b816
Added / Upgraded in v1.2:
- Collection Provenance manifests with Merkle membership proofs
- Counterparty Heritage Asset attachment and detachment UTXO workflows
- Offline Cold-Signing session manifests with air-gapped signature verification
- Event stream checkpointing and cursor replay for SSE/WebSocket
- Signed webhook endpoint verification, delivery history, and replaying
Migration Checklist: v1.0 ➔ v1.2
Ordex protocol releases are backwards compatible. Handled via additive OpenAPI routes and AsyncAPI event envelopes.
- All v1.0 signed PSBT portable asks continue to verify and settle without modification.
- Update
@bitcoinuniverse/ordex-sdkto1.0.0. - If consuming event streams, update cursor tracking to support checkpoint replaying.
Was this documentation helpful?
Privacy-first feedback. Your feedback is never shared with third parties.