BB Blockchain System Architecture
Last updated
Last updated
ZK-EVMs are essentially ZK-Rollups with a virtual machine similar to the EVM, which provides proof of correctness for each computation step. This proof ensures that the execution follows the rules.
Tnet’s ZK-EVM is similar to Ethereum internally, there are differences in external data structures, such as the block structure and state tree. With minor changes to the data
structure holding things like the Ethereum State, applications can be fully compatible with ZK-EVM. Tools for writing, debugging, and running solidity code can be used seamlessly with ZK-EVM, just as they can with Ethereum.
The Tnet architecture is formalized as a collection of protocol layers, designed to operate together. The most prominent example of such layered architecture is likely the Internet protocol suite, with its four layers (Link, Network, Transport and Application Layer) that power the Internet. Each of the protocol layers facilitates a specific sub-process, and this logical separation simplifies reasoning, implementation and upgrades of the architecture.
Tnet consists of four protocol layers, each enabling an important process within the network:
Staking Layer
Agg Layer
Execution Layer
Proving Layer
Tnet Transactions are batched on the rollup network and sent back to the mainnet with a SNARK proof to verify transactions
ZK-Rollups don’t need to publish all the transaction data on the L1 because they use validity proofs and they are sufficient in proving the authenticity. But they do publish the state data for every transaction processed off-chain to L1. Anyone can reproduce the rollup’s state and validate the chain themselves.
Tnet zkEVM actually works, we have to trace the whole sequence of transactions from the initialization point down to the finalization point. This process includes several steps, each critical to achieving the scalability and efficiency for which Tnet zkEVM is known.
