Ledger Listing

ORD.NET requires registering a seller-controlled 2-of-2 passthrough policy on the Ledger device for a sniping protected trading experience.

Once the policy is registered, the seller can list inscriptions held on the Ledger while connected as an Xverse wallet that imports that same Ledger account. Xverse signs TX1 (transfer) and Ledger signs TX2 (settlement) and TX3 (recovery) against the registered policy.

Wallet Policy

The policy lets the seller unilaterally recover the inscription at any time, and requires both the seller and ORD.NET to co-sign the sale.

Ledger registers the policy as ORD.NET Passthrough Policy:

tr(@0/**, multi_a(2, @1/**, @2/**))

• @0 seller key-path key (Ledger account m/86'/0'/n')

• @1 seller script-path key (Ledger account m/86'/0'/(n+1)')

• @2 ORD.NET co-signer key-info:

  [52266fd1/86'/0'/0']xpub6D1FCxdiqLnCTPXY8ddYjjms3dvnLeD7zNtNPCXG9cKW2A7bdAR5fkjz5Mhzxm85cQX2VKuPAaBoiQuBXWLWJwsiSjgxQ3cKbVGqkpzNre2

This key-info derives the ORD.NET public key used in the tapscript:

d2dc3222298e2a5f4e1c7d702fae2bcf7821cc0a095a478b95c62195b0df7398