Markets sleep.Vigil holds the line.
Vigil watches your collateral, your borrow, and your health factor on the chain's own lending market, block by block, and holds inside the exposure ceiling you set. It does not get tired, and it does not get emotional.
This is the literal read, live
Robinhood Chain block data, polled straight from the public RPC every few seconds. Chain id, block height, and RPC latency below are real right now. The moment $VIGIL launches, this same feed adds live transfers, total supply, and holder count, read directly from the token contract.
Set the ceiling. Watch it hold.
Drag both. This is one illustrative session, the same underlying path each time, reshaped by the two limits you set. Not live position data.
The watch, through the night
Four steps, the same through every session, lit or dark. Scroll to follow the candle along the line.
max_exposure, liquidation_buffer, defined by you before the watch starts. Nothing Vigil decides for itself. Every step after this one operates strictly inside the boundary set here.
Collateral, borrow, and the market's liquidation threshold, read directly from the lending market every block. Not a cached snapshot, the same state everyone else sees.
Continuously, at the roughly 100ms block cadence of the chain beneath it. The threshold is fixed by the market, not by Vigil.
Reduces or closes exposure, only within what you authorized, the instant the buffer is breached, across the full 24/7 watch. On a stalled read, it fails closed: nothing moves.
Three ways to define how far Vigil goes
A mandate is a scope, not a plan you buy. These are three illustrative shapes a mandate can take, narrowest to widest.
The narrowest mandate. Vigil watches a single position and flags conditions inside the boundary you set. It takes no unwind action without a fresh confirmation from you.
max_exposure: low
action: alert-only
A short basket of positions, a standard exposure ceiling, a liquidation buffer that unwinds the position itself. Vigil acts inside the mandate without waiting on a confirmation.
max_exposure: standard
action: auto-unwind
The full basket you authorize, the widest exposure ceiling your mandate allows, a watch that never closes. This is the vigil at its widest honest scope.
max_exposure: mandate max
action: 24/7 auto-unwind
These three scopes are illustrative examples of a mandate, not products, prices, or promises of return.
USDG in, yield out, a gate that never sleeps
Every dollar Vigil watches starts as a USDG deposit into the chain's on-chain lending market and ends behind a fails-closed gate. No staking, no emissions, nothing hidden between the two.
24 bars, one per hour
Vigil is active for the hours you are asleep, and every hour after that. It has no off switch.
On-chain. No surprises.
Every other market closes. It ranks its book, hands the desk to humans, and waits for the bell. Robinhood Chain doesn't. USDG deposits sit inside its on-chain lending market, an EVM rollup on the Arbitrum Orbit stack settling blocks roughly every 100ms, gas paid in ETH. No validator staking, no emissions: the yield is lending interest from that market, and nothing else. A position held there needs a watch that reads at the same cadence the chain settles at, and unwinds the instant the liquidation buffer is spent. Vigil is what that watch looks like when its authority is bounded on purpose, and it fails closed the moment a read stalls.
Honest questions
Is Vigil live right now?
No. The contract, X, and Telegram are all marked TBA below. Nothing on this page is a live trading session.
What is the interactive demo actually showing?
An illustrative simulation of one position's health factor, not a live read and not a backtest of a real market. Moving the sliders reshapes the same underlying session by changing the exposure ceiling and the liquidation buffer.
Can Vigil act outside the mandate I set?
No. The mandate is a boundary, not a suggestion. max_exposure and liquidation_buffer are hard limits Vigil operates inside, not targets it aims for.
What happens if a chain read stalls or fails?
Nothing moves. Vigil fails closed: on a stalled or failed read, no unwind fires and the base is never spent. It waits for a clean read before acting again.
What chain does Vigil run on?
Robinhood Chain, an Arbitrum Orbit rollup, fully EVM, gas paid in ETH, blocks roughly every 100ms. Vigil watches the on-chain lending market USDG deposits sit inside.
Is this financial advice or a promise of returns?
No. Nothing on this page is investment advice, and nothing here promises a return, a specific date, or a specific outcome.
How to be ready
Vigil hasn't launched yet. The contract, X, and Telegram below are all marked TBA. This is what being ready looks like when it does.
A Robinhood Chain compatible wallet, connected and funded, before launch. Nothing to sign yet, just be ready to.
Vigil launches natively on pons_v2, the chain's launchpad. That's where the pool goes live, not a link in a DM.
Confirm the contract address against the one posted on Vigil's official X account when it's revealed. Never trust an address someone sends you first.
Once live, the first mandate window opens and the vigil starts, 24/7, at the block cadence, inside whatever mandate is set.
The chain doesn't sleep.Neither does Vigil.
Vigil doesn't reference a team, a headline number, or a promise about returns. It references a mechanism: a watch that holds a position open, or closed, for exactly as long as its mandate says to, through every session, lit or dark.