wormhole/ethereum
Csongor Kiss 58cd031ea8 ethereum: Add verify script to match up the deployed bytecode with the
local build

Also include this step in the generated governance verification instructions
2022-06-30 13:57:02 +01:00
..
contracts evm: Make finality a state variable 2022-06-28 21:31:23 +01:00
migrations evm: Make finality a state variable 2022-06-28 21:31:23 +01:00
scripts ethereum: Add truffle scripts to deploy core & token bridge 2022-06-27 19:19:16 +01:00
test evm: Make finality a state variable 2022-06-28 21:31:23 +01:00
.dockerignore
.env.acala.mainnet Acala mainnet deploy 2022-06-03 14:44:22 -04:00
.env.acala.testnet evm: Make finality a state variable 2022-06-28 21:31:23 +01:00
.env.aurora.mainnet evm: Make finality a state variable 2022-06-28 21:31:23 +01:00
.env.aurora.testnet evm: Make finality a state variable 2022-06-28 21:31:23 +01:00
.env.celo.mainnet evm: Make finality a state variable 2022-06-28 21:31:23 +01:00
.env.celo.testnet evm: Make finality a state variable 2022-06-28 21:31:23 +01:00
.env.fantom.mainnet evm: Make finality a state variable 2022-06-28 21:31:23 +01:00
.env.fantom.testnet evm: Make finality a state variable 2022-06-28 21:31:23 +01:00
.env.karura.mainnet evm: Make finality a state variable 2022-06-28 21:31:23 +01:00
.env.karura.testnet evm: Make finality a state variable 2022-06-28 21:31:23 +01:00
.env.klaytn.mainnet evm: Make finality a state variable 2022-06-28 21:31:23 +01:00
.env.klaytn.testnet evm: Make finality a state variable 2022-06-28 21:31:23 +01:00
.env.moonbeam.testnet evm: Make finality a state variable 2022-06-28 21:31:23 +01:00
.env.neon.testnet evm: Make finality a state variable 2022-06-28 21:31:23 +01:00
.env.template evm: Make finality a state variable 2022-06-28 21:31:23 +01:00
.env.test evm: Make finality a state variable 2022-06-28 21:31:23 +01:00
.gitignore
Dockerfile
Makefile ethereum: add 'make test-upgrade' to simulate contract upgrades against mainnet 2022-06-27 19:19:16 +01:00
README.md
VERIFY.md
copy-from-container.sh
devnet_mnemonic.txt
karura-gas-prices Add script to query karura gas prices 2022-06-25 15:46:15 +01:00
mine.js
package-lock.json Klaytn mainnet deploy (#1185) 2022-05-16 10:06:17 -04:00
package.json Klaytn mainnet deploy (#1185) 2022-05-16 10:06:17 -04:00
simulate_upgrade ethereum: add 'make test-upgrade' to simulate contract upgrades against mainnet 2022-06-27 19:19:16 +01:00
simulate_upgrades ethereum: add 'make test-upgrade' to simulate contract upgrades against mainnet 2022-06-27 19:19:16 +01:00
truffle-config.js clients/js: Use ankr RPC instead of infura 2022-06-27 19:19:16 +01:00
truffle-verify-constants.patch
verify ethereum: Add verify script to match up the deployed bytecode with the 2022-06-30 13:57:02 +01:00

README.md

Wormhole bridge - ETH

These smart contracts allow to use Ethereum as foreign chain in the Wormhole protocol.

The Wormhole contract is the bridge contract and allows tokens to be transferred out of ETH and VAAs to be submitted to transfer tokens in or change configuration settings.

The WrappedAsset is a ERC-20 token contract that holds metadata about a wormhole asset on ETH. Wormhole assets are all wrapped non-ETH assets that are currently held on ETH.

Deploying

To deploy the bridge on Ethereum you first need to compile all smart contracts: npx truffle compile

To deploy you can either use the bytecode from the build/contracts folder or the oz cli oz deploy <Contract> (Documentation).

You first need to deploy one Wrapped Asset and initialize it using dummy data.

Then deploy the Wormhole using the initial guardian key (key_x,y_parity,0) and the address of the previously deployed WrappedAsset. The wrapped asset contract will be used as proxy library to all the creation of cheap proxy wrapped assets.

Testing

For each test run:

Run npx ganache-cli --deterministic --time "1970-01-01T00:00:00+00:00" to start a chain.

Run the all ethereum tests using make test

Run a specific test file using npx truffle test test/wormhole.js

Run a specific test file while skipping compile npx truffle test test/wormhole.js --compile-none

User methods

submitVAA(bytes vaa) can be used to execute a VAA.

lockAssets(address asset, uint256 amount, bytes32 recipient, uint8 target_chain) can be used to transfer any ERC20 compliant asset out of ETH to any recipient on another chain that is connected to the Wormhole protocol. asset is the asset to be transferred, amount is the amount to transfer (this must be <= the allowance that you have previously given to the bridge smart contract if the token is not a wormhole token), recipient is the foreign chain address of the recipient, target_chain is the id of the chain to transfer to.

lockETH(bytes32 recipient, uint8 target_chain) is a convenience function to wrap the Ether sent with the function call and transfer it as described in lockAssets.