Docs menu

YONDER docs

Pay with Zcash

You can pay for a YONDER piece in ZEC without connecting any wallet, keep a one-time claim code, and claim the piece later to a fresh stealth address. This route buys a piece, not $YONDER tokens. It appears after launch.

Status

After launch

The Pay in Zcash panel says "ZEC payments are not open yet" until the route is switched on. It also needs the operator's server, settlement and storage settings in place before it opens.

How paying works

  1. Open the Pay in Zcash panel, press Create claim code, save the code and press I saved the code. No wallet is connected and no name is asked for.
  2. The site asks NEAR Intents 1Click for a quote that swaps ZEC into USDC on Base, paid to the operator's treasury. You get a ZEC deposit address, the amount to send and a deadline.
  3. Before you pay, press Copy signed quote JSON and Copy secret session recovery, and keep both somewhere safe.
  4. Send exactly that amount from your own ZEC wallet to that deposit address, before the deadline. Confirm the amount and destination in your wallet.
  5. Press Check settlement. When 1Click reports the swap settled, the site reports that your public claim identifier is reserved.

The USDC settles on Base. It is not bridged to Robinhood Chain automatically, and this is not native ZEC on Robinhood Chain.

Your one-time claim code

Your browser creates a random valid signing code before the quote. It sends only the versioned public claim identifier, keccak256(20-byte signing address), to the API. The code itself never enters an API payload. The server stores a SHA-256 digest of the session, then reserves the public identifier after settlement.

Copy and save the code before pressing I saved the code. The site then hides it and shows payment instructions. A saved session can restore settlement status, but cannot restore a lost code. Legacy invoices and reservations need a new deployment and fresh state rollout.

Claiming later to a stealth address

  1. Whenever you are ready, open Claim with a code, paste the saved code and press Claim.
  2. The site connects your Robinhood Chain wallet and derives a fresh stealth address from the same wallet signature as your other YONDER pieces.
  3. The browser signs a versioned EIP-712 message locally with the code. It binds the public identifier, claiming wallet, stealth address, ephemeral public key hash and view tag to this chain and collection.
  4. One transaction calls claimWithCode with the public identifier and signature. The collection mints your piece straight to the stealth address and announces it the same way as every other piece, so Scan my stealth pieces finds it.

The code never enters a claim API payload or transaction calldata. The one transaction needs a little ETH on Robinhood Chain for gas. A failed claim does not consume the reserved identifier.

The honest limit

Limit

The ZEC leg uses a transparent deposit address, so the payment is visible on the Zcash chain. There is no shielded deposit door yet; shielding before you pay happens outside this site.

The code stays private. The public identifier, claiming wallet, stealth recipient, ephemeral public key, view tag and signature appear on Robinhood Chain. The operator sees settlement and reservation data. Settlement relies on the 1Click status service, so this is not a trustless payment route.

What to keep safe

KeepWhy
Your claim codeIt is the private signing key for the reserved identifier. Keep it private and save it before payment.
The secret session recovery valueIt lets you resume settlement status with Resume settlement, but it cannot restore the claim code.
The signed quote JSONYour record of the quote, for any dispute.

Refunds go to the operator's transparent ZEC recovery address and need operator help plus your saved session proof. If you lose both this browser session and your saved code before claiming, the piece cannot be recovered.