Today I got "on-chain data" tricked me again... I was staring at a transaction in the browser for half a day with no movement, almost thought I accidentally didn't send it, but then switching to a different RPC immediately showed it. Basically, what you see on the chain isn't necessarily slow because the chain itself is slow; it could be node synchronization, RPC queuing, or indexers still sluggishly scanning blocks, especially during congestion or L2 batch settlements, creating a whole "I clearly already sent it" illusion.



My partner also complained to me: You keep saying you're surfing in the mempool every day, how come you're still fooled by the "truth of delay"... I don't know either, but every time I review, I can write one sentence: Don't trust a single source, check multiple sources, and keep your emotions in check.

Recently, the NFT royalty war also resembles this logic: the transaction/revenue data you see is sometimes a product of platform rules + indexing standards, not necessarily absolutely fair and transparent on the chain. That's all for now, I'll catch up on sleep tomorrow.
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