BitcoinCash/CHIP-VM-Limits
1
Fork 0
Code Issues Pull Requests Releases Activity

Add stakeholder statements

Browse Source
This commit is contained in:
Jason Dreyzehner
2024-10-03 22:43:50 -04:00
parent 6b87d51708
commit 9ee390c3ba
2 changed files with 97 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
stakeholders.md
+91 -1
View File
@@ -24,4 +24,94 @@ This includes approval from nodes, wallets, and other open source software proje
## Stakeholder Responses
_To be collected October 1 to November 14._
<details>
<summary>Pending</summary>
_Full table will be published and continuously updated from October 14 through November 14. For a past example, see [CashTokens Stakeholder Responses](https://github.com/cashtokens/cashtokens/blob/master/stakeholders.md#stakeholder-responses)._
</details>
## Statements
The following public statements have been submitted in response to this CHIP.
### Approve
The following articles have been published in support of this CHIP:
- [bitjson.com](https://bitjson.com/) (October 1, 2024): "[2025 Bitcoin Cash Improvement Proposals](https://blog.bitjson.com/2025-chips/)"
The following statements have been submitted in support of this CHIP.
> The VM Limits CHIP retargets Bitcoin Cash's Denial-of-Service limits to extend compute for real contracts by more than 100x while reducing worst-case node compute usage by 50%. By reducing overhead, the retargeted limits simplify contracts, reduce transaction sizes, streamline contract audits, and improve overall security.
>
> By improving contract efficiency, this upgrade also makes important use cases more practical, including post-quantum cryptography, stronger escrow and settlement strategies, zero-knowledge proofs, homomorphic encryption, and other crucial innovations for the future security and competitiveness of Bitcoin Cash.
>
> Finally, this upgrade raises the bar by contributing new tooling and a cross-implementation benchmarking methodology to continuously verify node performance. Beyond empirically verifying the safety and correctness of the upgrade, these tools will simplify development of new production-ready implementations, prevent regressions in existing implementations, and reduce the cost of verifying implementation-specific software updates.
>
> I'm confident in the extensive cross-implementation testing and verification performed for this CHIP, and I recommend activation in Bitcoin Cash's 2025 upgrade.
>
> —<cite>Jason Dreyzehner, [Bitauth IDE](https://ide.bitauth.com), [Chaingraph](https://chaingraph.cash/), [Libauth](https://libauth.org/)</cite>
> I, Calin Culianu, believe the VM Limits and BigInt CHIPs should be included in the BCH upgrade for May 2025.
>
> I was excited about the VM Limits CHIP from at least February of 2024 and began considering it and trying out toy implementations of the earlier version of the CHIP since then. I subsequently worked with Jason a great deal with lots of back and forth in order to evolve the design, and I'm very confident in the final VM Limits CHIP design and rationale. I believe it will unlock a lot of extra capabilities for smart contracts on BCH, as well as plug some performance holes in terms of worst-case performance.
>
> In short: As a result of working on the VM Limits implementation for BCHN, I came to deeply understand its design and rationale and definitely endorse it. I think it is very well thought out and the idioms and costing concepts it invents give us new "knobs" to turn should we decide to turn up the script execution engine limits in the future. It is the right design, and it can take us into the future.
>
> Additionally – The BigInt CHIP came up as an offshoot of the VM Limits work. I believe bringing ~80k-bit integers to BCH script is a huge step forward as it unlocks many previously-impossible contract capabilities. While working on a proof of concept implementation of this CHIP, I was shocked at how fast BigInts are and how low the performance cost for allowing them truly is. It's a no-brainer in my mind to add this additional BigInt CHIP. What's more, VM Limits + BigInt work perfectly together and the costing scheme involved in VM Limits keeps the BigInt changes constrained, so no contract can abuse BigInts to create "poison" transactions or blocks that overuse CPU or memory when validating.
>
> As a Bitcoin Cash developer with many years of experience in this space, I endorse both the VM Limits and BigInt CHIPs for the upcoming May 2025 upgrade to BCH.
>
> —<cite>Calin Culianu, [Bitcoin Cash Node](https://bitcoincashnode.org/) contributor, [Fulcrum](https://github.com/cculianu/Fulcrum) lead developer, [Electron Cash](https://electroncash.org/) contributor</cite>
> I fully support the `CHIP-2021-05-vm-limits: Targeted Virtual Machine Limits` proposal for Bitcoin Cash. This upgrade enables more advanced, efficient smart contracts by removing outdated restrictions while maintaining safeguards, allowing contract authors to focus on application logic rather than working around the limits.
>
> The increased stack element size, revised operation cost system, and targeted hashing limits are well-reasoned improvements enhancing BCH's capabilities without compromising security or performance, and the extensive rationale, benchmarks, and risk assessment provide confidence in its design.
>
> This upgrade is a crucial step in BCH's evolution as a powerful, flexible cryptocurrency platform, and I'm looking forward to designing contract systems leveraging these new features!
>
> —<cite>bitcoincashautist, [CHIP-2023-04 Adaptive Blocksize Limit Algorithm](https://gitlab.com/0353F40E/ebaa) Owner</cite>
> This proposal will unlock the next generation of smart contracts on Bitcoin Cash. Incredibly it unlocks Ethereum-level complexity with no sacrifice at the alter of global state. This will be a huge competitive advantage for Bitcoin Cash in the coming years. The conservative approach to the new limits along with the thorough benchmarking, risk assessment and documentation leave no doubt that we can safely adopt this CHIP in May, and I support doing so.
>
> While the VM Limits proposal unlocks Ethereum-level complexity on Bitcoin Cash, our developer experience (DX) must aim for simplicity. That includes straightforward manipulation of numbers, regardless of their size and without a need for libraries or extra operations. This BigInt proposal will deliver a simple and powerful DX with no compromise on security or performance and I therefore support its adoption."
>
> —<cite>Richard Brady, [Coinbooth](https://coinbooth.io)</cite>
> As a BCH builder and CashScript developer, I wholeheartedly support the VM limits and big integer upgrades proposed by Jason Dreyzehner. These changes are crucial for expanding Bitcoin Cash's smart contract capabilities and improving overall network efficiency.
>
> The density-based limits and removal of arbitrary number size restrictions will enable more complex on-chain applications, benefiting projects like [TokenStork.com](https://tokenstork.com/) and opening new possibilities for CashScript development. The rigorous testing and community-driven approach to these upgrades instill confidence in their implementation.
>
> I believe these enhancements will significantly contribute to Bitcoin Cash's growth as a versatile and powerful Web3 network, aligning well with the goals of increased Bitcoin adoption and usability that drive projects like [BitcoinCashSite.com](https://www.bitcoincashsite.com/).
>
> —<cite>George Donnelly, [Panmoni](https://www.panmoni.com/), [TokenStork](https://tokenstork.com/), [BCH Works](https://www.bitcoincashsite.com/), [BCH Latam](https://www.instagram.com/bchlatam/)</cite>
> As an ecosystem supporter and Fulcrum server operator, I wholly endorse CHIP 2021-05 Targeted Virtual Machine Limits and CHIP 2024-07 BigInt. I have no concern with my node's ability to keep operating effectively, and expect that projects I contribute to will be able to take full advantage of these improvements.
>
> Though a long period of discussion, it appears all major concerns I've seen have been addressed. Frankly, from all I've read, these limits are rather conservative!
>
> The massive work put in by Jason Dreyzehner, Calin Culianu, and bitcoincashautist is inspiring. The attention to detail, time put into addressing concerns, running massive testing suites, etc. I hope to see both CHIPs locked in November, and activated in 2025!
>
> —<cite>Alex ([minisatoshi](https://x.com/_minisatoshi)), [minisatoshi.cash](https://minisatoshi.cash), Fulcrum server operator</cite>
> The VM Limits & BigInt CHIPs expand the power of Bitcoin script within BCH with minimal, if any downside. It's exciting to think about how it could potentially unlock new DeFi applications, and I appreciate the thorough risk assessment documentation that went into the CHIPs. Great work!
>
> —<cite>Jonald, [Electron Cash](https://electroncash.org/) developer</cite>
> Super excited by the new upgrades. VM Limits improvements and Big Integers are going to change the game completely. I have so many ideas for things we can do with these once live. Plus the prep work and test harnesses are top notch. Amazing what happens when devs work together.
>
> —<cite>Josh Ellithorpe, [bitcoincash.org](https://bitcoincash.org/), [BCHN](https://bitcoincashnode.org/) contributor, [Electron Cash](https://electroncash.org/) contributor, Fulcrum server operator</cite>
### Disapprove
The following statements have been submitted from individuals and organizations that disapprove of this CHIP.
_(None)_
### Neutral
The following statements have been submitted from individuals and organizations that abstained from approving this CHIP.
_(None)_