Skip to content
Deploier

One deal, two layers, no leak

A private record only the parties can open, and a public commitment anyone can verify on Robinhood Chain.

The Deploier settlement layer splits every deal into two parts. Robinhood Chain supplies the clock, the finality and the assets. Deploier supplies the discipline that keeps the private and public layers consistent: five steps, each one a signature or a public fact. In practice mode the desk records the agreement; with the escrow deployed, the same steps move the assets.

Runs in practice mode today
Parties

Maker desk

signs the proposal

Counterparty

signs acceptance

Reviewer

holds one view key

Public

reads the tape

Private records

Settlement terms

both wallets, both legs, memo

Salt

16 random bytes, never published

View key

opens this one record only

Robinhood Chain
Public tape: commitment hash · status · block
blkblkblkfinalblkblkblk
Parties sign; the private record stays with them; Robinhood Chain blocks time-stamp only the commitment and its status.

Propose and commit

  • The maker names one counterparty wallet and two legs, for example 50,000 USDG against 150 AAPL stock tokens, and signs the terms in plain words.
  • The terms and a fresh 16-byte salt are hashed with keccak256. The hash, the status proposed and the current Robinhood Chain block go on the public tape. Nothing else does.

Share and accept

  • The maker receives a view key for this one record and passes it to the counterparty through whatever channel they already trust.
  • Only the named counterparty's wallet can accept. Its signature flips the status to settled and stamps the block at which that happened.

Verify

  • Either party, or a reviewer given the key, recomputes the hash from the terms and salt and checks it against the public entry.
  • If one character of the terms had been changed later, the hash would no longer match.

Rules that hold for every participant

The layer is useful only if its rules are the same for everyone and can be read by anyone. These are the rules the practice desk enforces now and the contracts will enforce later.

Consent

  • A proposal names exactly one wallet. No one else can accept it, and it cannot be accepted twice.
  • Until acceptance, the proposing wallet can withdraw. After acceptance, the record is final.
  • Wallets sign readable text that states the action, the amounts and the chain id, with a one-time nonce.

Data

  • An unaccepted proposal lapses after 24 hours, so stale terms cannot be picked up days later at an old price.
  • A settlement exchanges one asset for another. Same-asset legs are refused as meaningless.
  • The server keeps only a SHA-256 of each view key, so a database leak does not open the private records.

What changes with the contracts

Practice mode records the agreement. The settlement escrow moves the assets too, atomically: both legs settle in one transaction or neither does.

Atomic delivery against payment

The escrow holds leg A from the proposal and releases both legs in the same transaction the named counterparty delivers leg B. If any transfer fails, nothing moves.

Commitments on-chain

The commitment is stored in the escrow, the registry or the issued token itself, so the public tape is the chain and not a server.

An honest limit

Token transfers on Robinhood Chain are visible to everyone. The contracts keep terms and memos private, but the token legs (assets, amounts, wallets) are public like any transfer; hiding amounts needs a shielded design that is a separate project.

What the public layer carries

  • Decentralized clock

    Every status is stamped with a Robinhood Chain block number, which no single company controls.
  • Readable rules

    Formation, acceptance and expiry are documented on this site and in the litepaper.
  • Open verification

    Any holder of the terms and salt can recompute a commitment without asking anyone.
Live from Robinhood Chain

Latest block

reading…

chain id 4663

Gas price

–

eth_gasPrice

ETH / USD

–

native gas asset, spot

Connect

Open the practice desk and watch the public tape and your private record side by side on one screen.

Build

Use the commitment rule and the signed-ticket flow to design an application that settles privately.

Run

Read the planned operator role: relay final states and serve sealed records without reading them.