I just set up a Subgraph, and after running for half a day it started hitting RPC rate limiting… the data just got stuck at a certain block number and won’t move. I’m really fed up with these node providers—when you check the logs, it’s all 429 errors from throttling. The truth is, no matter how powerful the indexer is, when you run into a “public RPC that costs a lot and still restricts access,” you have to accept defeat. With rate-cut expectations picking up recently, the discussion about the U.S. dollar index rising and falling in sync with risk assets has been pretty hot, and on-chain activity has also come back a bit. The more that’s the case, the more likely it is that they’ll cut you off when it matters. Anyway, I’ve learned my lesson now: I spin up a lightweight node myself, then attach an archive node for backups. Keep the data request frequency under control—don’t expect one single channel to carry everything. Back when I was chasing low-cap memecoins, I already ate this kind of loss—if the quote latency is delayed by a few steps, you get eaten. Once you’ve got cost awareness in place, execution won’t feel panicky.