Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with create2
Search options not deleted
user 22019
2
votes
Extracting salt from tx's to the CREATE2 deployer contract 0x4e59b44847b379578588920ca78fbf2...
It was quite easy. The salt is the first 32 bytes of the tx.input. So for 0x000000... it was:
0x0000000000000000000000000000000000000000d3af2663da51c10215000000
- 657
2
votes
2
answers
834
views
Extracting salt from tx's to the CREATE2 deployer contract 0x4e59b44847b379578588920ca78fbf2...
I've noticed a pattern in deploying CREATE2 contracts and now I'm trying to find out the salt used. … The reason is, for verifying contracts with CREATE2 on Sourcify salt and the deployerAddress are needed. …
- 657