SNAG docs
Short answers, two sentences each. See How it works for the fuller path.
No. The keeper submits the mint for you, and the piece lands directly in the wallet that bought.
Whichever wallet the pool sent the tokens to in that buy. 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 library waits for two confirmations before it will sign anything, and the keeper polls, so the piece typically lands well under a minute later, not inside the buy itself.
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.
Pieces simply wait. The keeper works from a saved block cursor and mints every buy it has not seen yet, in order, once it is running again.
The keeper's own wallet, funded separately from anything a buyer does. Buying the token never costs a buyer anything extra.
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 a transaction on its own.
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.
No. No V4 PoolManager was found on Robinhood Chain when this was built, so the signed keeper path is the one in use; the hook slot exists for later.