Skip to content

Classes of ewasm contracts #173

Open
@axic

Description

@axic

One other idea I was having some thought about is the following:

  • by default ewasm contracts are executed via an interpreter and costs are tuned for that
  • the user can opt to deploy contracts for AOT execution, which has lower gas costs for execution (= more can be done in the same block), but that comes with a larger cost for keeping around the compiled code - so essentially it may result in something like the rent proposal to keep paying for that

Not sure if “Eth 1.x precompiles” are third class of that or maybe they fit into the 2nd case.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions