On-chain data sometimes “lags,” and it’s not necessarily because your internet is bad. In many cases, it’s the indexer/Subgraph waiting for synchronization: when a new block comes in, it first writes to the database and runs the mappings; if there’s a reorganization, it has to roll back and do it again. Then, with RPC rate limiting, the interface has you queued up slowly, and the frontend freezes for a couple of seconds… You watch that K-line and think the sky is falling, but really, everyone is just waiting.


So recently, some people have been criticizing the tagging system as “lagging/misleading,” and I’m not surprised: the longer the data pipeline, the easier it is to end up waiting for confirmations, waiting for completion, and waiting for you to figure out who you’re supposed to trust. Anyway, when I see something abnormal now, I take a deep breath for three seconds first—don’t, just because you FOMO, dump the blame on “on-chain truth.”
View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
  • Reward
  • Comment
  • Repost
  • Share
Comment
Add a comment
Add a comment
No comments