Market
One item, one price
Items on offer on baklava-testnet-5, what each one costs, and who is selling it. This is the small reading of the word: there is no quoting and no matching here — an offer is a number somebody wrote down, and taking it is one transaction.
A listed item is the escrow's, not the seller's. While an offer stands the item's owner is an address nobody holds a key for, the same way a registration stake moves into a pool. Marking it as listed and leaving it where it was would let a seller hand it elsewhere while the offer was still standing — so the item moves, and a purchase either gets it or fails.
What is for sale
Newest first, from the index, as of height …. The index says which items are on offer and never what they cost; every price, seller and expiry below comes from the node.
Collections
What exists, whether or not any of it is for sale. A collection is one row however many items it holds, so this is cheap to keep and cheap to ask about.
Who owns one item
An item that has never moved has no row of its own, and its owner is the collection's creator. That is a rule rather than a record, so the node's answer proves two leaves and not one — and an absence on the item does not mean nobody owns it.
Sell one
Three transactions and none of them is signed here. This page never asks for a key or a recovery phrase, and you should not give one to a page that does — it composes the commands and you run them.
1 — put it up
baklava sell -collection <id> -item <n> -price <krumb> -days 30
The item moves to the market escrow, an address nobody holds a key for — the same trick a registration stake uses. Marking it as listed and leaving it with you would let you hand it elsewhere while the offer still stood. Add -token <id> to be paid in a token instead of BKLV; the fee is BKLV either way, as every fee is.
2 — or take it back
baklava unlist -collection <id> -item <n>
The seller may at any time, and anybody may once the offer has lapsed. They are the same transition with two authorizations, which is why there is one command — and the item always returns to whoever listed it.
3 — an offer lapses rather than lasting
baklava sell -collection <id> -item <n> -price <krumb> -days 365
A year is the longest an offer may stand. That is not about storage — an expired listing is still a row until somebody removes it, and nobody is paid to remove somebody else's. It is so an offer nobody is watching stops being a standing bid at a number its author stopped thinking about.
Why a purchase names the price it expects. A listing is keyed by the collection and the item and not by what it says, so cancelling one and listing again at a different number puts a different offer exactly where a purchase in flight was aimed. The transaction therefore carries the price and the asset, and the chain refuses it if either moved. The commands on this page pass -price for the same reason one step earlier: the number you are looking at was true at a height, and the command checks it is still true before it signs.
What is proved here and what is not. Every price, seller, expiry, owner and collection record comes from the node and carries a Merkle path to a signed header. The list of what is on offer comes from an index, which proves nothing and can hide a row — it can never invent one, because each row is then asked of the chain and dropped if the chain disagrees. The pictures come from the launchpad and are hashed in your browser against the commitment before they are shown. The paths themselves are folded by baklava rather than by this page.