Skip to content

Buying and selling

Outcome: you will know what a listing on this market actually is, why a purchase cannot half-happen, what cancelling does and does not do, and what the product will and will not let you do today.

A listing is one signature by the seller. It binds the output carrying the asset to one outcome: any transaction that spends that output must pay the seller the exact listed price. Nothing else about the final transaction is decided by anyone but the buyer.

Three consequences follow, and each is shown in the product rather than buried here:

  1. The service never holds anything. Your asset stays on your output; your funds stay in your wallet. There is no deposit, no escrow, and no account.
  2. A listing is a public offer. Anyone can settle it at the signed terms. Listing something is publishing it.
  3. Cancelling is withdrawal, not revocation. Cancelling removes the listing from this market, but the signature it published stays technically valid until the asset moves or the listing’s expiry block passes. If you need certain revocation, transfer the asset to yourself; that spends the output and no old signature can ever use it again.

A nonzero expiry is enforced by the Zcash network itself: the signature commits to an expiry block, and the network refuses settlement above that block height. An expiry of zero means the listing does not expire. Removing a never-expiring listing from the book does not revoke its published signature.

One transaction. It spends the seller’s asset output and the buyer’s funds, delivers the asset to the buyer’s address, pays the seller the price, and returns the buyer’s change, all together. Either that transaction confirms and all of it happened, or it does not and none of it did. There is no state where the money moved and the asset did not.

The product confirms a sale only when the configured confirmation policy and qualified protocol delivery evidence agree. A transaction in the mempool is shown as pending and can still fail; a chain reorganization reopens a listing whose settlement was disconnected.

The small amount of ZEC riding on the asset’s output (typically 546 zatoshis) transfers to the buyer with the asset. Listings state it, and prices should account for it.

Floor, volume, and sale counts on the market pages are derived from this service’s open listings and confirmed settlements only, and every market page says so. They are not chain facts and are never presented as such. An empty market shows as empty; nothing is fabricated to look busy. The overview’s cheapest open ask covers every family at once, so it is labelled Lowest ask; a Floor is always one collection’s.

This market is part of the application at zordinals.run and nowhere else. Zordinals and ZRUNES are Zcash protocols, and the wider Bitcoin Universe surfaces treat them as read and explore only: they display and search the chain record, and no marketplace outside this application trades them. If you are looking for somewhere else to buy or sell one, there is not one to point you at.

The Market navigation lists every destination the market serves: Overview, Zordinals, Collections, NFTs, ZRC-20, ZRunes, zkMap, Names and Activity, with Offers, Auctions, Cart, My listings, Relay Router and Licenses alongside them on the advanced surfaces. The list is not written out separately on each screen: every surface reads the same registry, so a destination that is served is a destination you can reach. Names had a page nobody could navigate to until that changed.

The zord and zecscriptions rulesets have separate books; their quantities and prices are never combined, and a ticker that exists under both is two assets rather than one. A deployed page opens an action only when that operation can execute safely.

Each hub reads an asset catalog rather than a page of orders, which is a distinction you can feel: discovery is not capped at the first couple of hundred orders, so an asset with a single standing ask is as findable as a busy one. Search and ordering live in the address bar, so a filtered list can be shared or restored with the back button.

Prices are ranked by the exact ratio of total to quantity, never by a rounded figure, so an eighteen-decimal lot and a whole-unit one sort correctly against each other. Where a price cannot be read the market says so in words. It never prints a zero, because a zero reads as free.

The market distinguishes states that look alike and are not:

  • Nothing matches these filters. The catalog is fine; the query is narrow.
  • Nothing here yet. Known to be empty, because the chain behind it has been read.
  • Not all of it has been read. The index has not covered enough chain to answer. Something missing may simply be in a block nothing has read.
  • This could not be read. A failure, not an empty market.
  • The network being served is not established. Nothing is published and nothing can be signed until the service says which chain it is answering about. A network selector is a preference in your browser; it does not repoint the service.

