wormhole/ethereum
bruce-riley 018908a420
Klaytn mainnet deploy (#1185)
* Klaytn mainnet deploy
2022-05-16 10:06:17 -04:00
..
contracts eth: token bridge transfer with payload 2022-05-11 21:24:36 -04:00
migrations
scripts algo: contracts 2022-04-29 20:56:17 -04:00
test eth: token bridge transfer with payload 2022-05-11 21:24:36 -04:00
.dockerignore
.env.acala.testnet
.env.aurora.mainnet
.env.aurora.testnet
.env.celo.mainnet Celo mainnet deploy changes 2022-05-13 13:11:28 -04:00
.env.celo.testnet Celo testnet support (#1051) 2022-04-28 12:20:38 -04:00
.env.fantom.mainnet
.env.fantom.testnet
.env.karura.mainnet Karura mainnet deploy (#1142) 2022-05-02 14:28:17 -04:00
.env.karura.testnet
.env.klaytn.mainnet Klaytn mainnet deploy (#1185) 2022-05-16 10:06:17 -04:00
.env.klaytn.testnet
.env.moonbeam.testnet Moonbeam to testnet (#1150) 2022-05-10 11:23:07 -04:00
.env.template
.env.test eth-devnet init with multiple guardians 2022-04-12 20:37:52 -05:00
.gitignore
1conf.patch
Dockerfile
Makefile
README.md Add to ethereum contract integration test coverage (#1053) 2022-04-14 10:11:04 -04:00
VERIFY.md
copy-from-container.sh
devnet_mnemonic.txt
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
truffle-config.js Klaytn mainnet deploy (#1185) 2022-05-16 10:06:17 -04:00
truffle-verify-constants.patch Add aurora 2022-04-12 14:30:35 -04: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.