💥 Add CREATE, CREATE2, and CREATE3 Deploy Functions

[pcaversaccio]

🕓 Changelog

Vyper has recently introduced the new raw_create built-in function via PR #4204, enabling direct contract creations using the EVM opcodes CREATE and CREATE2. In response, this PR adds CREATE, CREATE2, and CREATE3-based (i.e. without an initcode factor) utility functions to the corresponding module contracts in 🐍 snekmate. Please note that the current upper limit for the contract creation code is set to 8_192 bytes ($2^{13}$).

from snekmate.utils import create as c1
from snekmate.utils import create2 as c2
from snekmate.utils import create3 as c3


@external
@payable
def deploy_create(init_code: Bytes[8_192]) -> address:
    return c1._deploy_create(init_code)


@external
@payable
def deploy_create2(salt: bytes32, init_code: Bytes[8_192]) -> address:
    return c2._deploy_create2(salt, init_code)


@external
@payable
def deploy_create3(salt: bytes32, init_code: Bytes[8_192]) -> address:
    return c3._deploy_create3(salt, init_code)

⚠️ Breaking Changes

To improve clarity and maintain consistent naming conventions, the following name changes are included in this PR:

• create_address.vy → create.vy`
  • _compute_address_rlp_self → _compute_create_address_self
  • _compute_address_rlp → _compute_create_address
  • _convert_keccak256_2_address → _convert_keccak256_to_address
• create2_address.vy → create2.vy
  • _compute_address_self → _compute_create2_address_self
  • _compute_address → _compute_create2_address

These name changes are not backward-compatible and may require code updates in downstream projects.

Furthermore, Solidity has released its latest version v0.8.30. This PR updates the Solidity test files to align with this new version (we keep evm_version = "cancun").

🐶 Cute Animal Picture