These days, on-chain data is once again in a state of "lagging," and many people's first reaction is to accuse the project team of running away. In fact, more often it's a segment in the data pipeline of indexers/Subgraph/RPC that is rate-limited or rebuilding. To put it simply, when you click on the front end, behind the scenes you might have to wait for the indexer to catch up with blocks, then wait for the node to respond, and if a service provider is overwhelmed, they just return a 429 error. What you see is just a blank screen or a spinning circle. Before and after this wave of upgrades, mainstream public chains are once again speculating whether the ecosystem will migrate. I think it's better not to jump to conclusions and instead look at who is supporting the infrastructure and whether their bills are affordable. That's more realistic than worrying about migration. What I don't regret is that before each vote, I always ask: who will actually do this work? Don't let the budget just support a bunch of "seemingly decentralized" single points of service.

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