<summary><strong>Table of Contents</strong></summary>
- [Stakeholder Responses](#stakeholder-responses)
- [Nodes](#nodes)
- [Wallets](#wallets)
- [Projects](#projects)
- [Industry](#industry)
- [Statements](#statements)
- [Disapprove](#disapprove)
- [Neutral](#neutral)
- [Approve](#approve)
</details>
The goal of the [Cash Improvement Proposal (CHIP) process](https://blog.bitjson.com/bitcoin-cash-upgrade-2023/#why-chips) is to coordinate upgrades to Bitcoin Cash without a central authority by developing proposals in a collaborative, public process.
**CHIP maintainers are expected to actively seek out stakeholders and demonstrate widespread ecosystem approval.**
This includes approval from nodes, wallets, and other open source software projects, educational institutions and community initiatives, and industry actors like exchanges, miners, services, and other businesses.
_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:
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.
> 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.
> The re-targeted VM Limits CHIP solves a real, pressing problem for BCH smart contract developers while also improving the network's security by preventing some worst-case malicious contracts. The research and testing that went into this CHIP is of outstanding quality and sets a standard for future proposals to aspire to.
> 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!
> I'm excited about all the possibilities that the VM Limits and BigInt CHIPs enable. Additionally, the simplified contract development is a significant advantage, as it makes it easier for new talent to start building. I approve of activating these CHIPs in 2025.
>
> —<cite> [OPReturnCode](https://github.com/OPReturnCode/), [BCHD](https://github.com/gcash/bchd) lead developer, [Electron Cash](https://electroncash.org/) contributor</cite>
> BCH has always been smart internet money. Bitcoin Verde supports the bch-bigint and bch-vm-limit CHIPs for the Bitcoin Cash 2025 upgrade. This upgrade enables smart contracts like never seen before on BCH.
>
> —<cite>Josh Green ([@joshmgreen](https://x.com/joshmgreen/status/1844052791255499140)), [Bitcoin Verde](https://bitcoinverde.org/)</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."
> 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/).
> 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!
> 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!
> 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.
> Based on the significant benefits these two CHIPs offer the Bitcoin Cash network and decentralised p2p cash, both of these CHIPs have my full endorsement for implementation for the May 2025 BCH upgrade.
> As a software developer in the #BitcoinCash ecosystem I have reviewed and endorse both VM Limits and the BigInt changes for activation in May 2025. All concerns I have raised have been adequately addressed and I believe the value provided clearly outweigh the cost and risks.
> I formally support activation of the following two CHIPs for the Bitcoin Cash (#BCH💚) 2025 upgrade cycle:
>
> - CHIP-2021-05 VM Limits: Targeted Virtual Machine Limits
> - CHIP-2024-07 BigInt: High-Precision Arithmetic for Bitcoin Cash
>
> These two CHIPs dramatically increase the power of the BCH Script engine, while also making it significantly more efficient.
>
> The VM Limits CHIP implements a new script budgeting system that maximizes the resources available to a script without introducing any new worst-case scenarios or DoS vectors.
>
> This allows contract developers to reduce the complexity of their scripts while also affording them increased power and flexibility. Despite the increased flexibility, these scripts do not negatively affect the BCH economic model, as the budgeting system is measured against a standard P2PKH transaction as a baseline for worst-case validation times.
>
> The companionate BigInt CHIP enables the script engine to operate on integers of any magnitude (hundreds or thousands of digits). This allows contract and wallet developers access to bleeding-edge crypto technology such as quantum-resistant wallets, zero-knowledge-proof verification, and on-chain encryption.
>
> The benchmarking suite that was developed to R&D this CHIP is also quite impressive: it thoroughly tests every possible combination of arithmetic opcodes in order to prove that worst-case transaction validation times are not negatively impacted by the changes proposed in this CHIP.
>
> Overall, this CHIP (which started research in 2021, with the BigInt CHIP ending up as a "freebie" thanks to the new budgeting system) has a very clear analysis of benefits, risks, and implementation costs. On behalf of myself, [Selene Wallet](https://selene.cash/), [bch.ninja](https://bch.ninja/), and [XULU.TECH LLC](https://xulu.tech/), I couldn't be more excited to endorse activation of these two CHIPs for the November lock-in.
> I support BigInt and VM Limits CHIPs. It had me on stronger escrow contracts and post-quantum cryptography. BCH is making it nearly impossible for other coins to compete.
> I'm often humbled by the big brains in the #BitcoinCash space. When asked to submit my 0.00006 #BCH on the proposed 2025 CHIP for VMLimits & BigInt, I thought; I'm in no way qualified to weigh in on such matters. From a tech/dev perspective, I truly am not!
>
> Then, I realized that it's not JUST about the tech...it's also about timing, striking while the iron is hot and doubling-down on the #BitcoinCash momentum we're seeing happen right now! This is something I DO know a lot about, having single-handedly built a business from the ground up and seizing opportunities in a timely manner when they presented themselves.
>
> It might just be me, but I can't help feeling like we're at the dawn of some really big things with #BitcoinCash. For that reason, and FWIW, I fully support the 2025 CHIP for VMLimits & BigInt (bonus👊). I think NOT capitalizing on this opportunity (that's been three years in the making) will come with bigger opportunity costs than the low-risk of moving ahead NOW with this thoroughly vetted CHIP in May of 2025!
>
> We all stand on the shoulders of giants in one way or another and I take comfort knowing we have some of the biggest giants, brains and heavyweights in all of Crypto!
>
> Let's add rocket-fuel to the #BCH Script Engine!🚀 Bring on the smart contract and #BCH DApp goldush!⛏️ Release the horde of new developers, users and converts!🤯
> The VM Limits and BigInt CHIPs sound great, I support activation in 2025. I think the cost for the network is that nodes have to implement high-precision arithmetic which will make accounting more accurate. I love to have more tests and benchmark so we can move forward with confidence.
>
> —<cite>Damascene, [Testnet faucet](tbch.googol.cash), [Hur project](https://hur-project.gitlab.io/hur-freelancers/), [Flipstarters on Bitcoin Cash](https://flipstarters.bitcoincash.network/)</cite>
> As a developer of Opal Wallet, I fully endorse the activation of CHIP-2024-07-BigInt and CHIP-2021-05-vm-limits in the upcoming 2025 Bitcoin Cash upgrade. These improvements are key to realizing Bitcoin Cash's vision as true electronic cash, optimizing contracts and transactions on-chain.
> For Opal Wallet, these CHIPs will directly enhance features such as:
>
> - Batch Payments: Enabling businesses to make bulk payments more efficiently.
> - Reduced Fees: Leveraging high-precision BigInt operations to reduce contract sizes and transaction fees for users.
> - Improved UTXO Management: Expanding capabilities for handling complex UTXOs, enhancing user control, privacy, and efficiency.
>
> These upgrades enhance BCH's scripting abilities without compromising speed or security, aligning with our mission to provide the best possible Bitcoin Cash experience to all users.
>
> —<cite>Coda Beatrix ([@codabeatrix](https://x.com/codabeatrix)), Developer at [58 Opals](https://58opals.com), Developer of [SwiftFulcrum](https://github.com/58opals/SwiftFulcrum)/[Opal Base](https://github.com/58opals/OpalBase)/[Opal Wallet](https://opalwallet.cash)</cite>
> I looked over the VM Limits and BigInt CHIPs, and I support activation in 2025. These proposals seem like a sensible thing to do, since most of these limits were set 10+ years ago, for hardware that would be considered barely functional today. Seems like these proposals should enable much more interesting use cases.
