IoTeX Foundation: How to Ensure the Security and Efficiency of DePIN Networks with Decentralized Verification?
TechFlow Selected TechFlow Selected
IoTeX Foundation: How to Ensure the Security and Efficiency of DePIN Networks with Decentralized Verification?
This article delves into the issue of decentralized verification in DePIN, critically analyzes existing solutions, and proposes innovative approaches to ensure scalability without compromising security and decentralization.
Navigating Web3 tides with focused insightsAuthors: Raullen Chai, Andrew Law
Translation: TechFlow
Decentralized Physical Infrastructure Networks (DePIN) represent a transformation in how we plan and organize real-world systems, spanning sectors such as energy, transportation, and telecommunications. By combining blockchain, cryptocurrency, and smart contracts with smart devices, DePIN enables the coordination of physical infrastructure in a decentralized, peer-to-peer manner. As a16z's Guy Woulard pointed out, the key to DePIN’s success lies in solving one core challenge: ensuring trustworthy validation of geographically distributed service nodes without centralized management. This article dives into the issue of decentralized verification in DePIN, critically analyzes existing solutions, and proposes innovative pathways to guarantee scalability without compromising security or decentralization.
The Rise of DePIN
DePIN leverages the power of blockchain and smart contracts to build open markets for services rooted in physical infrastructure. Imagine an energy-based DePIN: households equipped with solar panels could potentially generate electricity and deliver surplus power directly to neighbors. Enabled by blockchain and executed via smart contracts, these energy transactions can be automatically recorded and settled. At the heart of this process are IoT devices—such as batteries and other microgrid-connected hardware—that make it possible for households to distribute energy in a trusted, direct peer-to-peer fashion, without utility companies acting as intermediaries.
These decentralized physical infrastructure networks have gained increasing attention across industries in 2023. By marginalizing centralized gatekeepers, DePIN promises greater efficiency, lower costs, expanded accessibility, and increased individual agency.
The Architecture of DePIN
Decentralized physical infrastructure relies on a complex technology stack that integrates hardware, connectivity, middleware, blockchain-based smart contracts, and network or mobile applications.
Zooming into a typical DePIN network (such as DIMO, Helium, WiFimap, or GeoDnet), they usually involve three roles:
-
Service Nodes: A set of servers or devices that provide services or utilities, such as WiFi/5G, environmental data collection, or energy production.
-
Middleware: A layer primarily dedicated to verifying whether service nodes are functioning properly. It ensures accurate representation and reporting of real-world activities and events from service nodes to smart contracts, which may be closely tied to how DePIN tokens operate.
-
End Users: Everyday individuals or business communities who actually use the utilities provided by service nodes or devices. The middleware is responsible for measuring the quality of service from nodes by tracking certain metrics. In their absence, the following issues may arise:
-
Self-dealing: Participants might exploit the network by using infrastructure they own to consume services, thereby accumulating fees and rewards. For example, an energy entity could simulate purchasing energy from its own reserves. With sufficient subsidies or initial block rewards, self-dealing becomes highly profitable.
-
Lazy Providers: Infrastructure providers may promise to deliver services but either fail to fulfill them or deliver low-quality service. Without a rigorous validation system, users have no recourse.
-
Malicious Providers: Though rarer than the previous two, there exists the possibility of malicious entities manipulating infrastructure to feed false sensor data that aligns with their financial interests, deceiving users. If unchecked, such behaviors can undermine the economic incentives of DePIN. Trust and network efficiency decline, leading to a "tragedy of the commons," where providers pursue self-interest, or result in centralization of power. In both cases, the goal of decentralized, peer-to-peer-driven infrastructure is compromised.
Verification Middleware
Designing and architecting such middleware is highly complex. Let us examine it from different angles.
Angle A: Viable Verification Technologies
Verification in DePIN is considered successful if the following two conditions are simultaneously met:
-
Authenticity and Integrity of Measurements: The measurements from service nodes or devices reflect their operational status (e.g., having delivered a service such as providing WiFi access or collecting environmental data) and must be authentic and unaltered.
-
Trustworthiness of Off-Chain Computation: Typically, raw measurements cannot be used directly for verification purposes. Some off-chain computation is required to process them, and this computation must be trustworthy—i.e., tamper-proof.
Take an energy-focused DePIN as an example: Smart contracts must trust that smart meters accurately measure solar power generation, and that middleware verifies a series of 6-hour readings from such meters before triggering cryptocurrency payments on-chain.
To achieve these two goals, we can list currently viable technologies as follows:
Angle B: Packaging Verification Technologies Decentrally
Having understood viable verification technologies sufficiently, we now need to consider how to package them into protocols in a decentralized way. Here are some ideas:
-
The hardware layer should be minimized (to ensure broad accessibility and decentralization), and many functionalities should be integrated into middleware to help avoid centralization risks elsewhere in the stack. This resembles the famous “fat protocol” thesis—we want the hardware layer to be lean and the middleware to be fat.
-
The operation of middleware should resemble that of public blockchains in the following aspects:
-
Permissionless and neutral (open-source, community-operated)
-
Transparent and trustless, offering high security and resilience against sophisticated attacks driven by financial incentives
-
Capable of executing various types of verification for different scenarios, thus requiring built-in programmability (think smart contracts)
-
Able to retain necessary functions from the hardware or application layers when needed.
Angle C: Modes of Verification
In different scenarios, service nodes operate differently. For instance, in file storage, service nodes are continuously working (storing the promised content), so they can be subject to sampling checks. In contrast, for DIMO (vehicle data collection), a service node (a device installed in a car) uploads measurements every 10 minutes, allowing all measurements to be verified. Therefore, middleware employs different verification modes tailored to various DePIN applications:
-
Data Processor: This is the most common mode, where service nodes or devices send essentially all measurements to the middleware, which then verifies and processes them to generate proofs for smart contracts.
-
Active Integrator: The middleware protocol actively selects a subset of service nodes for challenge (note: if the middleware protocol is powerful enough, it can “sample” all nodes). After receiving responses from nodes, it transitions into data processor mode. Filecoin’s random sampling method falls into this category.
-
Passive Observer: This is the least common approach, where the middleware silently observes nodes within the service and attempts to find evidence indicating whether they are (not) performing as expected (referencing dark forest theory).
Building W3bstream as Middleware for DePIN Verification
Synthesizing all the above perspectives, we advocate for a proof-of-validity approach and envision a decentralized, shared, and neutral off-chain verification protocol (as part of an IoT network) serving DePIN networks. This protocol aggregates measurements from numerous smaller DePIN networks and provides validity proofs (e.g., SNARK proofs, which we currently use) to smart contracts.
At a broader level, W3bstream is a community-operated sharded network that allows various DePIN projects to deploy (and later update) their verification “formulas” onto the platform. These “formulas” can be written in Rust, Golang, C++, and more languages will be supported soon. They typically look like this:
Zero-knowledge proofs often come with performance trade-offs, including longer proof generation times and higher computational demands, making them less scalable for certain practical applications. We have implemented internal optimizations on zk-SNARKs (including batching) to address these performance issues, aiming to deliver faster proof generation while preserving the core advantages of zero-knowledge protocols.
Decentralized physical infrastructure stands at the frontier of reshaping multiple layers of our world. Yet, unlocking its full potential hinges on overcoming the challenge of decentralized verification—ensuring the sanctity and inviolability of these networks. We look forward to engaging with top researchers and engineers in blockchain, cryptography, IoT, security/privacy, and economics to realize this shared vision together.
Join TechFlow official community to stay tuned
Telegram:https://t.me/TechFlowDaily
X (Twitter):https://x.com/TechFlowPost
X (Twitter) EN:https://x.com/BlockFlow_News
@iotex_io
