Carbon Emission Merkle
Last updated
Last updated
"Carbon Emission Merkle" is part of the "Work tier Merkle" that processes carbon emissions data. This MErkle calculates carbon emissions data, and the final calculated data is tokenized and processed.
Carbon emissions data collected externally is provided through applications such as payment services and usage service apps, and the infrastructure of certified organizations and companies. These data are collected utilizing WEB3 technology.
Carbon Emission Merkle is a system for payment and usage service clients accessed through “Web3 Provider”. In this system, the client is responsible for validating blocks whenever a transaction occurs.
In addition, the carbon emissions Merkle client adopts a layer-level system structure, which modifies the network protocol of the existing “Ethereum Virtual Machine (EVM)” system to provide specialized functions for processing transactions related to carbon emissions.
In the process of verifying master tier Merkle blocks and smart contract proposals, validator nodes play an important role. In this system, validator nodes are elected into a specific group through a system of router nodes, and this group verifies transactions using the "Boneh-Lynn-Shacham" (BLS) signature scheme.
A group of validator nodes is responsible for validating the proposals and execution of smart contracts related to master tier Merkle blocks. This achieves consensus within the blockchain network.
Additionally, validator nodes are also responsible for processing consensus on the invocation and deployment of smart contracts with other work tier merkles.
The function of helping a node easily find and connect to other nodes in the network is mainly performed by the “Bootstrapping Node”, also known as the “Boot Node”. When a new node attempts to join the network, this boot node plays a very important role.
In order for a new node to join the network, it must first connect to one of the boot nodes. A boot node helps new nodes easily integrate into the network by providing a list of the IP addresses of active nodes in the network. Through this list, new nodes can start connecting to other nodes in the network and proceed with the synchronization process with the network.
“ RPC (Remote Procedure Call) node” is a node that allows a client to call a function of a smart contract and receive the results. This allows clients to execute and manage various combinations of smart contracts using commands from the RPC node.
Service Apps that wish to participate in the Node “Node Authority DAO” of “Carbon Emissions Merkle” must have a Service App ID. This ID includes Google App ID and IOS App ID. The service app's information is passed through this app ID to existing node operators, who evaluate the app during a voting period of 1 to 7 days. If it receives more than 50% approval from existing node operators, the service app will be able to participate in the node, and through this, it will be authorized to issue distribution authentication tokens and usage authentication tokens. This deployment authentication token represents the authority to deploy a smart contract within a carbon emission Merkle, and the usage authentication token represents the authority to use a smart contract within a carbon emission Merkle.
In "Carbon Emissions Merkle", block creation must be pre-authorized by the "Node Authority DAO", which acts as a physical validator, and this organization uses the POA (Proof of Authority) consensus algorithm within the network. An agreement is reached accordingly.
When attempting to deploy a smart contract in a carbon emissions Merkle system, developers must receive a d from the node operator. This token serves to grant permission to deploy smart contracts. Once the deployment of the smart contract is successfully completed, this deployment authentication token is burned.
To use a smart contract in the carbon emissions Merkle system, you must receive a from the corresponding node operator. This usage authentication token is linked to the service app ID, which confirms that the service app has permission to use the smart contract.
