Glossary
Asset (asset id)
Section titled “Asset (asset id)”The canonical Counterparty asset id, named (RAREPEPE) or numeric. Every route
keys on it. A subasset’s longname (asset_longname) is display metadata only.
Edition
Section titled “Edition”Most assets here have many units (RAREPEPE has 300), so an asset page is an order book, not a single item. Trades move one unit per asset UTXO.
Raw quantity
Section titled “Raw quantity”An integer count of the smallest unit, sent as a decimal string. One indivisible
unit is "1"; one divisible unit is "100000000".
Asset UTXO
Section titled “Asset UTXO”A Bitcoin output that carries an attached Counterparty balance. Every listing
sells exactly one unit on its own asset UTXO, identified by txid and vout.
Typically 330 sats.
Attach
Section titled “Attach”A Counterparty transaction that moves units from an address balance onto an asset UTXO. It costs a Bitcoin network fee and may cost an XCP fee, which stays a quote until the attach is parsed.
Prepared unit
Section titled “Prepared unit”One unit already attached on its own asset UTXO, confirmed and indexed, so it can
be listed without broadcasting anything. See GET /v1/address/:address/inventory/prepared.
Detach
Section titled “Detach”A Counterparty message that moves every attached balance a transaction spends to one explicit address, as an ordinary address balance.
Detach delivery
Section titled “Detach delivery”The default checkout delivery mode. Output 0 of a settlement is an encrypted detach
OP_RETURN naming the delivery address, so the buyer receives an address balance,
not a new asset UTXO. One detach delivers every unit in a cart. The delivery
address can be any Counterparty address family.
Attached delivery
Section titled “Attached delivery”The purchased balance stays on a new asset UTXO at the trading address. Checkout supports this for a single acquired unit. The retained BTC is shown separately from fees in the quote.
Signing, delivery, and source addresses
Section titled “Signing, delivery, and source addresses”The three address roles. Signing is P2TR or P2WPKH; delivery is any family; source (the balance an attach spends) is P2PKH, P2WPKH, or P2TR. See Authentication.
Listing
Section titled “Listing”A seller’s SIGHASH_SINGLE|ANYONECANPAY signature over one asset UTXO and a
payment output worth the price, held (encrypted) by the market until a buyer
completes it.
Preflight
Section titled “Preflight”A server-side draft that composes and verifies a transaction for you to sign. Listing preflights are durable and idempotent; quotes and accept preflights reserve nothing.
The result of POST /v1/fills/request: an unsigned checkout PSBT that lives about
three minutes and reserves nothing. The first valid signed completion wins.
Whoever completes a trade: the buyer of a listing, or the seller who accepts an offer. The taker pays the 2.5% (minimum 1,000 sats) marketplace fee.
Funding slot
Section titled “Funding slot”A clean BTC output worth exactly an offer’s price, named
funding_slot_id = "<txid>:<vout>". One slot pays for one purchase, however many
policies or targets it backs.
Exact-target offer (exact_offer_v1)
Section titled “Exact-target offer (exact_offer_v1)”An offer the buyer has pre-signed for specific asset outpoints with SIGHASH_ALL.
The named seller signs their input and the market broadcasts, without the buyer.
Exact authorization
Section titled “Exact authorization”One such buyer-signed settlement for one asset outpoint. A snapshot: a new or moved outpoint needs a new authorization.
Counter
Section titled “Counter”A seller’s private listing addressed to one bidder, at least 1,000 sats above
the offer. The bidder fills it through checkout with counter_id.
Collection offer (funded_policy_offer_v1)
Section titled “Collection offer (funded_policy_offer_v1)”An offer on any unit matching a policy (asset, collection, series, artist, year, supply). The buyer signs a zero-fee version-3 funding parent; any holder of a matching attached unit can accept, co-signed by the market signer.
Policy
Section titled “Policy”The canonical eligibility object a collection offer commits to: scope,
asset, collection, max_supply_units, min_supply_units, issued_year,
series, artist, absent keys null.
Funding set
Section titled “Funding set”A collection offer’s funding inputs plus one anchor. Its 1..100 alternatives all spend it, so at most one can fill.
Anchor
Section titled “Anchor”A 330-sat market-owned output that every collection-offer funding parent also spends, signed by the market only at acceptance. Spending it lets the market invalidate that funding set’s parents on-chain; the parent recreates it on fill.
Market signer
Section titled “Market signer”The service that co-signs a collection-offer acceptance only while the offer is live, not soft-cancelled, and the unit matches.
Soft cancel / hard cancel
Section titled “Soft cancel / hard cancel”Soft cancel asks the market signer to refuse an offer (free, instant, trusts the market). Hard cancel spends the funding on-chain (costs a fee, trustless).
CPFP child
Section titled “CPFP child”A child transaction that pays extra fee for its parent. Exact-offer acceptance may include one paid from the seller’s proceeds; a collection offer’s acceptance child always pays the whole package.
Journal
Section titled “Journal”The market writes every finalized transaction’s exact bytes before it broadcasts,
and rebroadcasts those same bytes on recovery. A 202 means journaled but still
relaying.
Session
Section titled “Session”A 24-hour bearer token (x-session-token) proving control of one address,
obtained by a verified message signature. It never authorizes spending.