I’m done. Lately I’ve been running cross-chain data, and it stalls at every turn. I even thought it was my network acting up. After digging for a while, it’s mostly because the Subgraph sync is slow, or because the RPC side is rate-limited—basically, the indexer can’t keep up. I run a cross-chain route; along the way, the data gets stuck, and I can literally watch gas jump around. In the end, I still have to manually refresh and wait. The key is that I treated “simple” as a trap—I thought it was enough to just query directly. Turns out everything still has to be re-run on-chain from scratch, and the cost doubles.

Recently, a lot of people have been comparing RWA with on-chain yield products. They say U.S. Treasury yields are so stable. I’m thinking: sure—let’s not talk about that yet. First, make sure the data stops lagging. Otherwise you can’t even see the real on-chain liquidity, so what’s the point of comparing anything?

Forget it. In any case, on my own cross-chain route checklist, I’ve now added another step: first check whether the indexer update status is up to date; otherwise, just send it back.