Skip to content

TODO: optimize performance benchmarks #5

@bitjson

Description

@bitjson

Not sure why I didn't use OP_2DROP in the hashing benchmarks? I think those can be made a little more expensive by saving OP_DROPs, doing lots of OP_2DROPs at the end of the contract, and using those saved opcodes for more hashing.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions