Technical implementation scheme
Epidemic prevention Chainnetwork runs many block chains through Epidemic prevention ChainToken EPChanism. Although the goal of the existing proposal is to create a "single block chain" that contains all the global transaction order, Epidemic prevention ChainToken allows many block chains to maintain interoperability while running with each other. Based on this, the Epidemic prevention ChainToken Center is responsible for managing a large number of independent block chains (called "space ", sometimes called" debris ", based on database extension technology "slicing ").
The space on the center keeps submitting the latest blocks, which allows the center to keep up with the changes in the state of each space. Similarly, each space will be consistent with the state of the center. After that, the packet is passed from one space to another, and the message has been transmitted or received by publishing the Mekel certificate (Merkle-proof) to indicate that the information has been transmitted or received. This EPChanism is called "central transaction between blocks" or "IBC" EPChanism" for short.
Bitcoin uses batch replication of distributed accounting technology to ensure security Similarly, we can run on the block chain in this way, thus reducing the possibility of internal and external attacks. We call it distributed.
Epidemic prevention ChainToken fast transaction execution is another advantage °Epidemic prevention ChainToken the space can be achieved by giving priority to the rapid transaction without sacrificing consistency. And IBC (cross-block chain communication) token and other space transactions.
According to the current centralization of encrypted coins, a major application of Epidemic prevention ChainToken is to decentralize distributed exchanges. Its transaction throughput and submission delay can be comparable to those centralization. Traders can submit limit orders offline. Under the application of Epidemic prevention ChainToken ,Epidemic prevention ChainToken center and old C, traders can quickly complete the transfer of funds in and other spaces.
The privileged space can be used as a source of tokens linked to other encrypted currencies. this hook is similar to Epidemic prevention ChainToken relationship between center and space, both of which must update each other's latest blockchain in time to verify proof that tokens have been transferred from one side to the other.
Epidemic prevention Chain space linked to the network should be consistent with the center and other encrypted currencies. This indirEPCly linked space can maintain a simple central logic, And do not need to understand other block chain consensus strategy. Like, A Epidemic prevention ChainToken space with a specific validation group (possibly the same as a validation group in the center) can be used as a space to hook with an Ethernet coin, The application based on Epidemic prevention ChainSocket protocol (TMSP )(that is ," hook space ") has the method of exchanging IBC information with the external Ethernet block chain (that is ," starting point ") linked contract.
This integration may allow all those in the space who have a bank account to transfer the dollars in their own bank account to the space account, or to transfer them completely to the center or other space. From this point of view, the Epidemic prevention ChainToken center is a seamless conduit between legal tender and encrypted currency, thus solving the problem of interaction limitation that puzzles centralization so far.
Epidemic prevention Chainspace can run any application logic, which has been set in the early stage of space operation, can be continuously updated through management. This flexibility allows Epidemic prevention ChainToken space to become a hook carrier for other encrypted currencies, such as Ethernet Square or Bitcoin, and it can also be linked to derivatives of these block chains, using the same code base, but the validation group and initial allocation are different. This allows you to run a variety of existing cryptocurrency frameworks, such as ethernet, bitcoin, CryptoNote and so on, combine them with Epidemic preventionChain, become a better performance consensus engine in general network, and provide more interactive opportunities for the platform. In addition, as a multi-asset block chain, each transaction may contain multiple input and output items, each of which can be any token, making the Epidemic prevention ChainToken dirEPCly decentralized. Of course, it is assumed that the order matches through other platforms. Another alternative is to let space be distributed fault-tolerant (including order books), which can be regarded as a strict improvement on existing centralized encryption coins-an existing attack from time to time.
Space can also be used as a block chain version of the enterprise and government system, which was originally run by one or more organizations of a specific service, now as a TMSP application in a certain space, Thus, the security and interactivity of public Epidemic prevention ChainToken network are maintained without giving up the control of underlying services.
Therefore, Epidemic prevention ChainToken may provide the best operating environment for those who want to use block chain technology and do not want to give control to distributed third parties, that is, the most suitable operating environment for decentralized payment exchanges.
Epidemic prevention ChainarchitEPCure can alleviate the problem of network partitioning, it can use global central nodes, but space implements regional autonomy, and then the voting rights of each space are distributed according to normal geographical location. A general example may be aimed at individual cities or regions, allowing them to share common global centers (such as Epidemic prevention ChainToken centers) while running their own space, and to continue to maintain regional autonomy activities during interruptions caused by network partitioning. Note that in designing robust federated fault-tolerant systems, the characteristics of geography, politics, and network topologies can really be considered.
The name change on the workload proof block chain needs to wait for the additional workload proof verification block to proceed, which may take an hour on Bitcoin. Here Epidemic prevention ChainToken, we only need to use the block hash signed by the quorum certifier (through voting rights) and the Merkel proof of the current value associated with the name. This makes it possible to easily, quickly and safely validate the name value of a light client.
This concept can be used in Epidemic prevention ChainToken to extend it °Epidemic prevention ChainToken each name registry space in which there is a related highest-level domain name (TLD), such as ". com "or ". org ", each name registration space has its own management and registration rules.
Technical parameters Epidemic prevention Chainsilt
The protocol is not strictly an extensible solution. It provides special interoperability for different accounting systems through a loosely coupled bilateral network. For example, lightning networks, the purpose of ILP is to promote payment, but mainly in different book types of payment, and extend the atomic trading EPChanism to include hash locks and notary arbitration sets, also known as atomic transport protocols. The latter EPChanism used to maintain the number of transaction atoms between books is similar to the Epidemic prevention ChainToken light client SPV EPChanism, so the difference between ILP and Epidemic prevention Chain/EPC can be explained.
All block headers needed to be synchronized are now eliminated in the Epidemic prevention ChainToken-PoS because we have alternative chains (forks), which means more than a third of the binding equity can be reduced. Of course, cuts also require someone to share bifurcation evidence, so the light guest side stores any block hash it witnesses. In addition, the light client side can periodically synchronize validation group changes to avoid long-range attacks (among other possible solutions).
Along the same lines as ethernet, Epidemic prevention ChainToken allows applications to embed global EPCkelgen hash in each block for simple and verifiable status queries, such as account balances, contract value, or the presence of unused transaction inputs, depending on the characteristics of the application.
During the PoW, the light guest terminal is considered to be able to synchronize from the reliable creation block to the current height at any time, and this process can be done simply by processing the workload proof on each block head. However, in order to solve the problem LRA, we need to track the changes of the verification group regularly on the line of the light passenger terminal, and it must pay special attention to verifying the information collEPCed from the network according to the reliable source.
The above method of preventing LRA is suitable for Epidemic prevention ChainToken driven block chain validators and all nodes, because the task of these nodes is to keep connEPCed to the network. This method is also suitable for light clients who want to synchronize their networks frequently. However, there is another way to solve LRA problems for light clients who do not want frequent access to the Internet or block chain networks. Non-verifier token holders can issue tokens as collateral for a long untying period and provide a second-level solution to the light client to verify the validity of current and past block hash. Even if these nodes are not included in the security of the block chain consensus, they can provide a strong guarantee for the light client. If historical block hash queries have been supported in Ethernet Square, anyone can bind their tokens with specific smart contracts and provide payment certification services. Thus effEPCively develop a market for the security LRA light customers.
If a globally active opponent is involved, the network is segmented, resulting in a pull-down rate of the validation group subset. And that is not just a constraint for Epidemic prevention ChainToken, but for all consensus agreements. For these types of attacks, the verifier subset should be coordinated externally, signing the reorganization proposal to selEPC the bifurcation and the initial subset of the verifier. The certifiers who sign this restructuring proposal will give up all their collateral on other forks. The client verifies the signature on the reorganization proposal, verifies any evidence and makes a judgment or prompts the end user to make a decision.
dual signatures use simple verifiable evidence to create bifurcations, while submission to detEPC invalid states requires non-validating peer nodes to validate the entire block, i.e. they retain a copy of the local status to execute each transaction, and then calculate the state root independently. Furthermore, because certifiers of the Epidemic prevention ChainToken block chain may be able to authenticate, if there is this idea, the submission of an invalid state may also be punished by the law or other external legal system.