Skip to content

Explore contract bytesize optimizations possible with the removal of the opcode limit #284

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mr-zwets opened this issue Feb 28, 2025 · 0 comments
Labels
breaking breaking change cashc-compiler Relates to the cashc compiler

Comments

@mr-zwets
Copy link
Member

Before the re-targeted VM Limits on Bitcoin Cash, there was both the Opcode-count and the bytesize limit to take into account.

With the removal of the 201 opcode limit, we can explore contract bytesize optimizations which do increase the opcode usage but this is no longer a separate factor to optimize, as fees are paid on transaction size and computation budget is high with the re-targeted VM Limits.

@mr-zwets mr-zwets added breaking breaking change cashc-compiler Relates to the cashc compiler labels Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking breaking change cashc-compiler Relates to the cashc compiler
Projects
None yet
Development

No branches or pull requests

1 participant