I'm not very good at... that kind of work where you can see through the entire on-chain picture at a glance. I mostly focus on node status, block production, and avoiding pitfalls. Recently, I keep seeing people arguing fiercely over "on-chain data." Actually, that chunk you're seeing might already be late: which RPC you're connected to, whether it's under load, whether there's caching; whether the indexer is still catching up on blocks, whether it's only capturing some events... For the same transaction, some see it instantly, while others only get "on-chain confirmation" after half an hour, then start arguing, basically because their information sources are different.



The compliance boundaries for privacy coins/mixers are also causing heated debates. My feeling is: don't rush to use "on-chain proofs" as the final judge. First, ask where the data comes from, how much delay there is in updates, and whether anything is missing. Anyway, my own approach is pretty simple: try to verify critical operations with your own running node, avoid chasing hot topics, and take it slow for peace of mind. 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