https://github.com/pcaversaccio/create-util

Helper smart contract to make easier and safer usage of the `CREATE` EVM opcode.
https://github.com/pcaversaccio/create-util

create deployment ethereum smart-contracts solidity

Last synced: 11 days ago
JSON representation

Helper smart contract to make easier and safer usage of the `CREATE` EVM opcode.

• Host: GitHub
• URL: https://github.com/pcaversaccio/create-util
• Owner: pcaversaccio
• License: mit
• Created: 2021-11-02T15:42:35.000Z (about 3 years ago)
• Default Branch: main
• Last Pushed: 2024-10-26T17:55:59.000Z (18 days ago)
• Last Synced: 2024-10-26T19:46:21.318Z (18 days ago)
• Topics: create, deployment, ethereum, smart-contracts, solidity
• Language: TypeScript
• Homepage:
• Size: 3.24 MB
• Stars: 19
• Watchers: 3
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# `CREATE` Factory

[![🕵️‍♂️ Test smart contracts](https://github.com/pcaversaccio/create-util/actions/workflows/test-contracts.yml/badge.svg)](https://github.com/pcaversaccio/create-util/actions/workflows/test-contracts.yml)

[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/license/mit)

Helper smart contract [`Create`](./contracts/Create.sol) to make easier and safer usage of the [`CREATE`](https://www.evm.codes/#f0) Ethereum Virtual Machine (EVM) opcode. `CREATE`, in a way, does a built-in call. What actually happens is that the data passed to that call isn't the contract bytecode, it's the **init bytecode** (a.k.a. creation bytecode).

When the `CREATE` opcode is executed, the EVM creates a call frame in the context of the new contract (e.g. `address(this)` is the new contract's address). This executes the data passed to `CREATE` as the code, which in higher level languages is basically the constructor. At the end of this init stuff, it returns the actual code of the contract that is stored in the state trie.

The easiest way to think about it, which is also fairly accurate, is that the Solidity compiler takes all the executional code of the contract, compiles it to bytecode, and adds it as a return statement at the end of the constructor.

The smart contract [`Create`](./contracts/Create.sol) also provides a function `computeAddress` that returns (via the Recursive Length Prefix (RLP) encoding scheme) the address where a contract will be stored if deployed via `CREATE`.

## Test Deployments

- Sepolia: [`0x910F5D1Ec00F5E7226A14eAAeD8C3b5B03E11950`](https://sepolia.etherscan.io/address/0x910F5D1Ec00F5E7226A14eAAeD8C3b5B03E11950)

- Holešky (Holešovice): [`0x910F5D1Ec00F5E7226A14eAAeD8C3b5B03E11950`](https://holesky.etherscan.io/address/0x910F5D1Ec00F5E7226A14eAAeD8C3b5B03E11950)

## `CREATE2` Factory

A helper smart contract to make easier and safer usage of the [`CREATE2`](https://eips.ethereum.org/EIPS/eip-1014) EVM opcode can be found [here](https://github.com/pcaversaccio/create2deployer) (a.k.a. [`Create2Deployer`](https://github.com/pcaversaccio/create2deployer/blob/main/contracts/Create2Deployer.sol)) and [here](https://github.com/pcaversaccio/createx) (a.k.a. [`CreateX`](https://github.com/pcaversaccio/createx/blob/main/src/CreateX.sol); a versatile, trustless, and stateless successor to `Create2Deployer`).