Settlement
Four paths, two windows
Being drawn transfers nothing immediately. The position is marked as allocated and the purchaser chooses. A purchaser can never keep both the NFT and the backing.
| Path | Purchaser gets | Depositor gets |
|---|---|---|
| Keep | The NFT | Backing returned, minus the 1% keep-fee |
| Keep and relist | The NFT stays in protocol custody as a new listing, funded by the purchaser's fresh backing | Same net backing return |
| Accept bid | 95% of the backing | The NFT returned |
| Accept bid, settled as token | The same amount, routed through a token buy | The NFT returned |
Windows
Default outcome on finalise: NFT to the purchaser, backing to the depositor. A position can never lock up because someone walked away.
Why relisting is not optional
Relisting settles the old position and creates its linked replacement atomically, without the NFT passing through the purchaser’s wallet. Without that path every draw would deplete inventory and the pool would have to be restocked by hand.
Delivery is defensive
Keeping the NFT is settled strictly — it reverts on failure, so a purchaser whose transfer cannot complete can fall back to accepting the bid instead of losing both.
Every other resolution delivers best-effort. On failure it emits a delivery event and leaves the NFT claimable through a recovery path. A hostile or paused ERC-721 must never be able to brick a draw for everyone else.