Polygon Edge vs ConsenSys Quorum
What is Polygon Edge?
As per the website and dev docs, Edge is a framework built on Polygon that is modular and extensible to build private or public ethereum compatible blockchain networks. The consensus mechanism is IBFT (Istanbul Byzantine Fault Tolerant), which supports PoA and PoS. With Edge you can have custom features, cross-chain communication and portability of ethereum smart contracts.
The custom features include, but are not limited to:
● Dev friendly plugin system
● Development of plugins, but not by forking, by building
● Changing the core functionalities of consensus plugins
● Building ethereum smart contracts with runtime plugins
The cross-chain communication features are:
● Transferring erc20, nfts, and wrapped native currencies
● Customizable bridge functionality using bridge plugins
● Transferring assets to and from EVM compatible networks (most popular one is Polygon and ethereum mainnets)
● Building trustless and decentralized built in ethereum bridge solution
The portability features are:
● Full EVM support developing in Solidity/Vyper
● Full support with JSON-RPC wallets
● Uses widely adopted ethereum tooling, libraries, and dev tools
● Streamlined UX when doing cross-chain operations
Below is a look at the modules that cover the whole blockchain stack:
Edge Libp2p Module
Libp2p is modular, extensible, and fast. It is the base networking layer that fits into the designing philosophies of Edge. It is a good foundation for more advanced features, and was based on IPFS. The features include, transport, identity, security, peer routing, content discovery, and messaging/pubsub.
Edge Consensus and Synchronization Module
The separation between sync and consensus protocols allow for modularity and custom sync and consensus methods. This allows for Edge to have off-the-shelf pluggable consensus algorithms. Edge currently supports IBFT PoA and IBFT PoS. All nodes start in the Sync state, this is because fresh data needs to be fetched from the blockchain. It needs to find the current snapshot and the client needs to find out it’s the validator.
Edge Blockchain/State Module
The main modules of Edge are blockchain and state, blockchain is the integral part that deals with block reorganizations. The blockchain module deals with all the processing and logic that happens when a new block is included on the blockchain. State represents the state transition object. In other words, state is the change of the block that is being added. State handles: executing transactions, executing the EVM, changing the Merkle tries, and a lot more.
The important part is that the blockchain and state modules are very interconnected, and work closely together so the client can function. The blockchain module is also responsible for some parts of the consensus. “It is the main core logic through which all the blocks are included.”
Edge JSON RPC
The JSON RPC layer is an API that dApp devs use to interact with the blockchain. It supports standard json-rpc endpoints and websocket endpoints. It has a blockchain interface, ETH endpoints, and a filter manager. See the source for more information on the code associated with the module.
The TxPool layer is the transaction pool, this is where all transactions are held, however it is closely linked with many other modules in the system, as transactions can be made from different entry points. In the TxPool, there are operator commands, processing transactions, data structures, gas limit error management, and block gas target. See source for example scenarios on each.
Minimal is the central hub for all the services that run on Polygon Edge
Minimial is responsible for:
● Setting up data directories
● Creating a keystore for libp2p communication
● Creating storage
● Setting up consensus
● Setting up the blockchain object with GRPC, JSON RPC and Synchronization
The GRCP protocol layer helps abstract request/reply protocols and makes protocols needed for Edge to function simpler. It lies on top of libp2p, and there are multiple types of GRPC that Edge uses, but for simplicity it is grouped into one in this explanation. The GRCP relies on protocol buffers, which are like XML but smaller, faster and simpler. The GRCP defines services and message structures. GRCP can also be used for node operations.
What is ConsenSys Quorum?
As per the website and dev docs, Quorum enables enterprises to leverage ethereum for their high-value blockchain applications. You can build high-performance and customizable applications on a private blockchain. Quorum enables permissioning and privacy, consensus mechanisms, is prod-ready, ecosystem compatible, enables quick starts and support, and has enterprise add-ons.
Permissioning and privacy — its open source protocol layer allows businesses to build a public or private ethereum networks.
Consensus mechanisms — Hyperledger Besu and GoQuorum support PoA (IBFT and Clique) consensus mechanisms. Besu also supports PoW in EthHash
Prod-ready — allows connectivity to monitor uptime and performance of enterprise solutions. Also includes monitoring, logging, and event streaming for High Availability, and database backups for Disaster Recovery are in full support.
Ecosystem compatibility — works with Truffle, MetaMask, Remix, OpenZeppelin, and much more. Multitude of options for ethereum Mainnet.
Quickstarts and support — there is a multitude of dev documentation for the Quorum, and support is always available
Enterprise add-ons — allows for a number of market ready enterprise product modules in Mainnet and private network deployment
Quorum vs Edge, Pros, Cons, and Features