Docs · dependencies
How dependency readings are taken
A project's manifest lists what it depends on. FlexYield reads each dependency itself every 10 minutes and shows the reading, never a self-reported value.
| Kind | What is read | Status words |
|---|---|---|
oracle | the feed's latest round against its own heartbeat | ok when the round is younger than the heartbeat, stale when older, unknown when the feed cannot be read |
sequencer | the chain's sequencer uptime feed | ok up, down when the feed says so |
bridge | the newest event the bridge contract emitted in about the last hour of blocks | ok when there is one, down when there is none, unknown when the chain cannot be read |
rpc_vendor | how many endpoints answer per chain, as counts only | ok, stale or down from the counts; suppliers are not named |
Overdue
A dependency with no reading for 30 minutes shows unknown and says so.
Overall
The worst status wins: down, then stale, then unknown, then ok. Unsupported rows count only when every row is unsupported.
Readings come from public chain data and FlexYield's own supply checks. Add a dependency with the watch_dependency tool; read the raw readings with get_dependencies.