FAQ

Yes, for the buy itself. It is an ordinary transaction anyone can read, the same as any swap. Your piece lands at a fresh public stealth address. A main-wallet claim or top-up directly links that address to you.

Yes. Open Get my pieces, sign once to build your stealth keys, then submit the mint yourself. Your wallet pays the small network fee, the same as any transaction.

Not your regular wallet. The piece mints to a brand new, one-time stealth address derived from your keys, one that has never appeared on chain before. You scan for it, and later move it, from Get my pieces.

Only a buy at or above the collection's minimum. Smaller buys are ordinary swaps like any other, and never bring a piece.

Once minted, it is an ordinary ERC-721, so yes, the same way as any other NFT. Nothing about it is restricted or soulbound. You may want to move it out of the stealth address into a wallet you use day to day first.

Each qualifying buy is its own transaction and can bring its own piece. One transaction can never be authorised twice, but two separate buys are two separate chances.

No. The signing route waits for two confirmations before it will sign anything, and the mint itself is a separate transaction you submit afterward, so the piece never lands inside the buy's own transaction.

Robinhood Chain, chain id 4663, an EVM chain where gas is paid in ETH.

No. Nothing is deployed, and no address exists on any network yet.

Nothing is lost. The buy's proof lives on chain, not in a queue, so you can open Get my pieces and submit the mint whenever you are ready, using the same buy.

You do. Your own wallet submits the mint after it is authorised, so you pay the network fee, the same way you would for a swap. There is no keeper or relayer paying it for you.

No. The contract marks each buy's reference used before it mints, so the same buy can never produce a second piece.

Connecting only reads your address and balance; it never signs anything on its own. Building your stealth keys takes one extra signature, made once, and neither that signature nor the keys it derives ever leave your browser.

On this site's preview, a seed built from the pool, the buyer's wallet, which numbered buy it was, and the amount, all packed together and hashed. The same four inputs always give the same seed and the same piece.

Yes. The mint destination and token metadata are public, and your main-wallet claim links the destination to you. You claim it from Get my pieces with the wallet you bought with.

It hides where your piece lands from anyone reading only the ERC-5564 announcements. Your buy and your mint stay public, and because your own wallet sends the mint, a careful observer can link that wallet to the stealth address. See What is private, what is public.

A key your browser derives from one wallet signature, alongside your spending key. It lets the site recognise which announcements are yours, so it can find your pieces. See Finding your piece.

No. They live in page memory only, are never sent to a server and never saved to storage, and they are cleared when you switch account, switch chain or disconnect.

Connect the same wallet account on the same chain, sign the same message, and press Scan my stealth pieces in My pieces. Your keys are rebuilt from that signature, so there is nothing to import.

A shared, standard contract that logs each stealth delivery: the stealth address, an ephemeral public key, a view tag and which collection and token it is. The canonical Announcer is already live on Robinhood Chain, and YONDER uses it rather than a contract of its own.

No. There is no account, no email and no name anywhere in the flow. Your wallet and your keys are all you need.

After launch, holders of a YONDER piece can move $YONDER to a fresh stealth address and later scan and spend it with the same keys. See Make your $YONDER private.

No. Amounts, balances, senders and destinations stay public on chain. Stealth addresses reduce address reuse; they are not a mixer.

Moving a piece or spending tokens from a stealth address is its own transaction, so it needs a little ETH for gas. Topping it up from your main wallet publicly links the two, and a private relay is in development.

The ZEC door is closed. The proposed 1Click route creates a private signing code in your browser before the quote and sends only its public address-derived identifier to the API. Save the code before payment. A saved session can restore settlement status, but it cannot restore a lost code. See Pay with Zcash.