Recently, people keep asking me, "Why did the on-chain transaction get stuck again? Is it crashing?"… Actually, many times it's not the chain itself being slow, but the "traffic" on the bridge side being congested: the indexer/subgraph hasn't finished processing the new blocks, so when you query data, it's like going through old records; on the RPC side, it's more realistic—rate limiting kicks in and just keeps spinning, especially during peak times when there are many requests, causing wallets/dashboards to be sometimes responsive and sometimes not.



Retail investors complain that the sorting is unfair and that MEV is taking a cut, I can understand that too—clearly they click confirm but feel like they're being queued and cut in line… but it feels more like "upstream adding a lane" plus "downstream information delay" stacking together. Anyway, I now get used to checking data from two sources; if it's slow, it's slow—no need to rush and suspect assets are flying away. That's all for now.
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
  • Pinned