SHRIVE docs
This source targets the NU6.3 Ironwood pool and a signature claim that keeps the saved code private. The ZEC API is hard closed. Do not send payment. Rust compilation, live Ironwood receipt, reserve and claim integration, host validation and independent review remain UNVERIFIED. See the Zcash advisory.
Short answers, two sentences each. See How it works for the fuller path.
Yes. There is no keeper. Bring your claim code to Get my pieces, choose the wallet, and submit; you pay the small network fee.
The recipient you choose in the claim form. It may differ from the connected EVM wallet that pays the network fee.
A qualifying Pons buy uses the contract minimum. The separate Ironwood ZEC door requires one note at or above its exact invoice price, with the exact memo. Underpayment does not reserve a code.
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 Pons buy can authorize its normal claim. Each separate qualifying Ironwood note needs its own saved code and invoice. One transaction can never be authorised twice, but two separate buys are two separate chances.
No. The signing library waits for confirmations before it will sign anything, so your code typically arrives well under a minute later, not inside the buy itself. You still have to bring it back yourself to claim.
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.
The site does not connect to your Zcash wallet. Ironwood hides the direct transfer details from public observers, while the watcher sees received amounts and memo hashes. Prior transparent activity, timing and network metadata can still correlate a payment and later public claim.
You do. There is no keeper wallet paying on your behalf; claiming is an ordinary transaction you submit and pay for yourself.
No. The contract marks each claim code used before it mints, so the same code can never produce a second piece.
Connecting an EVM wallet reads its address. A claim requires your later wallet approvals. The site does not connect to your Zcash wallet; you sign the Ironwood payment in that wallet.
A seed built from the pool or the deposit, the claim reference, which numbered claim it was, and the amount, all packed together and hashed. The same 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 claim path is the one in use; the hook slot exists for later.