CIPHR docs
Short answers, two sentences each. See How it works for the fuller path.
Yes. There is no keeper minting for you: you sign to seal your own visor, then submit the mint from the wallet that bought.
Whichever wallet the pool sent the tokens to in that buy, and the same wallet that signs to seal it and submits the mint. That address is read straight from the chain, never typed in anywhere.
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 in your wallet, so yes, the same way as any other NFT. Nothing about it is restricted or soulbound.
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 sealing and minting only happen when you do them, in a separate transaction you send yourself.
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.
A qualifying buy does not expire, but only your own wallet can seal and mint it. Nothing lands until you do that step yourself, from the site.
The buyer submits and pays for the mint. The Phala CVM produces the signed seal after wallet authentication. First-claim enrollment is unfinished, so the current client refuses to request a deployment or mint transaction until enrollment is available.
No. The contract marks each buy's reference used before it mints, so the same buy can never produce a second piece.
No. Connecting only reads the address and its balance; it never signs anything on its own. Sealing asks for a separate signature, and minting asks for a separate transaction; each one shows you what it is before you approve it.
In the 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 preview. The visor secret itself is different: fresh private randomness generated inside the enrolled CVM, separate from the buy.
No. No V4 PoolManager was found on Robinhood Chain when this was built, so the signed authorisation path is the one in use; the hook slot exists for later.
Then your avatar stays noise to the world and clear to you. That is the point.