omni-network/omni

E2E deploy requires genesis balance for EOAs

Closed this issue · 0 comments

Problem to Solve

Currrently, the e2e app depends on a couple of EOAs to have a balance of OMNI on Omni EVM to do initial setup. These include (by role)

  • create3-depoloyer
  • deployer
  • admin

We also require the relayer to have some balance, to start relaying messages to Omni's EVM.

This is fine for devnet, staging, and testnet. Though this should not be fine on Mainnet, as the total supply of OMNI on Omni EVM & L1 is goverened by our native bridge. This bridge enforces that all L1 tokens map 1:1 to a token on Omni's EVM.

Unfortunately, we cannot use the native bridge to fund these addresses after deploying Omni's EVM, because the bridge requires the portal to be deployed, and the relayer to be funded.

Proposed Solution

The most promising option is to decrease the pre-allocated balance for each role to some lesser amount, decrement the total prefunded allocations om the native bridge's genesis balance, and transfer that amount to the bridge contract on L1.