The ZRC-20 hub (one per ruleset, zord or zecscriptions) and the ZRunes hub share one layout: a table of tokens with the protocol’s activity beside it. On a phone the activity moves below the table.

Search matches the identifier only. On the ZRC-20 hub that is the ticker. On the ZRunes hub it is the ZRune ID, such as 3493055:7; to find a ZRune by name, use Explore, which the hub links to.

Trading period (24H, 7D or 30D) sets the three period columns. They count confirmed sales only. Listings never move them.

ColumnMeaning
Lowest askThe cheapest open listing now, per token (or per base unit, see below)
ChangeFrom the first to the last confirmed sale in the period
VolumeZEC paid across those sales, fees excluded, with the quantity sold
SalesHow many confirmed sales
ListedTotal quantity on sale now
ListingsNumber of open listings

The period columns can say two things that look alike:

ShownMeaning
No sales (volume 0, sales 0)The figures were read, and nobody bought this token in the period
Not availableThe figures could not be read right now. Nothing is known about sales

Period columns cover the whole market, not just the rows on screen, so they are shown but cannot be sorted. You can sort by asset, lowest ask or newest listings.

A price is per token when the token’s divisibility (its decimals) is known. When it is not, the price is per base unit and says so. A price is never shown per token on a guess.

The top line shows Lowest ask, Listed and Listings, the same figures as the hub. Below it are the price chart, the depth chart and the history. The buy and sell panel sits beside them (above them on a phone).

The chart draws confirmed sales only. Each price is what buyer and seller agreed, fees excluded, divided by the quantity sold. A lot of 1,000 units sold for 5,000 zatoshis and a lot of 10 units sold for 50 zatoshis are the same price.

WindowCandle lengths offered
6H1 minute, 5 minutes, 1 hour
1D5 minutes, 1 hour
7D (default)1 hour, 1 day
30D1 day
  • Line or Candles switches how the same sales are drawn.
  • Reset view undoes any zoom or pan.
  • Price data opens the same numbers as a table (time, open, high, low, close, sales). Hovering the chart also shows them in text.
  • Above the chart: last sale, change, high, low, sales and volume for the window.

There is no All button. The service keeps at most 30 days of sales for a chart, so “All” would be 30 days under another name. Sales made through version 1 orders are not included.

What the chart can say instead of a line:

MessageMeaning
No confirmed sales in the last 7DRead correctly; nothing sold in that window
Price history could not be readA failure on this page, not a quiet market. Try again
This window has more sales than one chart can holdPick a shorter window
Showing the history read at (time)The latest refresh failed, so the last good chart stays up

Under Price depth: every open listing and offer, price left to right, quantity stacked upward. It shows how much is for sale at or below each price. It is about open orders, not sales. Depth levels opens it as a table.

LabelMeaning
ListedSomeone put tokens on sale
DelistedA listing was cancelled on this market
Submitted, not yet confirmedA purchase was broadcast; it can still fail
ConfirmedThe purchase transaction confirmed
SettledThe sale is complete and counts as a sale
Reorged outA chain reorganization removed the transaction

The price on a row is the agreed total for the quantity on that row, fees excluded. It is not what one token cost, and not what the buyer paid in total. Each hub only lists its own protocol, so a zord hub never shows a zecscriptions sale.

A ZkMap district is the winning inscription of a block number such as 1500000.zkmap, so it is listed and bought as a Zordinal: the seller’s single signature binds the output carrying the winning inscription, one transaction settles the sale, and the district follows that inscription to the buyer. There is no separate district order type. The rules are in the ZkMap v1 specification.

The Market navigation has a ZkMap destination at /market/zkmap. It shows every district: each winning block number is one card, whether or not it has ever been listed. Blocks nobody has claimed are not cards here; they stay in the block map and the mint flow.

  • All (the default), Listed and Not listed choose the cards. Listed districts always come first, across every page: first the ones you can buy now, then listings that are pending or cannot be bought right now, then the rest.
  • A district that is not listed shows no price and no Buy button. It is never shown as free, and a price filter never matches it.
  • A district whose winning inscription was burned or moved into a shielded transaction stays occupied and is shown as Not tradeable, with no holder.

