You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should instead have a governance parameter for the Ethereum address of the "proxy" smart contract and use that for getting the "bridge" and "governance" smart contract addresses. This should be initialized to the zero Ethereum address at genesis as the Ethereum bridge should not launch straight away at chain launch. The Ethereum oracle component should switch away from using the hardcoded dummy addresses.
We should also have a parameter for the wnam ERC20 contract address.
The text was updated successfully, but these errors were encountered:
james-chf
changed the title
Make a governance parameter for the Ethereum bridge smart contract address
Make a governance parameter for the Ethereum bridge proxy contract address
Oct 7, 2022
james-chf
changed the title
Make a governance parameter for the Ethereum bridge proxy contract address
Make governance parameters for the Ethereum bridge contract addresses
Oct 10, 2022
Currently we hardcode dummy Ethereum addresses for a couple of the bridge smart contracts
namada/apps/src/lib/node/ledger/ethereum_node/oracle.rs
Lines 21 to 23 in 67d9d43
We should instead have a governance parameter for the Ethereum address of the "proxy" smart contract and use that for getting the "bridge" and "governance" smart contract addresses. This should be initialized to the zero Ethereum address at genesis as the Ethereum bridge should not launch straight away at chain launch. The Ethereum oracle component should switch away from using the hardcoded dummy addresses.
We should also have a parameter for the
wnam
ERC20 contract address.The text was updated successfully, but these errors were encountered: