Minting is not a purchase from a shelf: the piece is inscribed on the blockchain at that moment. That is what makes the states below worth understanding — some of them exist because the chain and the app move at different speeds.
You do not pick the piece
In a mint drop you mint from the collection, and the platform hands you the next available piece. You cannot choose which one, and neither can anybody else — that is what keeps a drop fair when several people mint at the same second.
When you start, that specific piece is reserved for you while your mint is in flight. If it does not complete, the reservation lapses and the piece goes back into the pool. The window is deliberately longer than the platform's own wait, so a reservation never expires while your own mint is still going.
A piece that was withdrawn for review is quarantined and never handed out again — not to you, not to anyone.
How many are left is on the drop itself, live:
37 / 50
The states
| State | What it means | What you should do |
|---|---|---|
| Available | Nobody has minted it | mint it |
| Reserved | Someone is minting it right now | wait a moment and try again |
| Minted | It exists on chain and belongs to somebody | — |
| Pending | The transaction went out, but the piece is not fully visible yet | wait — see below |
| Quarantined | Withdrawn from the drop | nothing; it will not come back |
Why a piece can be pending
Two different things are called "pending", and they have different causes.
The chain has it, the index has not caught up
Your transaction was broadcast. The piece is yours — that is settled on chain — but its inscription number and its origin are assigned by the indexer that reads the chain, and that takes a little while. Until then the piece shows up incomplete.
Nothing is lost and nothing needs doing: the platform re-checks the pending ones periodically and fills in the missing data.
The response got lost on the way back
This one is worth knowing because it looks much worse than it is.
Inscribing a heavy piece — a 3D model of several megabytes — can take minutes. The web request that started it does not wait that long: it gives up after a minute. So the sequence can be:
- you press mint,
- the transaction is built, signed and broadcast — the piece is minted,
- the answer arrives after the web request already gave up,
- and the app never learns that it worked.
The money moved and the piece exists, but your wallet does not show it yet. That is a reconciliation, not a loss.
The platform resolves these on its own whenever the evidence on chain is conclusive. When it is not, a person looks at it rather than guessing — which is why a piece can occasionally take a while to appear instead of appearing wrong.
That check happens on our side, from public chain data. It never needs anything from you: no password, no keys, no seed phrase, no remote session and no reply to a message. If somebody contacts you offering to sort out a stuck mint, it is not us.
What not to do: mint again. If the first one worked, minting again buys a second piece. Check your wallet after a resync first, and if it is still missing, ask from inside the site.
How a piece was acquired
Every piece records how it came to you, and it matters when reading your own history:
| mint | You paid and it was inscribed for you |
| auction | You were the last bidder |
| airdrop | It was distributed to you at no cost |
| claim | You claimed it for free because you held something else |