search

Uniswap / permit2

🔑🔑🔑 next generation token approvals mechanism
MIT License
762 stars 188 forks source link

Error CREATE2 Deployer not present on this chain #251

Closed billalxcode closed 6 months ago

billalxcode commented 6 months ago

When i run command

forge script --broadcast --rpc-url https://testnet-rpc.dreyerx.com --private-key <PRIVATE KEY> --verify script/DeployPermit2.s.sol:DeployPermit2

Error stack

[⠒] Compiling...
No files changed, compilation skipped
Traces:
  [2117050] → new DeployPermit2@0x5b73C5498c1E3b4dbA84de0F1833c4a029d90519
    └─ ← [Return] 10353 bytes of code

  [144] DeployPermit2::setUp()
    └─ ← [Return]

  [38897] DeployPermit2::run()
    ├─ [0] VM::startBroadcast()
    │   └─ ← [Return]
    ├─ [0] → new <unknown>@0x8a8dDbE4c64CF1857360DC25883a581933D5ca4b
    │   └─ ← [Revert] 420 bytes of code
    └─ ← [Revert] CREATE2 Deployer (0x4e59b44847b379578588920ca78fbf26c0b4956c) not present on this chain.
For a production environment, you can deploy it using the pre-signed transaction from https://github.com/Arachnid/deterministic-deployment-proxy.
For a test environment, you can use `etch` to place the required bytecode at that address.

Error:
script failed: CREATE2 Deployer (0x4e59b44847b379578588920ca78fbf26c0b4956c) not present on this chain.
For a production environment, you can deploy it using the pre-signed transaction from https://github.com/Arachnid/deterministic-deployment-proxy.
For a test environment, you can use `etch` to place the required bytecode at that address.