How a crate movesSEC 004

Four steps, no custodian

01 — Declare

The sender itemises any mix of assets — tokenised stocks, memecoins, native ETH — onto one manifest. Everything on it moves into a non-custodial escrow contract on Robinhood Chain. No owner keys, no backdoors. Not even for us.

02 — Seal

Your browser generates a one-time keypair. The public half is hashed and committed on-chain with the drop. The private half goes into the link after the # — and URL fragments never leave the browser. No server ever sees the key. Lose the link, lose the crate.

03 — Crack

The recipient opens the link and cracks the seal. Their browser signs a claim with the fragment key and hands it to a relayer, which pays the gas and submits the transaction. The escrow verifies the signature against the commitment and releases every line on the manifest. One click, no wallet balance needed.

04 — Recall

Thirty days pass without a claim and the sender can pull the whole crate back. Escrow, not limbo.


Explorer: robinhoodchain.blockscout.com

Chain: Robinhood 4663 / explorer: robinhoodchain.blockscout.com
Against the referenceDIFF

The single-asset version of this primitive exists and works. CRATE extends the drop struct to hold an array of assets — one crate, many things. Stock plus memecoin plus ETH, same shipment.

struct Drop {
  address creator;
  bytes32 claimHash;
  address[] tokens;  // address(0) = ETH
  uint256[] amounts;
}

Plus a multi-swap path in createDropWithEth: one ETH payment fanned out into N assets before escrow.

One crate, many things — that is the whole pitch