Today, on-chain data is "lagging again," my first reaction isn't conspiracy theory, it's: probably 80% of indexers/Subgraphs/RPCs are just catching their breath... The balances, transactions, NFT lists you see—many of them are actually others first helping you "copy and organize" the blocks. When you push your request in, it starts rate limiting: queuing because too many requests, or simply returning responses more slowly. Not to mention some subgraphs are still catching up with blocks; when they're hundreds of blocks behind, it looks like time has been paused.



Recently, before and after that mainstream blockchain upgrade, many people were guessing whether there would be migrations. I feel that whether there is a migration or not is another matter; just during maintenance or forks, RPCs suddenly spike, enough to make everyone in the group joke "the chain is gone again." Joking aside, when I see lag now, I first reduce my requests a bit, don't rush to full-position operations. If I really need to use it, I prepare several RPCs/frontends to avoid my mood crashing from a "lag." Let's talk again next time.
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
  • Pin