The filters on the left apply to the whole market, not to the cards on screen:

  • Search: a block number (780000 or 780000.zkmap) or a winning inscription id. It is exact, so a partial height finds nothing rather than near misses, and 007 is refused because it is not how a block number is written.
  • Price in ZEC, exact to eight decimal places.
  • Block range, from one block number to another.
  • Holder address: the districts one address holds right now.
  • Traits: the block traits grouped by section, with a count beside each value. A count is how many districts in your current selection have that value. Unknown and not applicable are counted apart, never as false or zero, and traits that only exist on Bitcoin are listed under Not on Zcash with the reason.

The Holders tab lists the current holders of the selected districts, with how many each holds and lists and the listed value. Clicking one filters the market to that holder.

The order (lowest or highest price, newest claim, block number), the view (grid or list) and the card size are in the page address, so a view can be linked to someone else and the back button returns to it. Changing the card size or the view never reloads the market. If the market moves while you scroll further, the list starts again from the top instead of mixing two moments together.

The toolbar counts the districts that match your filters, all districts, and how many are listed. The floor is the lowest price you can buy at now.

The Floor price chart shows the lowest open ask at each moment. It is rebuilt from the market’s complete record of listings, delistings and sales, so an old listing that is still open counts from the day it was listed.

  • It is ask history. Sales do not draw it, and there are no candles.
  • Between events the floor holds, so the line steps.
  • Where no district was listed, there is no floor and the line breaks.
  • Windows: 24H, 7D, 30D and All. Reset view undoes zoom and pan.
  • If the record grows too long to rebuild, the chart says Floor history is too long to rebuild here and shows no floor rather than a partial one.

Activity lists sales, new listings and delistings, each at the time it happened. A market with no sales says No sales yet.

When the market cannot be read, it says so and offers a retry. That is a different statement from an empty market, and a listing book with nothing in it is not the same as a map with no districts.

The Offers panel is a collection offer on every zkMap district. A buyer offers a price for any one district and signs it once in the Web Wallet; the district is delivered to the buyer’s own address. A holder of any district can then Sell now to the best offer. The sale is one transaction that the seller signs; the network fee and the market fee come out of the seller’s amount, and the panel shows the exact figures before anything is signed.

The buyer’s signature is kept by the market service until a sale uses it, and is never shown publicly. Spending the funds an offer names ends the offer, and the buyer can also cancel it. Offers can be made and accepted with the in-app Web Wallet; other wallets are told so rather than shown a button that cannot work.

Tick the box on any district you can buy, or Select all loaded to take every buyable listing on screen. The bar at the bottom shows the count and the exact total. Each district is still its own transaction: you approve each one, each one succeeds or fails on its own, and a purchase that went through is never repeated. If one fails, the others are not undone.

A district listing shows its block number, its picture and a link to the district itself, above the signed terms rather than instead of them. The name comes only from a current winning claim. If the inscription has since lost its block number, the page says so: it can still be bought, but it is not a district. If the claim simply cannot be read right now, the page says that too, and does not present an unreadable claim as an invalid one.

The next lot-ask version lets a seller name one exact total price in zatoshis for the whole lot. Token decimals change the displayed quantity, not that price. A lot of two tokens has 2, 2,000,000, or 2,000,000,000,000,000,000 base units for tokens with 0, 6, or 18 decimals; the same 1,000-zatoshi lot price still costs exactly 1,000 zatoshis in every case, before the buyer’s separately reviewed transaction costs.

The buyer takes the entire listed quantity. This change does not open partial fills, bids, or auctions. Existing version 2 asks keep their original signed per-base-unit price; they are not silently converted to the new contract. See order versions.

Read the complete quantity and the total lot price as separate figures. The candidate interface preserves every digit of large quantities and keeps the quantity distinct from the price on narrow screens. Display formatting does not round the amount being bought or change the signed total.

