What it decided across every incident it has seen
Real captures, feed discoveries and blind tests, counted together. Refusals are the majority and always will be.
0 cleared to trade0 still investigating0 refused
Funds leave a protocol, or a holder moves a block onto an exchange. WAKE measures who absorbs it, prices the move it implies, and subtracts what the market has already done. Most of the time nothing is left, and WAKE holds.
WAKE watches for security incidents, works out which asset actually absorbs the loss, checks whether the market has already priced it, and trades the gap on Bitget with a size it computes itself. It abstains far more often than it trades, and every decision below, including the refusals, was produced by the scheduled agent and committed to the repository.
Every order was placed by the agent itself and capped at $100 of notional. Fills, fees, funding and the net result are read back from Bitget's own position history, not computed by this app; an earlier version priced exits off the mainnet mark while orders filled on the Demo book, which overstated one result, and that is now corrected. No real incident has cleared the risk gate yet, so each position here came from a blind test.
Newest first, across real captures, incidents found on the exploit feed, and blind tests. Pick any one to see the evidence, the challenges it had to survive, and the size that would have been taken.
That is the product. Anyone can short a hacked token. The work is knowing when the move has already happened, and refusing the rest.
Real captures, feed discoveries and blind tests, counted together. Refusals are the majority and always will be.
Contracts deployed after WAKE starts watching, attacked at a random moment, with the answer sealed beforehand.
A stop at two observed sigmas, fees and spread priced in, bounded by a risk budget, by a share of real traded value, and by the venue cap.
The investigator names the mechanism and who bears the loss, and can veto a trade. It can never create one, change a number or choose a size.
Each evaluation, order and exit lands in a hash chained log written by the scheduled run. Editing any past entry breaks the chain.
The same loop runs whether the incident arrived from the feed, from a capture, or from a blind test.
Every hour WAKE reads new blocks on three chains and the public exploit feed, and opens an investigation for anything material. No human files the incident.
WAKE trades only what it can measure. Every refusal and every trade carries its reason, and every result is settled by Bitget.
Open the desk ↓WAKE watches for security incidents, works out which asset actually absorbs the loss, checks whether the market has already priced it, and trades the gap on Bitget with a size it computes itself. It abstains far more often than it trades, and every decision below, including the refusals, was produced by the scheduled agent and committed to the repository.
Every order was placed by the agent itself and capped at $100 of notional. Fills, fees, funding and the net result are read back from Bitget's own position history, not computed by this app; an earlier version priced exits off the mainnet mark while orders filled on the Demo book, which overstated one result, and that is now corrected. No real incident has cleared the risk gate yet, so each position here came from a blind test.
Newest first, across real captures, incidents found on the exploit feed, and blind tests. Pick any one to see the evidence, the challenges it had to survive, and the size that would have been taken.
That is the product. Anyone can short a hacked token. The work is knowing when the move has already happened, and refusing the rest.
Real captures, feed discoveries and blind tests, counted together. Refusals are the majority and always will be.
Contracts deployed after WAKE starts watching, attacked at a random moment, with the answer sealed beforehand.
A stop at two observed sigmas, fees and spread priced in, bounded by a risk budget, by a share of real traded value, and by the venue cap.
The investigator names the mechanism and who bears the loss, and can veto a trade. It can never create one, change a number or choose a size.
Each evaluation, order and exit lands in a hash chained log written by the scheduled run. Editing any past entry breaks the chain.
The same loop runs whether the incident arrived from the feed, from a capture, or from a blind test.
Every hour WAKE reads new blocks on three chains and the public exploit feed, and opens an investigation for anything material. No human files the incident.
Each refusal has a reason attached to it, and so does each trade. The queue below is the whole record, newest first.
Open the desk ↓