Original source:
Original author:Naz
Original source:twitter
Original Compilation: Kate, Marsbit
Note: This article comes from@CryptoNasss Twitter, MarsBit organized as follows:
Comparing threads of modular blockchains
Explore their architecture, scalability solutions, consensus mechanisms and interoperability features
consensus mechanism
PolyBFT (Polygonal Byzantine Fault Tolerance)
Avalanche consensus, repeated subsampling among nodes and pass-through voting in DAG
BABE for block production (a variant of Ouroboros Praos) and GRANDPA for finalization (a variant of PBFT)
Tendermint PBFT
QBFT, IBFT 2.0, Etherhash, and Clique
Validator admission
Polygon: Proof of Stake
Avalance/Polkadot/Cosmos: Proof-of-Stake on the main network and keep the option on other networks
Besu: Runs 3 consensus mechanisms, PoS, PoW and PoA (Proof of Authority)
Computational throughput
Polygon: Over 2000 TPS
Avalance/Polkadot/Cosmos: Depends on the runtime complexity of each chain, and as interoperable chains grow, the entire network is unconstrained.
Besu: up to 400 TPS
transaction delay
𝗣𝗼𝗹𝘆𝗴𝗼𝗻: Instant finality with 2 second block time.
𝗔𝘃𝗮𝗹𝗮𝗻𝗰𝗵𝗲: Adjust system parameters to reduce the possibility of two nodes contradicting each other on a single txn.
𝗣𝗼𝗹𝗸𝗮𝗱𝗼𝘁: End time between 12 and 60 seconds.
𝗖𝗼𝘀𝗺𝗼𝘀: Completes between 6-7 seconds.
𝗕𝗲𝘀𝘂: It's hard to be sure because it varies with different consensus mechanisms. You can read more here:
https：//hyperledger.org/learn/publications/blockchain-performance-metrics#appendix-a
transaction fee
𝗣𝗼𝗹𝘆𝗴𝗼𝗻: Provide lower gas cost through transaction batching. Users can configure batch processing according to their own needs, so as to be able to configure the cost of txn.
𝗔𝘃𝗮𝗹𝗮𝗻𝗰𝗵𝗲/𝗖𝗼𝘀𝗺𝗼𝘀: Customizable fee per active chain.
𝗣𝗼𝗹𝗸𝗮𝗱𝗼𝘁: Fees can be customized through pre-computation by weight system, fee burning per chain is optional.
𝗕𝗲𝘀𝘂: Fees are set by network participants, in other words, validators for each consensus mechanism.
Cross-chain network topology
𝗣𝗼𝗹𝘆𝗴𝗼𝗻: A distributed network of self-sovereign chains with their own validating nodes.
𝗔𝘃𝗮𝗹𝗮𝗻𝗰𝗵𝗲: runs an overlapping network of validators for multiple chains, simultaneously validating
𝗣𝗼𝗹𝗸𝗮𝗱𝗼𝘁: Hierarchical inheritance security from the central chain to the connected chain. Interoperability through cross-chain messaging.
𝗖𝗼𝘀𝗺𝗼𝘀: A distributed network of self-sovereign chains with their own validators. Interoperability is achieved through interchain communication.
𝗕𝗲𝘀𝘂: Interoperability with EVM-compatible networks.
governance
𝗣𝗼𝗹𝘆𝗴𝗼𝗻/𝗔𝘃𝗮𝗹𝗮𝗻𝗰𝗵𝗲: Blockchain parameters can be upgraded through on-chain voting.
𝗖𝗼𝘀𝗺𝗼𝘀: On-chain mechanism for changing consensus parameters and coordinating funds.
𝗕𝗲𝘀𝘂: No documents found related to HyperLedger Besu governance.
𝗣𝗼𝗹𝗸𝗮𝗱𝗼𝘁: The entire runtime logic is stored on-chain as a WASM (Web Assembly) binary, allowing fork-free runtime upgrades. Governance modules include token-weighted voting, time-locked voting, and adaptive group bias.
Developability
𝗣𝗼𝗹𝘆𝗴𝗼𝗻：
With Polygon Edge's built-in support for the EVM, Solidity smart contracts can be easily ported to the Polygon Edge network without any modifications.
𝗔𝘃𝗮𝗹𝗮𝗻𝗰𝗵𝗲：
Avalanche virtual machine for building your own VMs (SDK coming soon).
In order for your chain to go live, a subnet of validators needs to be attracted to run your chain.
Deploy smart contracts on EVM-compatible C-chains.
𝗣𝗼𝗹𝗸𝗮𝗱𝗼𝘁：
Substrate for building your own virtual machines in Rust.
Your chain goes live after you win a seat in the parachain auction, which inherits the security of the relay chain. Alternatively, you can grow your own validator community.
𝗖𝗼𝘀𝗺𝗼𝘀：
With Cosmos SDK and Tendermint as middleware, you can build your own VM in any language.
In order to get your chain live you need to build a validator community from the ground up and attract a validator community from an existing chain.
𝗕𝗲𝘀𝘂: Support for Solidity.
shared security
𝗣𝗼𝗹𝘆𝗴𝗼𝗻: Validators verify all transactions on the super network. Composed of third-party staking companies, validators stake MATIC tokens on the mainnet prior to validating the network. A high level of security can be achieved because: Validators are vetted by Polygon. It’s worth noting that any misbehavior by a validator has an immediate impact on the amount staked.
𝗔𝘃𝗮𝗹𝗮𝗻𝗰𝗵𝗲: Security is handled at the subnet level and can consist of multiple virtual machines (blockchains). Each validator in the subnet also has a node on the main network. Shared security is optional.
𝗣𝗼𝗹𝗸𝗮𝗱𝗼𝘁: The relay chain verifies the state transitions of all parachains. Each parachain needs to implement its own security measures to prevent censorship attacks. Shared security is mandatory.
𝗖𝗼𝘀𝗺𝗼𝘀: Each hub and zone has its own security. Research and Center Validation Zone Sharing Security.
𝗕𝗲𝘀𝘂: Lack of shared security.
Interoperability
𝗣𝗼𝗹𝘆𝗴𝗼𝗻：
* Interoperable with EVM-compatible blockchains.
*Any smart contract can be executed and deployed on the Ethereum/Polygon mainnet.
* Plug and play existing Ethereum tools: Solidity, Hardhat, ethers.js, web.js, Metamask, Remix, etc.
𝗔𝘃𝗮𝗹𝗮𝗻𝗰𝗵𝗲：
* Interoperate between virtual machines within a subnet and between any subnets.
*The level of trust differs at the subnet level.
*The main network can be used as a source of trust.
* Connect to external blockchains via a bridge.
𝗣𝗼𝗹𝗸𝗮𝗱𝗼𝘁：
*All parachains share the same trust assumption of the Relay Chain validator set.
* Connect to external blockchains by bridging parachains.
*External blockchains take longer to finalize.
* Parachain slots are limited.
𝗖𝗼𝘀𝗺𝗼𝘀：
* Interoperate through paths connecting zones and hubs.
*Different trust levels for each zone/hub path taken.
* Connect to external blockchains via Peg zones or ask them to fork the code and implement IBC (Inter blockchain Communication).
𝗕𝗲𝘀𝘂: Interoperability with EVM compliant networks.
Token Economics
𝗣𝗼𝗹𝘆𝗴𝗼𝗻: The super network requires validators to stake $MATIC on the Polygon PoS chain. From a token economics perspective, you can set up your own native gas currency that provides instant utility.
𝗔𝘃𝗮𝗹𝗮𝗻𝗰𝗵𝗲: Validators for each subnet must also validate the main network and stake 2000 $AVAX. In AVAX, transaction fees on the main network, subnet and blockchain creation fees are burned. Each subnet can have its own token.
𝗣𝗼𝗹𝗸𝗮𝗱𝗼𝘁: $DOT is used to secure the relay chain. Each parachain needs to earn enough DOTs to win the auction for a slot, and each parachain has its own token.
𝗖𝗼𝘀𝗺𝗼𝘀: Each zone/hub earns tokens and there will be many hubs. Inflation/uncapped supply.
𝗕𝗲𝘀𝘂: Support 0 minimum gas fee.
use
𝗣𝗼𝗹𝘆𝗴𝗼𝗻：Nexon,Immutable, @Google, @gotchicchain and 10 other clients are building the supernet.
𝗔𝘃𝗮𝗹𝗮𝗻𝗰𝗵𝗲: 19+ subnets, but only 5 seem to be active.
𝗣𝗼𝗹𝗸𝗮𝗱𝗼𝘁: Substrate Ecosystem (https://substrate.io/ecosystem/projects/）
𝗖𝗼𝘀𝗺𝗼𝘀: 200+ Cosmos chains. (https://mapofzones.com/home )
𝗕𝗲𝘀𝘂: Many enterprise case studies. (https://hyperledger.org/learn/case-studies)
EVM Compatibility
𝗣𝗼𝗹𝘆𝗴𝗼𝗻: Yes
𝗔𝘃𝗮𝗹𝗮𝗻𝗰𝗵𝗲: yes + AVM + custom VM options (SpaceVM, BlobVM, etc.)
𝗣𝗼𝗹𝗸𝗮𝗱𝗼𝘁: None
𝗖𝗼𝘀𝗺𝗼𝘀: Not by default, but EVMOS is a compatible Cosmos chain.
𝗕𝗲𝘀𝘂: Yes
storage
𝗣𝗼𝗹𝘆𝗴𝗼𝗻：LevelDB
𝗔𝘃𝗮𝗹𝗮𝗻𝗰𝗵𝗲: Bundlr Network
𝗣𝗼𝗹𝗸𝗮𝗱𝗼𝘁: DCS (Decentralized Cloud Storage)
𝗖𝗼𝘀𝗺𝗼𝘀: Varies depending on the application chain
𝗕𝗲𝘀𝘂：RocksDB（KVS）
account abstraction
𝗣𝗼𝗹𝘆𝗴𝗼𝗻: experimental
𝗔𝘃𝗮𝗹𝗮𝗻𝗰𝗵𝗲: can be implemented in a custom virtual machine
𝗣𝗼𝗹𝗸𝗮𝗱𝗼𝘁: Not applicable
𝗖𝗼𝘀𝗺𝗼𝘀: Not applicable
𝗕𝗲𝘀𝘂: Lack of AA.
repeater
𝗣𝗼𝗹𝘆𝗴𝗼𝗻/𝗔𝘃𝗮𝗹𝗮𝗻𝗰𝗵𝗲/𝗕𝗲𝘀𝘂: not native, via 3 P software
𝗣𝗼𝗹𝗸𝗮𝗱𝗼𝘁: Not applicable
𝗖𝗼𝘀𝗺𝗼𝘀: Not applicable
Staking/reward
𝗣𝗼𝗹𝘆𝗴𝗼𝗻: $MATIC/flexible
𝗔𝘃𝗮𝗹𝗮𝗻𝗰𝗵𝗲: $AVAX/flexible
𝗣𝗼𝗹𝗸𝗮𝗱𝗼𝘁: Not applicable
𝗖𝗼𝘀𝗺𝗼𝘀: $ATOM/native token
𝗕𝗲𝘀𝘂: no need/native token
EIP-1559 Combustion
𝗣𝗼𝗹𝘆𝗴𝗼𝗻: Yes
𝗔𝘃𝗮𝗹𝗮𝗻𝗰𝗵𝗲: None, but highly customizable fees by default.
𝗣𝗼𝗹𝗸𝗮𝗱𝗼𝘁: Fee burning per chain is optional.
𝗖𝗼𝘀𝗺𝗼𝘀：N / a
𝗕𝗲𝘀𝘂: Yes
bridging capability
𝗣𝗼𝗹𝘆𝗴𝗼𝗻: Built-in PoS V1, supports ERC-20, ERC-721 and ERC-1155, 3P of external ecosystem.
𝗔𝘃𝗮𝗹𝗮𝗻𝗰𝗵𝗲: additional deployment, support for ERC-20 without ecosystem, 3P of external ecosystem.
𝗣𝗼𝗹𝗸𝗮𝗱𝗼𝘁: Not applicable
𝗖𝗼𝘀𝗺𝗼𝘀: Gravity Bridge
𝗕𝗲𝘀𝘂：HyperLedger Cacti
double pledge
None of these modular chains are dual-staking.
light node
𝗣𝗼𝗹𝘆𝗴𝗼𝗻: None
𝗔𝘃𝗮𝗹𝗮𝗻𝗰𝗵𝗲: state synchronization/database replication
𝗣𝗼𝗹𝗸𝗮𝗱𝗼𝘁: Not applicable
𝗖𝗼𝘀𝗺𝗼𝘀: light client/full node
𝗕𝗲𝘀𝘂: No, only full and archived => (Pos, PoA, PoW)
KYC
𝗣𝗼𝗹𝘆𝗴𝗼𝗻/𝗖𝗼𝘀𝗺𝗼𝘀/𝗕𝗲𝘀𝘂: not built-in, but integrable.
𝗔𝘃𝗮𝗹𝗮𝗻𝗰𝗵𝗲: Yes, built-in.
𝗣𝗼𝗹𝗸𝗮𝗱𝗼𝘁: Not applicable
Liquidity pledge
𝗣𝗼𝗹𝘆𝗴𝗼𝗻: No, but planned with Hub.
𝗔𝘃𝗮𝗹𝗮𝗻𝗰𝗵𝗲: None
𝗣𝗼𝗹𝗸𝗮𝗱𝗼𝘁: Not applicable
𝗖𝗼𝘀𝗺𝗼𝘀: Yes
𝗕𝗲𝘀𝘂: None
Thank you for walking me this far, I hope you learn something new from this, I spent a lot of time researching and providing this information for the lovely you, so thank you very much. see you next time
Additional resources and useful links:
https://medium.com/1kx network/application-specific-blockchains-9 a 36511 c 832
https://globalcoinresearch.com/2023/04/20/dapp-chains-go-head-to-head-a-comprehensive-comparison-of-avalanche-polkadot-celestia-and-cosmos/
https://coinbase.com/cloud/discover/dev-foundations/intro-to-avalanche-subnets
