I set a rule for myself: on-chain data just needs to "pause for a moment," don't rush to curse the project team for running away, and don't click confirm impulsively. Many times it's not that the chain is broken, but that the indexer/subgraph is catching up with blocks, or RPC is being rate-limited. What looks like "balance not changing, NFT missing" on your side is actually just data not yet fed to the frontend. To put it simply, the blockchain is the fact layer, and the frontend is the transporter. When the transporter gets tired, it will be a bit slow.

Recently, there's been more noise about NFT royalties. Creators say they can't make a living, and trading platforms say liquidity is more important... I find it pretty annoying too, but one thing is very realistic: what you see as "transactions/royalties/positions" are often just the results of data reads. If reading is slow, it easily triggers emotions and misjudgments. Anyway, when I encounter lag, I just switch to another RPC, wait two minutes, then check on the blockchain explorer. I’d rather be slow than have to write an apology statement later. That’s it for now.