DataBroker DAO is the first marketplace for buying and selling sensor data. As a decentralized market for IoT sensor data utilizing blockchain technology, Databroker DAO enables sensor owners to monetize their data by transforming it into revenue streams. This will open up rich opportunities across various industries, making data more utilized and effective. The DTX token is the utility token on the Databroker DAO platform. DTX is an ERC20 compatible token with 18 decimal places. The tokens will serve as the currency for buying and selling sensor data on the platform.

Project Distribution

On the DataBroker DAO platform, data buyers spend DTX tokens to acquire data, while data providers receive 80% of the DTX, telecommunication companies get 10%, and the DataBroker DAO platform receives 10%. In this way, buyers conveniently obtain the required data, while providers and service parties receive corresponding rewards.

Project Prospects

Currently, smart cities are a key focus area for DataBroker DAO, with discussions ongoing with the Dubai government. The Dubai government aims to enhance residents happiness through smart cities, and via the DataBroker DAO platform, they can easily access the needed data. Another direction is smart farms, where farmers collect sensor data, boosting productivity by 2-3% annually, and can sell sensor data through DataBroker DAO for additional income. Thanks to its top-notch development team and abundant industry resources, DataBroker DAO is rapidly advancing project implementation. More and more sensor manufacturers are choosing to join DataBroker DAO, fostering rapid ecosystem growth. As a unicorn in the niche field of sensor data trading, DataBroker DAO has successfully seized the industrys lead. With the rapid iteration of underlying blockchain technologies, DataBroker DAO is poised for explosive growth!

Project Architecture

Token-Gated Registration for Reputation, Quality, and Content Management
The core component of the platform is the registration of sensors and data streams/files offered on the platform. In the DataStreamRegistry, we will store all resources that provide sensor data. Broadcasted data can be real-time data from an IoT sensor, sold based on time spans. The DataSetRegistry will preserve data "files" that can be purchased; these are sold per download. To list data streams/sets in such registries, owners must hold (stake/send/lock) a certain amount of DTX tokens. These tokens are locked by data sellers as a good faith guarantee. There will be a minimum holding requirement to be permanently listed in the registry. If data sellers wish, they can hold more DTX tokens. The more tokens held, the more prominent the position of these data streams/sets in listings (such as sorting or additional badges in the interface), increasing the likelihood of being purchased while simultaneously enhancing buyer assurance that the data is high quality and contains what is advertised. Unsatisfied buyers can challenge records in the registry by holding some DTX tokens. This challenge will be reflected in the UI facing all potential buyers as a negative reputation score. In itself, it does not impact the sale of the data. When a certain threshold of challenges is reached, the DataBroker DAO administrator will conduct a verification operation on the data provider. If issues are found with the advertised data, the tokens held will be split between all challengers and the DataBroker DAO platform wallet, and the record will be deleted. If the data is deemed reliable, the tokens held by the challengers are split between the data seller and the platform.

Identity Management for One Billion Sensor Owners
Databroker DAO is a peer-to-peer market for IoT sensor data. This data is generated by sensors, and we are talking about billions of them. These sensors are owned by a vast number of owners. These owners have contracted with network operators (who may be telecommunications companies or producers) to transmit the data generated by their sensors (primarily via networks) to gateways for use. Network operators act as gatekeepers for data flows through their gateways. They have conducted all required KYC procedures for sensor owners and have themselves verified and authenticated the sensors. They also protect their networks against unauthorized use. Moreover, in most regions, network operators enjoy monopoly positions, resulting in a vast number of partners but significantly fewer compared to the number of owners or sensors. For Databroker DAO, partnering with these gateway operators is a highly beneficial strategy. By controlling and validating gateway operators, the platform gains indirect management and control over a vast number of sensors. This raises the issue of managing identities of sensors, owners, and operators on the platform. Relying on end-user identity management solutions like uPort, the platform operates with "regulated identity proxy" contracts. These proxy contracts contain links associated with the sensor owners wallets and addresses. Unlike end-user solutions, these proxy contracts are also linked to the owners identity with the gateway operator and can be controlled by the gateway administrator. This allows us to have full ownership alongside sensor owners, combined with the ability of gateway operators to control/automate their interactions with the system and even handle end-user private keys until proper key management systems are widely adopted and prevalent. The system will be open source before the public token sale.

dAPPs and dAPIs
In the blockchain space, most projects are built on top of distributed applications or dAPPs. These client applications interact directly with Ethereum or other blockchains. In many cases, to improve future user experience, these applications run on remote shared nodes, although this is the only way to create user-friendly peer-to-peer applications, it presents significant drawbacks for some of our use cases:
● Single point of failure. During recent token sales, client applications plus high demand have caused these shared nodes to crash. Not for lack of effort or skill, but because massive amounts of PRC calls are required to execute specific functions on Ethereum smart contracts. In high-stakes areas, such failures are unacceptable.
● Web interfaces and applications are beautiful, but the real value lies in APIs. In todays SaaS and cloud frenzy, this is almost taken for granted. You cannot have a real product unless you also have an API for it. Slack, Zapier, Github, CRM, and ERP systems, their success is partly due to their investment in APIs.
● The more applications, the more problems. Adding more interfaces only makes it harder for the average user. Sensor owners already have accounts with operators. They have learned how to use them and are happy (or they would switch operators).
This is why we have added what we call dAPIs. Like dAPPs, they are API applications deployed on each node. These dAPIs are primarily used by gateway operators, data processors, and large data buyers, rather than sensor owners or small-scale buyers. They will use off-the-shelf interfaces provided by network operators or the Databroker DAO dAPP.

Data Distribution and Storage
Billions of sensors generate vast amounts of data. Consequently, any company using IoT sensor data has its own systems for handling this data and is unlikely to want to replace their systems. This means we cannot force them to implement new data storage systems. More importantly, the platforms goal is not to permanently store all IoT sensor data. Built-in connectors within the dAPI integrate with leading IoT and big data storage providers, allowing buyers to choose destinations for sending data. There is now a valid use case for blockchain to store such data. Immutable and timestamp features are noteworthy. To benefit from these features, the dAPI will store data on the Ethereum mainnet (using Chainpoint spec).

Related Links:
https://www.qukuaiwang.com.cn/news/6693.html
http://www.120btc.com/coin/1814.html
https://cloud.tencent.com/developer/news/248571

*The above content is officially organized by Bixiaohao. If you need to reprint, please indicate the source.