Skip to content

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

Open
@mr-zwets

Description

@mr-zwets

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    breakingbreaking changecashc-compilerRelates to the cashc compiler

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions