DEV Community

4k TEAM
4k TEAM

Posted on

When on-chain data is unavailable, say so

A dashboard is only useful when readers can tell what it knows—and what it doesn’t.
If a public RPC is rate-limiting a query, or a data source hasn’t returned a verifiable result, showing a precise-looking number anyway creates false confidence.
It’s better to mark the value as temporarily unavailable, keep its source and timestamp, retry carefully, and display it only when it has been verified. A brief gap in the interface is better than a number that looks certain but isn’t.
How do you handle incomplete on-chain data in your Solana tools: hide the metric, mark it as stale, or show its source and last update?

Top comments (0)