# KAGOME treasury proposal 3

[KAGOME](https://github.com/qdrvm/kagome) is a C++ implementation of the [Polkadot Host](https://wiki.polkadot.network/docs/learn-polkadot-host) that is protocol compatible with the original implementation in Rust and is already participating in [Kusama relay chain validation](https://kusama.subscan.io/validator/GZ777psWniwVo6gJV5T1ywnEy9UsQZEehWW5zu76A3Cco3z). With KAGOME and other client implementations we bring client diversity to Polkadot, mitigating risks of fatal bugs, bringing innovations and broadening the development community. During previous work as part of [Polkadot treasury proposal 2](https://polkadot.subsquare.io/referenda/201), the following results were achieved:

- Asynchronous backing
- BEEFY integration
- New Wasm engine (WasmEdge)
- Initial security audit by SRLabs ([link](https://polkadot.polkassembly.io/referenda/201#YClm2meeCYN0RxRjQcbR))
- General maintenance

In addition to features that were planned during the previous proposal our team achieved the following:

- Implemented Grid and Cluster network topologies for statements distribution
- Partially Integrated disabled validators feature
- Partially implemented elastic scaling
- Implemented multiple security features

This proposal asks for funding for the next 4 months, in addition to the previous 6 months of work on features that have been retroactively implemented (marked with Done status in Section 4).

### Problem statement

Client diversity is essential for the security and resilience of Polkadot as it helps to mitigate the risk of bugs and exploits. If there is only one implementation (which is currently the case Polkadot), then any bug or exploit that is found in that implementation could potentially bring down the entire network. However, with multiple implementations, the risk of a bug or exploit affecting all of the nodes in the network is greatly reduced.

Importance of having multiple client implementations was highlighted multiple times by Polkadot twitter ([source](https://twitter.com/Polkadot/status/1707031181219225653)), and Web3 foundation RFP ([source](https://github.com/w3f/Grants-Program/blob/1d60558a028f79635b37d8830ab650db0eb57dcc/docs/RFPs/alternative_polkadot_host_implementations.md?plain=1)). Moreover, W3F recognizes clients diversity importance and allocates 10 million DOT prise for the future multiple implementations of JAM protocol.

Gavin Wood mentioned KAGOME during 2023 yearly roundup article ([link](https://link.medium.com/3t0YYCF7MKb)) and highlighted our achievement of executing KAGOME node in Kusama during his recent interview ([link](https://t.co/2VGDYts10N)).

To learn more about multi-client philosophy and KAGOME Polkadot Host implementation watch our previous presentations:

- [Building alternative clients in Polkadot | Polkadot Decoded 2023](https://youtu.be/TnENz6I9l8A)
- [Polkadot Host architecture in 2024 | Sub0 Asia 2024](https://youtu.be/Lv2KQ2EDyM8?si=ZmWBINzMwEqbMb90)

### Alignment with JAM

Quadrivium is planning to develop a JAM client and is already working on some features for this in parallel with KAGOME. We also started work on SASSAFRAS many months ago, but stopped because the reference implementation in Rust had not yet been merged into the Polkadot SDK. Given that SAFROLE is the simplified version of SASSAFRAS, we are well positioned to implement a new leader election mechanism in the JAM implementation.

However, we recognize the importance of multiple Polkadot Host implementations today, especially since most features are already available and KAGOME is compatible with the Polkadot SDK. Moreover, it's not anticipated that JAM will be launched within the next one or two years. Luckily, we can repurpose much of the KAGOME codebase for the future JAM client implementation. For instance:

1. Grandpa – fully implemented and audited.
2. SASSAFRAS – partially implemented.
3. SCALE – fully implemented.

But since we didn't initially intend to reuse these components, some refactoring of KAGOME is required. This will enable these components to be reusable and easily integrated into the future JAM client implementation.

### The scope of proposal

- Security improvements (retroactive)
- Grid and cluster topologies (retroactive)
- Elastic scaling (partially implemented)
- Disabled validators mechanism (partially implemented)
- Validation protocol upgrade
- Systematic chunks
- Minor features and improvements (partially implemented)
- DevOps and QA maintenance
- Security assurance by SRLabs

### Requested DOT

- Quadrivium: 86507
- SRLabs: 54888
- Total: 141395

Please review the full proposal with detailed tasks descriptions and price breakdown: https://docs.google.com/document/d/1NOkXMSAOYYgm_NCEzuTCKE-rl5MnlaZD3FN8v0otYbc

### About Quadrivium

Quadrivium ([https://www.qdrvm.io](https://www.qdrvm.io/) ) is a blockchain infrastructure development company founded in 2023. 

The company specializes in the development of blockchain clients, peer-to-peer networking tools, and zk-cryptography. Quadrivium develops KAGOME Polkadot Host implementation, in partnership with the Web3 Foundation. The company also maintains the C++ libp2p library.

### About SRLabs

SRLabs (https://www.srlabs.de/) is home to knowledge leaders securing critical infrastructures in finance, blockchain, energy, and telecommunications.

The company focuses on hands-on hacking resilience, not compliance. Their approach is shaped by combining their hacking research with impactful consulting work for innovation leaders who naturally thrive on cutting-edge technologies.

SRLabs is one of the leading blockchain audit companies with experience in many Substrate-based blockchains, including the Polkadot layer-0 relay chain and parachains built on top.

This proposal seeks funding for the third milestone of the KAGOME project, a C++ implementation of the Polkadot Host, aimed at enhancing client diversity, security, and performance within the Polkadot ecosystem. KAGOME already participates in Kusama relay chain validation and brings alternative client options to reduce the risks associated with a single implementation. The proposal outlines work on critical features such as elastic scaling, validation protocol upgrades, systematic chunks, and various security enhancements. The proposal also includes ongoing security assurance by SRLabs to ensure the robustness of the KAGOME implementation, with technical support and oversight provided by the Web3 Foundation.

Deploying V2, an overhaul of our protocol with many new improvements.

Adding support for major Ethereum L2 chains.

Simplifying the SDK developer experience and documentation.

Support for single-click, multi-hop swap and bridge transactions.

Continuing to operate, secure and keep the bridge up to date.

Improving our consumer-targeted marketing efforts.

Optimizing our light client for faster, cheaper bridging.

Improve the decentralization of our off-chain components.

Ramping up support for stablecoins and improve the UX of stablecoin-based payment flows.

Giving OpenGov new superpowers that it can use to poach liquidity from Ethereum products.

amount

beneficiary

- **Problem Statement:** Lack of client diversity in Polkadot poses a risk of network-wide bugs and exploits.
- **Significance:** Client diversity enhances network security, as highlighted by Polkadot's Twitter and Web3 foundation, reducing the impact of bugs on all nodes.
- **Proposed Solution:** Requesting funding for 4 months to enhance KAGOME with security improvements, grid and cluster topologies, disabled validators mechanism, and more.
- **Expected Outcomes:** Increased network resilience, reduced bug impact, and enhanced security through client diversity.

KAGOME – the C++ implementation of Polkadot Host milestone 3

General

#925 KAGOME – the C++ implementation of Polkadot Host milestone 3

No Active Proposals