solidity-benchmarks icon indicating copy to clipboard operation
solidity-benchmarks copied to clipboard

Benchmarks of popular contract implementations in solidity

Solidity Benchmarks

Benchmarks for popular implementations of contract standards.

⚠️ The gas usage shown in the benchmarks doesn't take into account the 21k gas added to every ethereum transaction

  • ERC20 0.8.10
  • ERC721 0.8.10
  • ERC1155 0.8.10 (wip)

You can see benchmarks for different compiler versions on benchmarks/

The file data.json provides a json format of all the data used in the benchmarks. That file is generated by running the command make json.

Method used

We create a minimal implementation of each contract that uses the specific implementation as a base. Then for each of the methods we want to benchmark, we create a test contract that set the environment in the setUp function and each test only runs the specific function we're benchmarking, trying to reduce the noise as much as possible.

The gas usage shown here is not 100% accurate, but it's good enough to be able to compare the gas usage between the implementations.

All tests are generated using the template files in templates

All tables in the readmes are generated using the scripts in scripts

Contributing

If you want to add another implementation, please open an issue with a link to the repo, or try adding it yourself by using the instructions below.

How to add a contract

Dependencies

  • You'll need python 3 installed to run the scripts under the scripts folder
  • pip install -r requirements.txt (or pip3 depending on ur environment)

Instructions

  1. Create a minimal implementation on src/, the contract name and file name should follow the convention <Contract Type>_<Variation>.
  2. Implement the common interface that is in other files of the same contract type (for ERC721 for example, it's mint and safeMint functions)
  3. Add an entry to the contracts.<contract type>.variations property on test-cases.yml, following the examples there.
  4. Add an entry to scripts/.py's variants var following the examples there. It should map the variant name you used in the contract like ERC721_<Variant> to the name you want to appear on the table. E.g.:
variations = {
    "OZ": "Open Zeppelin",
    "OZEnumerable": "Open Zeppelin Enumerable",
    "Solmate": "Solmate",
    "A": "ERC721A",
    "B": "ERC721B",
    "K": "ERC721K",
}
  1. Run the following commands:
make codegen
make snapshot
make readme
  1. Add the contract to the list at the top of the <Contract Type>.md. (If you added a new ERC721, update the list on top of ERC721.md)

Quick links

ERC20

  • 0.8.10
  • 0.8.11
  • 0.8.12
  • 0.8.13

ERC721

  • 0.8.10
  • 0.8.11
  • 0.8.12
  • 0.8.13

ERC1155

  • 0.8.10
  • 0.8.11
  • 0.8.12
  • 0.8.13