A ZRC-721 item is traded as the inscription that minted it, because that is what it is. An NFT listing is a version 2 item ask with protocol zrc721, signed by the holder’s wallet over the inscription’s carrying output exactly as a Zordinal ask is. The collection key and the token id are not in the signature; they are facts the indexer proves about that inscription, and the market checks them when the listing is admitted, every time it is revalidated, when a buyer prepares a purchase, and again before a sale is called delivered.

What a wallet shows you when you sign or buy is the physical truth: the inscription id and the outpoint that carries it, the price, and the recipient address. In the asset composition the item appears as zerdinals:<inscription id>, because the item and the inscription are one thing; there is no second entry for the NFT. A listing whose output carries anything besides that one inscription is refused.

From an item’s page at /nfts/:key/:tokenId, or the collection’s market page at /market/nfts/:collectionKey, you can:

  • Buy a listed item at its asked price, through the same purchase paths as a Zordinal.
  • Offer on an item, or on any item in a collection. As with every v2 offer, the seller signs at acceptance; an offer does not settle itself.
  • List an item you hold, and cancel a listing, with the same meaning cancelling has everywhere here: withdrawal from this book, not revocation of the signature.
  • Sweep several listed items of one collection through the cart.

A watch-only address sees all of this and can do none of it: listing, offering and buying need the wallet that controls the output.

A sale is delivered when two independent things agree: the settlement transaction has reached the configured confirmation depth, and the indexer reports the item at the buyer’s output under the same collection and token id the listing named. The receipt the product shows (market-nft-settlement-receipt-v1) carries both the inscription transfer receipt and that item evidence. A transaction id alone is not delivery, and if either proof is missing the outcome stays unresolved.

Floor, listed count and volume on NFT pages are this service’s own open listings and confirmed settlements, as on every other market page here, and are never chain facts. Anything shown from a collection’s off-chain metadata is labelled off-chain and plays no part in a sale.

Shielded NFPT items are a different family and are not traded here. The NFTs category links to their public directory so they can be found; no buy, list or offer action exists for them, because no proof of shielded settlement exists that this market could verify.

The NFTs category also carries a directory of collections reported across Zcash, so a collection can be found here whether or not this service can trade it. A directory entry records what a project has published about itself: a name, a link, and the protocol it says it uses. It is labelled Unverified until the collection’s identity and protocol are established against Universe-operated chain data, and an unverified entry carries no ownership, supply, volume or price claim. Anything a project reports about itself is shown as reported by the project, next to whatever this service has actually observed, and the two are never added together.

The directory is seeded with eight discovery leads recorded on 18 September 2026: zkSNARKs, ZecBit Genesis, ZADDR, Zec Punks, BITFOOTS, ZecFrogs, ZecCat and Zecutives. Every one of them is seeded unverified, with no collection identifier and with every capability except discovery blocked, and each entry names the evidence that would unblock it.

Capability is answered per protocol, not for the directory as a whole. Each entry says which of explore, mint, transfer, list and buy it can execute, and an entry that cannot execute one names the blocker rather than showing an empty book. Listing, buying and cancelling exist only for ZRC-721 items this service’s own indexer has accepted; everything else in the directory is discovery only.

ZRC-721 is a transparent inscription protocol and is not a shielded-asset protocol. ZIP 226 and ZIP 227, the Zcash Shielded Assets proposals, are Draft: there is no deployed shielded-asset support for this market to trade, and a project describing its collection as ZSA does not create one.

These entries stay discovery only and unverified. The Zcash Testnet acceptance of 18 September 2026 covered the launch economics, not the admission of any of these collections, and ZIP 226 and ZIP 227 are still Draft. Nothing here is deployed on Zcash mainnet.

Names work differently, and the difference matters

Section titled “Names work differently, and the difference matters”

