Repository navigation
Deterministic Deployment #1
Description
Normally you would use the deterministic deployer or use Nick's method directly to deploy a contract like this to a fixed address.
This isn't simple because gas on Filecoin is computed differently. From my own experience I believe the eth->ewasm gas multiplier is about 440x.
Metadata
Metadata
Assignees
Type
Fields
No fields configured for issues without a type.
Projects
- Status
Activity
wjmelements commentedon Aug 28, 2025
Since the contract is currently under 1k, the filecoin gasUsed is only
14213586, so this is currently possible!jennijuju commentedon Aug 28, 2025
DarkLord017 commentedon Oct 14, 2025
can i work on this @wjmelements ?
wjmelements commentedon Oct 14, 2025
This task should be on-hold until for at least another week because the spec might change again if it turns out we need #2 or #3.
BigLep commentedon Dec 3, 2025
What are the next steps here? Is this needed for GA?
rvagg commentedon Dec 4, 2025
Not strictly needed for GA, just nice to have. And I think the other alternative here is to do this in a slightly less trustless way than "Nick's method", by generating a keypair, making deployment message(s) with it and destroying the private key. I think this is what a lot of other projects to, I believe this is what multicall3 does.
But, this feels very much like a stretch-goal, not necessary functionality wise, just nice if we have the same address everywhere.