We started with the idea of making software that is modular.
This is something that is present in almost all parts of the Polygon SDK. Below, you will find a brief overview of the built architecture and its layering.
Polygon SDK Layering
It all starts at the base networking layer, which utilizes libp2p. We decided to go with this technology because it fits into the designing philosophies of Polygon SDK. Libp2p is:
Most importantly, it provides a great foundation for more advanced features, which we’ll cover later on.
Synchronization & Consensus
The separation of the synchronization and consensus protocols allows for modularity and implementation of custom sync and consensus mechanisms – depending on how the client is being run.
Polygon SDK is designed to offer off-the-shelf pluggable consensus algorithms.
The current list of supported consensus algorithms:
- Ethereum’s Nakamoto PoW (⚠️WIP)
- Clique PoA (⚠️WIP)
We plan to add support for more consensus algorithms in the future (HotStuff, Tendermint etc).
Contact the team if you would like to use a specific, not yet supported algorithm for your project.
The Blockchain layer is the central layer that coordinates everything in the Polygon SDK system. It is covered in depth in the corresponding Modules section.
The State inner layer contains state transition logic. It deals with how the state changes when a new block is included. It is covered in depth in the corresponding Modules section.
The JSON RPC layer is an API layer that dApp developers use to interact with the blockchain. It is covered in depth in the corresponding Modules section.
The TxPool layer represents the transaction pool, and it is closely linked with other modules in the system, as transactions can be added from multiple entry points.
The GRPC layer is vital for operator interactions. Through it, node operators can easily interact with the client, providing an enjoyable UX.
Originally published @ https://sdk-docs.polygon.technology/docs/reference/architecture