Sentinel turns delegation into a bounded mandate — an owner-signed policy that fixes what an agent may trade, where, and with how much. Enforced by Move guards, observable from signature to indexed state.
Readiness
Built on the current Sui stack
The problem
Today the choices are bad: share a key, sign a standing approval, or babysit the bot. Each one trades real control for convenience.
A mandate is an owner-signed, on-chain object that says exactly what the agent may do — which pools, how much, until when — and nothing else. Bounded by Move guards. Revocable in one transaction.
How it works
No seed phrase handoff, no standing approval. Authority is granted as a bounded, revocable object — and nothing more.
Sign a policy that names the DeepBook pools, per-order cap, global budget, slippage, and expiry. The bounds live inside one Sui object you own.
Deposit into a trading vault you control, then mint the agent a revocable trading pass. Your keys never leave your wallet.
The agent trades inside the lines. Every order is checked against the policy at the Move layer and tracked from signature to indexed state.
Capabilities
Sentinel pairs every delegation capability with the evidence that it is working — boundaries first, decoration never.
pools · order side · per-order cap
Name the DeepBook pools and order bounds the agent may use. Anything outside the mandate fails closed at the Move layer.
global budget · slippage · expiry
Hard spend ceilings and expiry live inside the policy object itself, so financial risk is bounded before the first order is placed.
gas · trading pass · vault balance
Sentinel verifies agent gas, the trading pass, and vault funding before autonomous orders are allowed — blockers are named, not implied.
pending → submitted → synced
Every owner action and agent order is tracked from wallet signature to indexed state, including failures that deserve attention.
pause · revoke · rotate pass
Pause or revoke a single mandate with one owner-signed transaction. Wallet keys never leave your control.
digests · events · cursors
Each execution links to its transaction digest and indexed events, so a reviewer can confirm what actually happened on-chain.
Anatomy of a mandate
Scope, budget, readiness, lifecycle, and custody are the actual surfaces you operate in the Sentinel workspace — not mockups.
Scope, budget, expiry, and the agent binding live in a single owner-controlled Sui object — readable by anyone, changeable only by you.
Readiness rail
Autonomous orders stay blocked until every check passes — and the dashboard tells you which one is in the way.
Lifecycle states
Custody boundary
Async Indexing API
Digest recording, waitForTransaction sync, cursoring, and duplicate suppression reconcile every wallet action into canonical indexed state.
1 tx
to pause or revoke a mandate
0
seed phrases or private keys shared
100%
of limits enforced on-chain
4
lifecycle states per action
Under the hood
The scope is intentionally focused: zkLogin, DeepBook, programmable transaction blocks, Move contracts, and indexed state.
Familiar Web2 sign-in that derives a Sui address — onboarding without seed phrases or custodial shortcuts.
The on-chain central limit order book on Sui, and the first execution adapter behind Sentinel policies.
Object-centric guards that enforce scope, budget, and expiry at execution time — not in a backend promise.
Chained, atomic execution paths for vault setup, pass minting, and trading actions.
Records every digest and reconciles it into the canonical indexed state the workspace reads.
gRPC for transaction execution paths and GraphQL for zkLogin verification and flexible event reads.
Define scope and budget, fund the vault, mint the trading pass — then let the agent work inside the lines.