CPS-0018? | Greater Transaction Throughput

[bwbush]

The Cardano mainnet occasionally experiences congestion where there are too many transactions in the memory pool to be included in the next block or in the next few blocks. Sometimes the block utilization peaks above 90% for an extended period of time. This not only impacts general user experience but it can also severely impact use cases such as airdrops, oracles, partner chains, DEXes, and Dapps. Emerging use cases and application deployments promise to accelerate the need for high throughput on Cardano. Applied research on several fronts is needed to propose and provide evidence for techniques that increase throughput measured in terms of transactions, transaction size, and script execution units. Such work should be based on a clear understanding of stakeholder requirements.

---

(rendered latest document)

[rphair]

thanks @bwbush & @abailly-iohk - I'd tagged this submission Triage before noticing it was still a draft. If you would like some feedback at the upcoming CIP meeting (https://hackmd.io/@cip-editors/98) please say so and I'll apply that tag again.

Also please update the "latest document" link above if & when the added pathname to your README.md changes.

[bwbush]

@rphair, I made a few revisions in 97908bd and marked this ready for review.

[rphair]

thanks @bwbush - tagging Triage to put this on the same agenda (https://hackmd.io/@cip-editors/101) as

• CIP-0140? | Ouroboros Peras - Faster Settlement #872
• CPS-0017? | Settlement Speed #922

[rphair]

@bwbush this whole series of Consensus submissions has been well received so far & both CPSs and their corresponding CIPs should all have candidate numbers assigned by now. Eventually we would like each CIP to link to the CPS that it "solves" (and vice versa, including in the metadata header). I believe it's a benefit to the community that each solution comes with its own definition of the problem space, to potentially include improvements offered by others.

Please also assign this number by renaming the containing folder & linking to the new pathname of your README file in the original posting at the beginning of the PR. 🎉