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
Copy file name to clipboardExpand all lines: README.md
+28-1Lines changed: 28 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,6 +32,12 @@ If you are deploying the receiver to a new chain, you will also need to supply a
32
32
33
33
If you are redeploying the receiver to an existing chain, you will want to deploy the latest copy of the receiver contract for that chain with any changes desired. Similarly, the construction addresses for the Wormhole Core Contracts and sender will need to be supplied. Additionally, you will need to use the current receiver implementation to send a governance message to the Uniswap V3 deployment on that chain to update it's trusted receiver to point to the new implementation.
34
34
35
+
The receiver contract can be deployed via a Foundry script. The `RPC_URL` environment variable must be set to a valid RPC url and a wallet must be made accessible to the forge script. More on how this can be done [here](https://www.getfoundry.sh/forge/scripting#providing-a-private-key).
**BNBChain**: BNBChain's `UniswapWormholeReceiver` does not match this repository 1:1. Notably, it uses a hard coded, public `BSC_CHAIN_ID` value rather than the public immutable `chainId` used in this repository. Otherwise it is functionally identical.
0 commit comments