LlamaRisk

LlamaGuard PT Oracle

Internal monitoring | PT-srUSDe-22OCT2026 shadow on Ethereum (chainId 1) | data refreshes every 60s

Implied rate EMA ()
Pool proportion EMA ()
stressed 2.5× | 0.96 trading edge
Shadow
what automation would aim for
Real d
steward-set
Deviation

Implied rate EMA ()

Every AnswerUpdated round from the shadow's LlamaGuardOracle: the EMA of Pendle's lastLnImpliedRate. This is the input everything below derives from.

LlamaRisk

Shadow vs real d

, recomputed at every EMA round; the published and steward lines only move on writes.

LlamaRisk

When the two lines sit close together, the humans and the algorithm agree on the fair rate; a steward update stepping the real d toward the shadow's continuously-computed target is the agreement made visible.

Price deviation vs the ±30 bps publish band

at every EMA round, using the real adapter's d. Inside the shaded band the discount workflow stays silent by design; it would publish the moment the line leaves the band.

LlamaRisk

This chart is the discount workflow's entire decision, drawn over time. While the line stays inside the band the shadow correctly publishes no discount updates; the moment it leaves the band, a publish fires on the next 4h run.

Write log: everything the shadow has published

Discount-rate writes ()

IdTime (UTC)New rateReferenceTx

E-Mode risk-parameter writes ( records, batches)

IdBatch Time (UTC)LTVLTLBTx

EMA rounds ( total, hourly)

RoundTime (UTC)Implied rate EMAΔ prevGap to prev roundTx