You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: