LOCKET docs
Short answers, two sentences each. See How it works for the fuller path.
Yes. Once your buy clears, sign once to seal your own hidden trait and submit the mint yourself. LOCKET has no keeper doing that step for you.
Whichever wallet the pool sent the tokens to in that buy, and that same wallet has to be the one that signs and sends the mint, since the contract only accepts the credited buyer as its sender.
Only your first buy at or above the collection's minimum. LOCKET mints once per wallet for life, so a later qualifying buy from the same address never brings a second 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. Selling it clears its seal; the new holder makes their own.
Only your first qualifying buy can ever bring a piece. The contract remembers your wallet as claimed the moment you mint, so a second buy, however large, will not authorise a second piece.
No. The signing route waits for two confirmations before it will sign anything, and then it is on you: sign once to seal your trait and send the mint yourself. It can follow within moments of your buy, but it is a transaction you send, not something that happens on its own.
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 can be authorised or minted until it is back. Your buy stays safely on chain either way, and nothing about it expires while you wait.
You do. The standard buy claim requires the authorized buyer wallet to send the mint transaction and pay its gas, the same as any other on-chain action you take.
No. The contract marks each buy's reference used, and your wallet claimed, before it mints, so the same buy or the same wallet can never produce a second piece.
No. Connecting only reads the address and its balance; it never signs a transaction on its own.
Its public face: 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 public face; this is the planned on-chain art, which the deployed contract does not draw yet. Your sealed trait is separate: you choose and encrypt it yourself, so no seed decides it for you.
The LOCKET server relays encrypted data. Lit TEE, RPC and operator setup are trust boundaries. Live decryption remains unverified.