Vigil Logo

VIGIL

Decentralized Liquidation Prediction

Bittensor Subnet Proposal

1
$2.4B

liquidated in DeFi last year

😶 Borrowers had no warning

🤖 Liquidators with private bots won everything

The prediction intelligence exists. It's locked in private bots.

2

What Happens Today

User deposits $100K collateral

Market drops 20%

Health factor crosses 1.0

LIQUIDATED

$10K penalty. No warning.

3

The Solution

Miners compete to predict liquidations

MINERS

Predict which positions will liquidate

VALIDATORS

Verify against on-chain events

TAO

Rewards accurate predictors

Where does TAO come from?

Bittensor network emissions — not users. Like Bitcoin mining rewards, TAO is emitted by the protocol itself and distributed to subnets based on value created.

4

How It Works

Every hour:

1
Validators snapshot at-risk positions
2
Miners predict (10 min window)
3
6-hour observation (starts after predictions)
4
Match predictions to reality
5
Score miners → distribute TAO

Scoring:

Dimension Weight
Precision 40%
Recall 30%
Lead Time 20%
Calibration 10%
5

Key Innovations

Danger Zone Credit

Miner predicts liquidation. User adds collateral. No liquidation.

Was the prediction wrong? Not if HF dropped below 1.02.

→ Half credit for danger zone hits

HF History Tracking

Health Factor = liquidation risk metric.

HF > 1 = safe. HF < 1 = liquidatable.

→ Track HF over time via archive nodes

Rolling 24h Aggregation

5-10 liquidations/day = too noisy for per-epoch scoring.

24-hour window = 50-200 data points.

→ Statistical significance

Lead Time Threshold

Earlier predictions earn bonus — but only if precision > 50%. Prevents wild early guesses.

6

Why It's Verifiable

Liquidations are on-chain facts.

Data Source How
Did it liquidate? Transaction hash LiquidationCall event logs
When? Block timestamp Block header data
Danger zone hit? HF history getUserAccountData() on archive node

What's HF history?

Health metric values over time. Validators query each protocol's risk function (Aave/Morpho: getUserAccountData, Compound: getAccountLiquidity) at historical blocks. If the position entered danger zone, we can prove it.

No subjectivity. No disputes.

Validators verify facts, not judge quality.

7

Business Model

Customer Product Why They Pay
Borrowers Alerts Avoid 5-15% penalty
Liquidators API Better timing
Protocols Dashboard Risk monitoring

"Why don't miners just liquidate themselves?"

Prediction ≠ Execution

• Prediction requires analysis skills and data infrastructure

• Liquidation requires $100K+ capital and MEV infrastructure

Vigil commoditizes prediction. Liquidators compete on execution.

8

Differentiation

vs SN10 (Sturdy)

Sturdy Vigil
Maximize yield (offense) Predict risk (defense)
Continuous optimization Discrete events
Weeks to verify Hours to verify

vs Outside Bittensor

Competitor Gap
DeFi Saver Reactive, not predictive
Gauntlet Centralized, B2B only
Private bots Proprietary

Vigil = First decentralized, predictive liquidation intelligence

9

Round II Plan

4 weeks. Protocol-agnostic architecture. Aave + Compound + Morpho = 65% of lending market.

WEEK 1

Adapter interface
Aave V3 adapter

WEEK 2

Compound V3 adapter
Morpho adapter

WEEK 3

Validator scoring
(works across all)

WEEK 4

Testing + docs
Historical replay

Protocol Adapter Interface

Each protocol defines: prediction window, risk metric, liquidation events. Scoring logic is protocol-agnostic. Add new protocols by implementing one interface.

Future: Maker Support

Maker uses auctions (not instant). Architecture supports 24h window + auction-start prediction. Documented, not built in Round II.

10
Vigil Logo

VIGIL

Decentralized Liquidation Prediction

PROBLEM
$2.4B liquidated with no warning
SOLUTION
Miners predict, validators verify, TAO rewards accuracy
WHY NOW
Novel use case, no existing subnet
WHY US
DeFi expertise, buildable in 4 weeks

Key Innovations:

Faruukku

@faruukku

11