Increase Transaction and Block Memory Units (Part 1 of 2)
227 DReps voted · 76 with a rationale · 2 changed their vote · 3 re-voted unchanged
Open a row to read the rationale.
Changed votes: 2 to no, together voting with 162.3M ₳ of voting power.
- Yes56.1K ₳No rationale
- Yes55.1K ₳Rationale
I very much agree with Pi Lanningham's take on this protocol parameter change. Increasing block mem units is a great way to increase Plutus smart contract transaction throughput for the Cardano ledger without risking an eventual later change (back to a lower value) breaking dApps and protocols that depend on higher tx limits. This will also give us an idea of whether tx limits can and should be changed at a later stage.
- Yes51.8K ₳Rationale
This is important feature with the current development of Cardano, as long as this not complicate and risk the network security or speed
- Yes48.7K ₳Rationale
good
- Yes48K ₳No rationale
- No45.3K ₳No rationale
- Yes41K ₳No rationale
- Yes40.6K ₳No rationale
- Yes36.9K ₳No rationale
- Yes30.9K ₳No rationale
- Yes28.8K ₳No rationale
- Yes26.7K ₳No rationale
- Yes15.7K ₳No rationale
- Yes15.3K ₳No rationale
- Yes10.7K ₳Rationale
I like this proposal, so I vote yes.
- Abstain8.4K ₳No rationale
- Yes6.8K ₳No rationale
- Yes4.1K ₳No rationale
- YesRevoted3.4K ₳Rationale
As a DRep, I support this proposal because it increases the memory limits per transaction and per block for Plutus scripts, which:
Facilitates DApp development on Cardano by reducing technical constraints.
Improves scalability and potentially allows for more Plutus scripts per block.
Is tested and validated on the Preview and PreProd testnets without impacting network security or performance.
Complies with all the safeguards of the Cardano Constitution (PARAM, NETWORK, MTEU-M, MBEU-M).
Is a gradual and reversible change, minimizing any risk to the ecosystem.
This update contributes to a more robust Cardano network and increased adoption of DApps, while remaining compliant with technical and security standards.
Earlier votes
Yes7mo agoSuperseded
- Yes1.2K ₳Rationale
I am voting yes for this proposal because it helps our DApp builders from having to manually optimize due to insufficient Plutus script memory unit limits per transaction. This allows teams to focus on innovation rather than workarounds. This would also allow for more sophisticated smart contract logic, the kind that cannot exist with our 14 million memory unit ceiling. This will unlock new capabilities and use cases for our ecosystem! By allowing more plutus scripts to execute per block, we are greatly enhancing our scalability! This upgrade has been tested as being safe, as it has run on testnet and has passed all the proper safety checks. Let's get it passed!
- Yes688.8 ₳No rationale
- Yes675.6 ₳No rationale
- Yes167.1 ₳No rationale
- Yes116.1 ₳No rationale
- Yes99.5 ₳No rationale
- Yes0 ₳No rationale
- Yes0 ₳No rationale