<h1>Quadrivium Polkadot-SDK improvements proposal 1</h1> This proposal seeks funding for the work focusing on:<ol><li data-list="bullet">Preparing Polkadot storage infrastructure to handle thousands of transactions per second (TPS)</li><li data-list="bullet">Ensuring parachain liveness with a single honest collator assumption</li><li data-list="bullet">Enhancing testing infrastructure by simplifying the bug reproduction process</li></ol>This will be achieved by implementing the following features into Polkadot-SDK:<ol><li data-list="bullet">State sync fixes and improvements: ensuring we can handle large state synchronization</li><li data-list="bullet">Compact archive node research and development: ensuring large state parachains have relatively compact archive storages, required for historical data analytics</li><li data-list="bullet">Multi-slot collation: ensure we can guarantee liveness of parachains with a single honest collator assumption</li><li data-list="bullet">Polkadot discrete event simulation research: ensure we can reproduce any of 1000s test runs that ended up with a failure</li><li data-list="bullet">Faster erasure coding (RFC-0139): ensure data availability will not be a bottleneck</li></ol>The proposal scope will be implemented by the Quadrivium team. We are the original developers of the KAGOME client, which is fully protocol-compatible, has successfully passed a rigorous security audit, and launched on the mainnet earlier this year—all clear evidence of our expertise in the Polkadot protocol and ability to deliver on promises.Parity and Web3 Foundation will provide implementation guidance and conduct final review of proposal deliverables. The Parity team also contributed to defining the proposal's scope.Read the full<a href="https://docs.google.com/document/d/14utgMw0XZycmNo6RAJ9GLlvwmxh3QtAShRnLJoDU6oY/edit?usp=sharing" rel="noopener noreferrer" target="_blank"> proposal</a> for further details about features description, development approach, concrete deliverables, and price breakdown.<h2>Requested funding</h2>288,000 USDC<h2> </h2><h2>Context of previous proposal</h2>Quadrivium is best known in the Polkadot ecosystem for implementation of alternative Polkadot Host implementation KAGOME, which went live on Polkadot mainnet in April this year (link) turning Polkadot into one of few blockchains having live multiple client implementations.Unfortunately, in spite of the great progress with KAGOME, and support from W3F and independent node operators with an increasing fraction of validators using KAGOME, the treasury proposal 1549 to support further development and maintenance of KAGOME got rejected.&nbsp;We respect community opinion and therefore we put KAGOME development on pause.Nonetheless, our team has a very unique understanding of the Polkadot protocol, which we believe the Polkadot ecosystem may get advantage from. Therefore, we will be refocusing our efforts towards improving Polkadot-SDK and Polkadot Protocol. <h3>About Quadrivium</h3>Quadrivium (<a href="https://www.qdrvm.io/" rel="noopener noreferrer" target="_blank">https://www.qdrvm.io</a> ) 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 developed KAGOME Polkadot Host implementation, in partnership with the Web3 Foundation. The company also maintains the C++ libp2p library.

Propose and approve a spend of treasury funds.

## Dispatch Origin

Must be [`Config::SpendOrigin`] with the `Success` value being at least
`amount` of `asset_kind` in the native asset. The amount of `asset_kind` is converted
for assertion using the [`Config::BalanceConverter`].

## Details

Create an approved spend for transferring a specific `amount` of `asset_kind` to a
designated beneficiary. The spend must be claimed using the `payout` dispatchable within
the [`Config::PayoutPeriod`].

### Parameters
- `asset_kind`: An indicator of the specific asset class to be spent.
- `amount`: The amount to be transferred from the treasury to the `beneficiary`.
- `beneficiary`: The beneficiary of the spend.
- `valid_from`: The block number from which the spend can be claimed. It can refer to
  the past if the resulting spend has not yet expired according to the
  [`Config::PayoutPeriod`]. If `None`, the spend can be claimed immediately after
  approval.

## Events

Emits [`Event::AssetSpendApproved`] if successful.

#1689 Quadrivium Polkadot-SDK improvements proposal 1

No Active Proposals