Zether Network Layers
Last updated
Last updated
The Zether Network serves as the central communication hub, facilitating storage, verification, and processing of data.
Featuring minimal gas fees and block confirmation times under 3 seconds, the Zether Network ensures cost-efficient and rapid completion of operations.
Builders have the capability to deploy spotter contracts on our blockchain, acting as decision-making entities that generate specific operations based on input data or the overall state of their Protocol.
For Solana deployment, EVM compatibility is achieved through the utilization of the Ethermint Library. This enables the deployment of smart contracts written in Solidity and Rust on Solana.
The Zether Network consists of 3 Layers:
Application Layer
Modules Layer
Tendermint Core Layer
The Application Layer is responsible for accommodating the decoding, correctness and redirection of messages into the Modules assigned.
See the list of modules and their description in the table below.
Delegated Proof of Stake (DPoS)
Facilitates staking for Validators and Delegators.
Banking
Sending and receiving assets on Zether Network
GOV Module
Changes to blockchain parameters, addition of new Validators, Distributors or Agents.
Auth Module
Allows authorized entities to launch smart contracts on Zether Network.
IBC Module
Facilitates communication with Cosmos-based Chains.
Distributor Module
A database of authorized Distributors added through the GOV Module.
EVM Module
Hosts smart contracts deployed on Zether Network such as the Controller. Provides composability between Zether Network and EVM Infrastructure such as Metamask, Hardhat, and Truffle.
The Tendermint Consensus Algorithm enables P2P connections among Validators, facilitating consensus on new blocks. This process consists of three rounds:
Proposal Round: A Validator is selected to propose a block.
Pre-Vote Round: Validators cast "Pre-Votes" on a block, with at least 2/3 of Validators with voting power required to reach consensus.
Pre-Commit Round: Validators vote and achieve consensus again. If all three rounds are successful, a block is committed under a new "block height," containing new transactions.