Architecture

There is a vital role in TRON's cross-chain design: Messenger.

Any full node can apply for being a messenger. Messengers are responsible for message deliveries between different chains. Messengers of the two connected chains are SPV nodes of each other, record each others' block headers for cross-chain transaction verifications.

For now, it's enabled to quickly build isomorphic parachains(Isomorphic chains have similar consensus and communication protocols) through java-tron. Parachains will support definite business needs by adding new types of transactions, customising actuators, Etc. The development of TRON's cross-chain is now ongoing with further optimisations. Developers can expect creative functions in the future that can be friendly SDKs or heterogeneous cross-chain.

Cross-Chain Consensus

TRON applies a hybrid consensus of DPoS(Delegated-Proof-of-Stake) and pBFT(practical Byzantine Fault Tolerance). DPoS determines the power of producing blocks as well as pBFT accelerates the block confirmation processes.

Originally, TRON has the advantages of DPoS: Fast block generation, high network throughput, and the low possibility to fork. Currently, the block confirmation time is about one minute, and the time will shorten it to 3-6 seconds after pBFT being added.

In addition, pBFT can tolerate less than one-third of dishonest nodes. It has stronger robustness comparing with similar block confirmation algorithms.