Journal · 9 May 2026
Oracle lag, written for someone who posted collateral
Two prices, one position
A visitor in May had been watching a SOL price on a trading screen and could not understand a liquidation warning that cited a different figure. The oracle binder on the third shelf is kept for that conversation. A lending program does not have to measure collateral by the last trade the reader saw. It measures collateral by the feed named in its own configuration: sometimes a published oracle, sometimes a pool price, sometimes a blend. The sheet’s first line is the name of that feed, copied from the program’s public description and dated.
Lag is the gap in time between the feed’s last update and the moment the reader is looking. In a fast market the gap can be long enough for a warning, or a liquidation, to reference a price the reader considers already gone. The binder does not call this a malfunction on its own. Some programs state that their feed updates on a heartbeat or when price moves by a set amount. The sheet copies that statement when the library can find it, and it leaves the line blank when it cannot. A blank line is a finding. It means the reader should not invent an update rule that the filing does not contain.
Internal price and external feed
Liquidity pools also print a price, implied by the assets sitting in them. That internal price can be pushed by a large swap. An external oracle is slower and, when it is working as published, harder for one swap to drag. A lending program that uses the internal price is exposed to a different risk from one that uses an external feed. The evening circle on 19 November is dedicated to this distinction, with the seminar table and a handout that has one column for each source.
The private reading treats the feed name as part of the position, alongside collateral and debt. Jae-won writes it at the top of the packet so it is not an afterthought squeezed under the health ratio. Readers who have never looked up their program’s feed often find this the longest ten minutes of the sitting, because the public page is dull and the consequence is not.
What the room will not smooth over
The library can show a reader which feed was named on the day the sheet was filed. It cannot promise that the feed will update during the next volatile hour, and it cannot restore a liquidation that has already executed. Visitors who come after a loss still receive a reading of the sheet. The letter distinguishes what the sheet said from what the program did. Those belong in separate paragraphs so grief and filing dates do not get mixed into one sentence.