Genesis with better support for ipc enabled and ipc disabled use cases

consensus-shipyard / ipc

🌳 Spawn multi-level trees of customized, scalable, EVM-compatible networks with IPC. L2++ powered by FVM, Wasm, libp2p, IPFS/IPLD, and CometBFT.

https://ipc.space

Apache License 2.0

43 stars 39 forks source link

Genesis with better support for ipc enabled and ipc disabled use cases #1102

Open cryptoAtwill opened 3 months ago

cryptoAtwill commented 3 months ago

Genesis should handle ipc enabled and disabled better. Currently the implementation also assumes ipc is enabled and requires artifacts in Hardhat, a proper refactor is needed to handle disabled ipc properly.

raulk commented 2 months ago

This makes sense. You imagine not deploying the gateway and registry contracts if the network is standalone? Is Fendermint capable of detecting this and stop producing checkpoints, prevent messages being sent, etc.? IUC, that's not the case?

Another way to look at this is that we eventually want to support subnet attachment, detachment, and migration. So ideally we should be able to enable and disable this functionality at runtime, for a truly dynamic environment.