Monetize data, obtain blockchain Token incentives, and realize the thinking of "reading/driving/transaction", that is, mining technical solutions. In order to realize the great imagination of user data confirmation and data realization, a series of technical problems need to be solved, such as the combination of blockchain + big data.
More blockchain technology and application classification:
Blockchain applicationBlockchain development
Ethernet Square | Fabric | BCOS | cryptography | consensus algorithm | bitcoin | Other chain
Token Economy | Traditional Financial Scenarios | Decentralized Finance | Anti-counterfeiting Traceability | Data Sharing | Trusted Deposit
When it comes to blockchain, it always mentions user data confirmation and the great imagination of data realization. Such as "drive mining", "token incentives", etc. The realization of these core functions involves the integration of blockchain + big data, and this part of the function belongs to the core part of the interaction between the two systems, involving technology, Security, passes and many other aspects. Therefore, there are still architectural and technical issues that need to be resolved if it is to be truly implemented.
1. Incentive token type
Tokens on the blockchain can be divided into two categories based on different implementation technologies: "platform currency" and "contract currency".
Platform currency: the token determined by the consensus of the underlying public chain, such as BTC in the bitcoin network and ETH in the Ethereum.
Contract currency: The token defined in the smart contract can still store value, transfer, and never disappear, but it is not determined by the underlying network. Such as the ERC series of tokens in Ethereum.
two. Early data contribution incentives
In the early days, the idea of monetizing data on the public chain was like this: First, deploy your own public chain (running multiple nodes and mining farms), then use mining pools to mine the coins in a token pool, and then end users through contributions Data acquisition of tokens in the Pool. This model of acquiring tokens based on the amount of data is similar to the "POS consensus" in the public chain system. This is probably the frequently heard "POS consensus reading/driving/transaction" That is mining". The logic is as follows.
in conclusion:
This solution needs to deploy its own public chain.
three. Current incentives
Taking into account the implementation and feasibility, the following scheme can be used: Use a mature blockchain, such as Ethereum, and use contract tokens as incentive Tokens, so there is no need for mining or token pools. Therefore, It is very different from the former architecture. End users interact with our Ethereum private chain/consortium chain, users upload their own data, and then through a certain layer of protocol conversion (this part of the problem is discussed later) to record on the Ethereum private chain, when the user uses "Withdrawal "During operation, extract the coin mapping on the private chain/consortium chain to the contract corresponding to the public chain. This process requires ether gas fee, which can be paid by the user, which can effectively limit the damage of malicious nodes to the blockchain network.
Here are the advantages of using the Ethereum private chain/consortium chain:
- The data still cannot be tampered with at will, you can only empty or save all the data.
- Improve performance, maximize TPS, throughput and other performance in a private chain/consortium chain environment
- Seamless access to official SDKs such as wallets, and a very mature library to manage data assets on the private chain/consortium chain.
four. "Data" and "Token" Conversion
In the architecture mentioned above, the core issue is at which layer the conversion protocol between "user vehicle data" and "tokens" is implemented.
The conversion protocol is implemented at the data service layer, smart contract layer and consensus layer:
(1) Data service layer:
This layer is a back-end service and is outside the blockchain. It is the easiest to implement at this layer. The back-end statistically analyzes the data uploaded by users (or completed by the big data module), and then informs the blockchain of the Token that needs to be allocated, and the call area Block link port realizes token distribution.
(2) Smart contract layer
However, if this function is implemented at the contract layer, every data/batch of data needs to pass through the blockchain and contract, which poses a challenge to the performance of the blockchain. Moreover, the data is ultimately stored outside the blockchain (big data platform), so this solution needs to be considered.
(3) Consensus layer
Realizing the conversion protocol at the consensus layer is actually the most ideal. All data is distributed through the underlying protocol of the blockchain for Token distribution, which can generate the greatest degree of trust. However, the underlying consensus of the blockchain must be modified. In other words, you need to develop a chain yourself, such as using the "POD" consensus (Proof Of Data). Therefore, it is currently more difficult.
Fives. Scheme architecture in three ways
With the determination of the conversion protocol, the architecture level of blockchain and big data will also be adjusted. The current thinking is that after data comes in, it passes through the blockchain first, and then to big data. But for the reliability and credibility of data mining, the data flow direction of the back-end architecture can be changed to other forms. The first option is to pass the blockchain first and then the big data, the second option is to flow to the blockchain and big data at the same time, and the third option is to pass the big data first and then to the blockchain.
Original link: Data incentive "xx is mining" technical realization plan