forc deploy with [proxy] reuses the same address across networks (testnet → mainnet), causing deploy failure

[rishabhkeshan]

Related Component

forc-deploy

Problem you are trying to solve

When [proxy] is enabled in forc.toml, doing a testnet/mainnet deploy writes a proxy address into the config. A subsequent alternate deploy reuses that same proxy address, which doesn’t exist on the other network, so the deploy fails. This makes multi-network workflows fragile and forces manual edits to forc.toml between deploys.

Solution you'd like

[proxy]
enabled = true

[proxy.addresses]
testnet = "0x_testnet_proxy"
mainnet = "0x_mainnet_proxy"

Notes

No response

[IGI-111]

A related issue that was mentioned at Forge is how to make this feature deal with local setups:

The proxy enabled flag is very useful to develop games as you can modify the contract while the game is running. Unfotunately the address info is inserted in the Forc.toml which is suppoed to be saved in version control. This means when reseting the dev server or on other mahcine that address migh nto exist and the proxy deploymemt/upgrade will fails

Seems like generally doing the right thing based on the environment you're deploying the proxy in should be thought through.

[luizstacio]

I would say it would be better to have different files, or/env use env variables, or if inside the file make it more flexible:
Ex.:

[proxy.testnet]
address = "0x_testnet_proxy"

[proxy.mainnet]
address = "0x_testnet_proxy"

[proxy.<anything>]
address = "0x_testnet_proxy"

This combined with a option to provide the config you want to use --env mainnet would help. The problem with fixing to just testnet, devnet.... is that if ou have two envs in the same network the problem appears again.

The way we solved this problem with fuels typescript is that, fuels.config.ts is a script and allow people to set things when you start the process of deploy.