Increase Transaction and Block Memory Units (Part 1 of 2)
227 DReps voted · 74 with a rationale · 5 changed their vote
Open a row to read the rationale.
- Yes52.4K ₳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 ₳No rationale
- Yes50.5K ₳No rationale
- Abstain49.6K ₳Rationale
I choose to ABSTAIN from voting on this proposal due to my current understanding / recollection of parameter change effects and the technical nuances that involve these changes. I must refresh my knowledge of the key parameters before I can vote with confidence in my full understandings of the effects of these changes both positive and negative. Regardless I find value in the ability to allow the developers more "wiggle" room in building and providing services on the blockchain, I applaud the authors of this proposal for the submission.
LourdeOuroborus Imperator Aeternalis~ - Yes48.6K ₳Rationale
good
- Yes46.5K ₳Rationale
This is important feature with the current development of Cardano, as long as this not complicate and risk the network security or speed
- No45.2K ₳No rationale
- Yes40.5K ₳No rationale
- Yes36.3K ₳No rationale
- Yes30.9K ₳No rationale
- YesRevoted28.2K ₳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
Yes6mo agoSuperseded
- Yes26.7K ₳No rationale
- Yes25.7K ₳No rationale
- Yes15.2K ₳No rationale
- Yes10.6K ₳Rationale
I like this proposal, so I vote yes.
- Abstain8.3K ₳No rationale
- Yes8.1K ₳No rationale
- Yes6.7K ₳No rationale
- Yes4.7K ₳No rationale
- Yes4.4K ₳No rationale
- 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!
- Yes682 ₳No rationale
- Yes153.7 ₳No rationale
- Yes123.6 ₳No rationale
- Yes0 ₳No rationale
- Yes0 ₳No rationale
- Yes0 ₳No rationale