Fair launch on letscash.fun Deploying on Robinhood Chain Physical AI Infrastructure

Home / Products / Oracle

Oracle
Security

One validator signing its own scores is a database, not an oracle. Attestation requires a quorum of independent signers, and mainnet locking is designed to make manipulating that set expensive.

Mesh Connected Scheme m-of-n Locking Planned

Monitor Runtime

stdout / live

Threat Model

what the design defends
  • Score forgery

    An attestation is only valid if the digest recomputes to the same struct the signer approved.

  • Replay

    Each attestation carries a nonce, and an anchored motion hash cannot be anchored twice.

  • Signature malleability

    Signatures in the upper half of the curve order are rejected outright.

  • Signer capture

    Quorum is enforced on chain, and veRONET locking is planned to raise the cost of assembling one.

Signer Liveness

testnet attestation set
SignerRoleStatusLatency
validator-00Primary attestorOnline42 ms
validator-01Primary attestorOnline67 ms
validator-02Secondary attestorOnline95 ms
validator-03StandbySyncing—
3
Signers Online
2 of 3
Quorum Policy
41 ms
Median Drift
0
Failed Anchors
Testnet trust assumptions

The signer set shown above runs on testnet and is operated by the core team during this phase. Decentralization of the attestation set, and the veRONET locking that secures it, are planned work rather than live guarantees.