Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

Nomad Overview

Nomad is the node network that helps Mirage private transfers settle quickly. Nodes provide liquidity, execute recipient transfers, and get reimbursed only after proving the transaction was completed.

Nomad uses trusted execution environments for sensitive processing. This is one layer in the design, alongside screened operators, escrow verification, node bonds, proof-based reimbursement, and optional multi-routing.

How Nomad Is Used in the Network

  1. Clients encrypt their signal, which contains the recipient, amount, and other details, using the enclave's global secp256k1 public key and send it to the network.
  2. The signal propagates through a libp2p gossip layer, where nodes receive incoming signals and randomly sample them for execution.
  3. Inside each node's SGX enclave, the signal is decrypted and processed:
    1. The enclave validates the escrow contract bytecode
    2. The enclave bonds tokens using one of its internal EOAs
    3. The enclave executes the transfer from another EOA
    4. The enclave builds a Merkle proof for the transfer and collects the reward by submitting the proof to the escrow contract using the bonded EOA

Basic requirements

To run a node, you must meet the following requirements:

  • At least $10k in USDC liquidity
  • Dedicated SGX machine (cloud-hosted)
Interested in running a Nomad node?We can help you get set up and join the network.

Talk to us

Node Revenue

Nodes generate revenue from tips paid alongside signals. Operators can expect each signal to include a tip of a few dollars, and the node will hold the profits until the operator withdraws them. Maintaining good node uptime allows the node to accept as many unsolved signals as possible from the network gossip.

Risk Controls

Nodes run a lightweight enclave that handles sensitive signal processing and execution steps. Mirage does not rely on enclaves alone: nodes must verify escrows, post bonds, execute transfers, and prove completion before reimbursement.

If a node software issue is discovered, Mirage can revoke the affected enclave version so clients stop producing signals for it. Once a mitigation is available, a new signed enclave can be distributed to resume work.