improve local deploy handling

[holic]

Just an idea that might help us create more visibility in clients about what is going on under the hood while they wait for their dev:contracts service to boot up or mud deploy to execute:

• use CREATE3 for a deterministic world address, write the world address to disk before deploying
• emit an event (e.g. emit Init()) in the world constructor that represents a deploy, so we can query/poll the RPC for it rather than waiting for a block number (I wish ~all contracts did this)
• move to a single deploys.json file with all the chains -> world addresses to help with vite (messy dynamic imports) and vercel (has a hard time locating static files for dynamic imports)

[ludns]

I agree with this
On 1) This is really useful, and we should move in that direction for all of MUD (systems and modules mostly). the tricky thing is we can't have CREATE2 because it still depends on the deployer address (and ideally the deployer address wouldn't matter).
Having a CREATE3 kind of situation where the address only depends on the the bytecode and a salt would be ideal. We can then get a fresh address for the same world bytecode by changing the salt, and we can set the salt to 0 for systems and modules. That avoids us from having to redeploy the same system or module, we can just check if it already exists!.
On 2) agreed too. Then we don't need startBlockNumber as a parameter ever again.

[holic]

Having a CREATE3 kind of situation where the address only depends on the the bytecode and a salt would be ideal.

whoops, I think CREATE3 is what I meant here!

[ludns]

Actually it's not event that! Had to double check but I also mis-remembered what CREATE3 is
CREATE3:

Deterministic contract address based on msg.sender + salt

We want deterministic contract address based on bytecode + salt.
Something like this would work: https://github.com/Arachnid/deterministic-deployment-proxy

[holic]

If we only have/need world addresses, then another thing we could do is write them all out to a single mapping/manifest file like deploys.json of chain ID => world address (rather than one file per chain). This would make it easier to load them into Vite as one static import, since we've had trouble with dynamic/conditional imports in local and in Vercel.

[holic]

got started on a single deploys file here: #803