Infrastructure projects (infrastructure type) are not directly aimed at end users like DeFi/NFT; they are more like "behind-the-scenes heroes," providing services such as node services, oracles, Layer2 scaling, wallets, RPC access, data indexing, cross-chain bridges, and more. Whether a project can run stably, scale quickly, and connect well depends on whether these infrastructures are "usable, stable, and in use." In this article, we will discuss: how should we look at data for infrastructure projects?
1. Is the service "really being used"?#
The value of infrastructure projects is reflected in "how much it is used by B-end" — how many developers/protocols have integrated it?
What to look at?
Daily active call volume (Request/Day): Especially for RPC and data indexing services, check how many call requests are made each day.
Number of integrated projects: How many Web3 projects have called its API or integrated its node/oracle services?
Number of on-chain contract interaction addresses: How many contracts have been deployed, how many callers are there, is it concentrated on a few projects, or is it widely used?
Usage volume by infrastructure type classification: Is it more wallet calls? More DEX calls? Is it relied upon by cross-chain bridges?
How to analyze?
Analyze the service call curve, growth trends, and project integration list on its Dashboard / Explorer.
Check if it supports multi-chain and cross-chain scenarios, and whether it can serve multiple ecosystems.
Recommended tools:
Official Dashboard: Platforms like Infura, Alchemy, Pyth, Chainlink, etc., have transparent dashboards.
Dune: Check oracle call frequency, on-chain call addresses.
NodeReal, Tenderly: Real-time call monitoring on tool platforms.
GitHub: Analyze SDK integration volume and developer usage.
2. Is the performance stable & fast enough?#
Infrastructure not only needs to be "usable," but also "stable and fast." Unstable node services, oracle delays, and cross-chain bridge failures can severely impact the user experience of upper-layer DApps.
What to look at?
Response time (Latency): For example, RPC/node service delays, can it be below 300ms?
System stability (Uptime): What is the online rate for the year? Has it reached the "99.99%" level?
Processing capacity (TPS or throughput): Especially for Layer2 or cross-chain bridges, are there peak testing records?
Downtime/incident history: Have there been significant service interruption events? How long did it take to recover? How was it resolved?
How to analyze?
Compare performance curves over different time periods and different off-chain scenarios (stable vs. fluctuating).
Check if it has passed independent monitoring (like L2beat or Status page).
Recommended tools:
L2Beat: Check TPS, data availability, and other metrics for Layer2.
Official Status pages like Chainlink Status, Infura Status.
Third-party service status tracking like Pingdom, UptimeRobot.
GitHub Issue history + community feedback on frequent downtime complaints.
Tip: The "availability" of infrastructure projects = performance + stability; continuous observation is essential, don't just look at single-day data.
3. Who is using it? Is the ecological impact significant?#
Ultimately, infrastructure needs to serve developers and DApps. If leading projects are not using it, then no matter how good the data looks, it lacks ecological impact.
What to look at?
List of ecosystem integration projects: Which leading protocols are using its services? Is it "genuine integration" or just "in name"?
Variety of cooperative project types: Is it focused on DeFi, NFT, or new directions like cross-chain/AI/modularization?
Developer activity: GitHub submission frequency, is there much interaction on issues? Are there active contributors?
Community operation status: Is there a forum, development documentation, activities, support groups, etc., being continuously maintained?
How to analyze?
Check the whitelist of partners (many infrastructure projects will list cooperative agreements).
Look at interaction activity on Discord, GitHub, X platform.
Compare which infrastructure projects serve more leading protocols.
Recommended tools:
GitHub Pulse: Check code submission trends, number of developers.
Discord / X / Farcaster: Observe developer interaction and feedback.
Platforms like DeFiLlama, RWA.xyz, L2beat for cooperative protocol queries.
Project official website "Clients / Partners" section.
Tip: When looking at a project, it's not just about "whether it is used," but also "who is using it." Serving leading protocols itself represents the industry influence and validation value of the infrastructure.
Summary: How to look at infrastructure project data?#
Is anyone using it?
Call volume, integrated projects, interaction addresses, check the real business coverage.
Is it stable? Is it fast?
Stability, response time, TPS, continuously track to see reliability.
Is the ecosystem broad? Are there leading clients?
Check if the service targets are high quality, if developers are active, and if documentation is friendly.
Infrastructure is not a "showcase of technology"; it is the foundation that truly supports the stable operation of the entire Web3 system. By looking at the data correctly, we can determine whether it is a reliable "Web3 infrastructure company."
Welcome to join the community
Feel free to join the community WeChat: BQ221858
Follow us on Weibo: @QuarkMing202
Follow us on Twitter: @xian202766693