Skip to content
Deploier

Operate the layer, never read the deals

A settlement layer needs people who keep it running. The operator role is designed so that running the infrastructure gives no view into the business on it.

Operator programme: planned

Relay final states, serve sealed records to the parties who hold their keys and keep the public tape honest, on a layer built so that operators never see what was agreed.

Grow with the network

How operators would be chosen and paid is still open. The design starts from a few principles: rewards should follow the work done, measured against public data anyone can check; operators serve every valid record in order, because choosing whose settlement to relay first would breach the role.

The $DEPLOIER token is expected to play a part in operator bonding and fees. The exact design will be published before any operator joins. Infrastructure providers and custodians are the natural first operators, and interest can be registered today.

What an operator would do

These duties exist today inside the single practice server. The plan is to spread them across independent operators, each anchored to Robinhood Chain blocks that no operator controls.

  • Relay

    Pass signed proposals and acceptances to the settlement contract on Robinhood Chain and report the resulting block.

  • Store sealed records

    Hold encrypted private records for parties who want redundancy, readable only with the view key.

  • Publish the tape

    Serve the public list of commitments and statuses so anyone can check what the layer has settled.

  • Raise the alarm

    Flag a commitment that does not match the contract state, or a relay that stops answering.

“A market needs two things from a settlement: proof that it happened, and silence about what happened. We keep the first public and the second with the parties.”
Deploier design principleFrom the litepaper, section 3

What an operator can never do

The design goal is that a dishonest operator can stall at worst, never steal or spy.

Read terms

Records are opened with view keys the operator never receives.

Forge consent

Acceptances are wallet signatures. An operator cannot produce one.

Rewrite history

Commitments and final states are anchored to chain blocks that no operator controls.

Interested in running a desk?

Tell the team who you are and what infrastructure you operate today.

  • Earned by uptime

    Rewards follow measurable work, not stake size alone.
  • Neutral by rule

    Every valid record is served in order.
  • Open to qualified firms

    Infrastructure providers and custodians first.

This form sends nothing to our servers and stores nothing. Pressing the button copies your message and opens @deploier on X, where you paste it into a direct message. The team will never ask for a seed phrase, a private key or a payment.