Technical Architecture
Match is an extensively scalable blockchain based on the Proof-of-Stake (PoS) consensus mechanism. It seamlessly integrates with the Ethereum Virtual Machine (EVM), ensuring complete compatibility and interoperability. Developed on the Cosmos SDK framework, Match leverages the CometBFT consensus engine (a derivative of Tendermint Core) to achieve rapid transaction finality, exceptional throughput, and remarkably short block times, averaging around 5 seconds.
Match incorporates these essential functionalities by:
Harnessing the capabilities of modules and various mechanisms integrated into the Cosmos SDK.
Incorporating the Application Blockchain Interface (ABCI) of CometBFT to effectively oversee the blockchain.
Leveraging the geth library to foster code reusability and enhance the ease of maintenance.
Providing a comprehensive Web3 JSON-RPC layer that is fully compatible with established Ethereum clients and tools such as Metamask, Remix, Truffle, and others.
The incorporation of these attributes empowers developers to harness the prevailing Ethereum ecosystem infrastructure and software, enabling effortless deployment of smart contracts.
Cosmos SDK
Match harnesses the comprehensive composability and modularity offered by the Cosmos SDK, facilitating its status as a self-governing blockchain equipped with a distinctive native token. This integration capitalizes on the amalgamation of standard Cosmos SDK modules and Match-specific modules, expertly crafted by the core development team behind Match.
CometBFT & ABCI
CometBFT encompasses two fundamental technical elements: a robust blockchain consensus engine and a versatile application interface. The consensus engine guarantees the uniform recording of transactions across all machines, ensuring a consistent order. On the other hand, the Application Blockchain Interface (ABCI), constituting the application interface, empowers the processing of transactions in a multitude of programming languages, fostering flexibility and compatibility.
CometBFT has undergone significant development to become a versatile consensus engine for blockchain, capable of accommodating diverse application states. With its ability to replicate any kind of application, it can seamlessly replace the consensus engines of other blockchains, making it a convenient plug-and-play option. An instance of this is Match, an ABCI application that replaces Ethereum's Proof of Work mechanism through the utilization of CometBFT's consensus engine.
Another prominent example of a cryptocurrency application that leverages CometBFT is the Cosmos network. By offering a straightforward API known as the Application Blockchain Interface (ABCI), CometBFT simplifies the blockchain architecture by establishing a clear separation between the application and consensus processes. This decomposition of the design contributes to the overall efficiency and effectiveness of the system.
EVM Compatibility
Match achieves EVM compatibility by incorporating a range of components that collectively facilitate all EVM state transitions, while concurrently upholding a developer experience that parallels that of Ethereum:
The transaction format of Ethereum can be translated into a Cosmos SDK Tx and Msg interface, allowing for seamless interoperability.
Ethereum leverages the secp256k1 curve within the Cosmos Keyring, enhancing security and cryptographic operations.
To facilitate state updates and queries, the StateDB interface, enabling efficient and reliable access to the underlying blockchain data.
Interaction with the Ethereum Virtual Machine (EVM) is achieved through a JSON-RPC client, facilitating seamless integration and communication with the EVM's functionalities.
The majority of components are integrated within the EVM module, but in order to enhance the developer experience, certain components are implemented outside of the module.
To gain a deeper understanding of how Match achieves EVM compatibility as a Cosmos chain, it is advisable to familiarize yourself with the following concepts:
Contributing
To enhance your understanding and become more knowledgeable about the Match core protocol, there are multiple avenues for contribution. We suggest starting with setting up a local Match node using the Match CLI, which will provide you with practical experience. By utilizing the supported clients, you can engage with the node through queries and transactions.
If you find yourself captivated by the process, you can delve even deeper into the subject matter.
Engage in open-source contributions by addressing issues on GitHub in accordance with the Match Contributor Guideline.
Participate in bug hunting activities and potentially receive a bounty for identifying and reporting bugs.
Last updated