Ordex

An order and evidence format for exchanging Ordinals using signed PSBTs, with verification against a local node rather than a trusted marketplace.

Chain

Bitcoin

Carrier

Signed partially signed Bitcoin transactions

Ownership model

utxo

Operations

publish, route, verify

Also written

openordex

Where it came from

An original Bitcoin Universe protocol, published 2025.

A routing and evidence layer over openly published PSBT orders.

Where the specification lives

The specification and reference documentation for Ordex live in bitcoinuniverseio/ordex and are published at https://bitcoinuniverseio.github.io/ordex/. That site is the authority. This page exists so you can find it and compare it with the rest of the estate.

Bitcoin Universe indexes or implements it in bitcoinuniverseio/ordex.

Support in Bitcoin Universe products

Feature gated

Implemented, but switched off unless an operator enables the gate.

Execution model: Routes signed transactions; never broadcasts a settlement. This surface sits behind the ordex feature gate.

Where it appears

• Core: view, view-collection, list
• Wallet: view, send, receive

Implemented

• viewpsbt-routing-only
• view-collectionpsbt-routing-only
• listpsbt-routing-only

Not implemented, and why

view-activity

Ordex does not implement view-activity on this marketplace surface.

update-listing

Ordex does not mutate signed PSBT terms; publish a new signed order instead.

unlist

Ordex withdrawal is an operator-admin action; no public seller cancellation authorization is implemented.

buy

Ordex validates and routes PSBTs but explicitly does not fund, sign, or broadcast settlement.

make-offer

Ordex has no executable offer workflow on this marketplace surface.

accept-offer

Ordex has no executable offer workflow on this marketplace surface.

cancel-offer

Ordex has no executable offer workflow on this marketplace surface.

sell

Ordex has no executable offer workflow on this marketplace surface.

settle

Ordex has no executable settle authority on this marketplace surface.

reconcile

Ordex has no executable reconcile authority on this marketplace surface.

Operational behaviour

Indexing

State is read from Local Bitcoin Core and local ord server. Supporting reads come from Signed OpenOrdex Nostr kind-802 evidence, ord-offers/direct imports.

What must be true before any change is accepted: Build/publish validates live UTXO and ord claim; no persistent node/indexer lag metric is enforced.

Confirmation

Ordex never broadcasts or records a completed settlement.

Reorganisation

Manual revalidation can change actionability; no automatic reorg state transition exists.

Freshness

Orders can be manually revalidated; there is no automatic lag threshold or reconciliation cadence.

Provenance

Capability facts on this page were generated from backend/packages/ecosystem-contracts/lib/protocols.js in bitcoinuniverseio/core at 15dd03b5986a. Implemented behaviour is not the same as production availability: see how to read our status.