near-preflight

So far

Loading…

How one check goes

1. The agent asks. It names a token and an amount, and pays for the check.
2. The sentinels simulate. Each off-chain service runs the buy NEAR would sign, then its resales at several delays and sizes, and votes: an allow takes two matching votes of three, one block is enough.
3. The verdict is stored on NEAR. With the sha256 of its evidence and the hash of the one transaction the guard may sign.
4. NEAR signs. On allow, or a warn the owner approved, the guard builds the swap itself and NEAR Chain Signatures signs it.

The evidence replays: the Base-mainnet check shipped in the repository on any machine, a fork check against the team's fork and proof files (replay and attest).

State now

Loading

…

Checks

Newest first. Open a line for its agent, hashes, model decision, signed transaction and how to verify it.

Four lamps, four steps: asked, simulated, verdict stored, signed by NEAR. The fourth lights only when NEAR signs.

Shared blocklist

The guard refuses a check or a buy of these tokens. A sentinel listing names the verdict it rests on; only the owner can unlist.