Everything above describes an inscription changing hands: your asset sits on an output, your single signature binds that output to a price, and one transaction settles it. None of that applies to a native name. A name is not an inscription and a name purchase is not an atomic swap, so the three consequences at the top of this page: no escrow, a public offer, withdrawal rather than revocation: do not carry over. Reading them as though they did is the single most costly mistake available on this page.

A name lives in a registry, and the registry is the authority on who holds it. Buying one means paying a registrar and having the registry record the change. Three things follow:

  1. The registrar does hold funds, for a time. Seller proceeds and refunds to a losing buyer may sit as a registrar credit rather than returning to your wallet on their own. The generic promise that this market never holds anything is a promise about inscription trading and is not true of names.
  2. A credit is not a refund. A credit is a balance the registrar owes you. Getting it out is a separate, supported withdrawal, not something that happens automatically on chain.
  3. Payment is proved by observation, not by your having paid. A payment URI, a QR code, a wallet that says it sent something, or a button that says “I have paid” are none of them evidence. An operation reaches settled only when the payment has been observed and the registry itself has been read back.

The states are distinct and the product shows them as such: prepared, awaiting payment, paid, settled, and separately conflict, expired or failed. Paid is not settled: a competing buyer can still win the name, and then what you have is a credit and a recovery path rather than a name.

Two registries are served and they are separate scopes, not two views of one list. The same label in each is two different names with two different owners. zcashme-zns has no listing or purchase protocol at all: its resolve, register and manage entry points are offered and its market is not, which is a property of that registry rather than an outage.

Signing a registry command is also not the same capability as spending funds. The registry key that authorises a name command and the key that moves your ZEC are different keys, and one never stands in for the other. Mainnet and Testnet registries are separate signature domains besides: a command signed for one is not valid on the other, by design.

After a reload or a lost response, return to the existing execution reference and check its status before starting another purchase. Reopening that execution does not prepare another trade, request another signature, or submit it again. An error or timeout does not establish that the earlier purchase failed.

For a confirmed ZRC-20 purchase, the product checks both the inscription transfer and the token settlement under the selected ruleset. They must describe the same delivery. A transaction identifier alone is not delivery evidence; if those proofs are unavailable or disagree, keep the outcome unresolved.

These recovery and display checks belong to the source and testnet candidate. They do not establish production availability; use the release status below.

The source and public-testnet campaigns include working wallet and marketplace journeys. They do not establish which release the public site is serving. The production inspection on 17 September 2026 found an older product release and an indexer missing the current market receipt contracts and replay identity evidence. Production marketplace qualification remains incomplete.

The NFT journeys above are part of the same source candidate and follow the same rule: each action opens only where its own release evidence and dependencies are healthy, and the page names the blocker otherwise.

Creating a listing requires a wallet qualified for that operation. A published listing alone does not prove that execution is available: preparation and new submission also require an explicitly configured confirmation policy, healthy dependencies, and matching release evidence. An unavailable book must not be shown as an empty book.

A fixed-price Zordinal purchase has two independent paths. A connected wallet can review and sign its funding input. The pay-from-any-wallet path creates an exact ZEC invoice and, after confirmation, combines those funds with the seller’s already sealed authorization. The service never signs the seller’s asset input. Each path opens only when its own release authorization and dependencies are healthy. Until then the product shows the precise blocker instead of offering a path that cannot finish. When one path is open and the other is not, the listing says which one is open (for example Open, with a wallet) and names the closed path’s reason once, rather than calling the whole purchase paused. See Pay with any wallet and current status.

Native name operations carry their own prerequisites and they are stricter. A name purchase needs a qualified registrar, an authenticated observation of the payment, and a registry readback before anything is called settled. Where any of those is missing the operation is not offered, and the product names which one rather than presenting a path that cannot finish.

Everything. The listing, its price, the seller address, the settlement transaction, the buyer’s receiving address, and the full history of all of it are permanently readable by anyone, on this site and on every other reader of the Zcash chain. Nothing about market activity is shielded or anonymous. If you do not want an address linked to a sale, use a fresh receiving address and understand the linkage a settlement itself creates.