certusone
/
wormhole-networks
mirror of https://github.com/certusone/wormhole-networks.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update mainnet info

This commit is contained in:
Leo 2021-10-27 01:57:34 +02:00
parent aace1efff0
commit 8777c9721c
1 changed files with 6 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
mainnetv2/info.md
View File

@ -10,7 +10,7 @@ Wormhole mainnet connects the following chains:
- Binance Smart Chain mainnet.
It runs the [v2.4.0](https://github.com/certusone/wormhole/releases/tag/v2.4.0) guardiand reference implementation.
It runs the [v2.5.0](https://github.com/certusone/wormhole/releases/tag/v2.5.0) guardiand reference implementation.
## Network parameters
@ -32,31 +32,14 @@ Connected chain contracts:
| Binance Smart Chain (Impl) | [`0x736d2a394f7810c17b3c6fed017d5bc7d60c077d`](https://bscscan.com/address/0x736d2a394f7810c17b3c6fed017d5bc7d60c077d) |
| Solana Mainnet | [`worm2ZoG2kUd4vFXhvjh93UUH596ayRfgQ2MgjNMTth`](https://explorer.solana.com/address/worm2ZoG2kUd4vFXhvjh93UUH596ayRfgQ2MgjNMTth) |
| Terra Columbus-5 | [`terra1dq03ugtd40zu9hcgdzrsq6z2z4hwhc9tqk2uy5`](https://finder.terra.money/columbus-5/address/terra1dq03ugtd40zu9hcgdzrsq6z2z4hwhc9tqk2uy5) |
| Polygon Mainnet (Core) | [`0x7A4B5a56256163F07b2C80A7cA55aBE66c4ec4d7`](https://polygonscan.com/address/0x7A4B5a56256163F07b2C80A7cA55aBE66c4ec4d7#code) |
| Polygon Mainnet (Impl) | [`0xd2F50cAFfCaf238a0C3e78Ce81c5BF7D9f7f3350`](https://polygonscan.com/address/0xd2F50cAFfCaf238a0C3e78Ce81c5BF7D9f7f3350#code) |
Eth and BSC use the same deployer key, leading to identical addresses. This key has no privileges.
## Terra Multisig
Columbus-4 does not allow contracts to upgrade themselves. Therefore, the Columbus-4 contract has been deployed
using a multisig wallet:
| Holder | Key |
|----------------|--------------------------------------------------------------------------------|
| Certus One | `terrapub1addwnpepq2sakzkw3dz427pj9rudtvdjmpjs7k3cah6afhwarqdtp630tt50ghak5xd` |
| Terraform Labs | `terrapub1addwnpepqtlu2m33tfqgaglayzp2dnhv6s8994qcvuqtv5t3jsegrt58dt39jn5mt8v` |
| P2P Validator | `terrapub1addwnpepqtmgahrsyw6t7d48zr7yxml4ydy8mjp67tkxsdhexf7fy0tkgeez204um3y` |
Resulting wallet: `terra1xcp70wju9rsdh466y9g6a3c8shhuggdqmq8987`
Once Terra was upgraded to Columbus-5, this multisig wallet will be used to redeploy the Wormhole contract.
After the upgrade, the contract will be governed by the guardian set, eliminating the need for the multisig wallet.
## Guardian set
Current generation: **1**.
See [v1.prototext](guardianset/v1.prototxt) for the first guardian set update that will be executed once everyone's
node on the network is live.
Current generation: **1** (see [v1.prototext](guardianset/v1.prototxt)).
## Example command line options
@ -77,6 +60,7 @@ ExecStart=/opt/wormhole/wormhole/build/bin/guardiand node \
--network "/wormhole/mainnet/2" \
--ethContract "0x98f3c9e6E3fAce36bAAd05FE09d375Ef1464288B" \
--bscContract "0x98f3c9e6E3fAce36bAAd05FE09d375Ef1464288B" \
--polygonContract "0x7A4B5a56256163F07b2C80A7cA55aBE66c4ec4d7" \
--solanaContract "worm2ZoG2kUd4vFXhvjh93UUH596ayRfgQ2MgjNMTth" \
--terraContract "terra1dq03ugtd40zu9hcgdzrsq6z2z4hwhc9tqk2uy5" \
--adminSocket /run/guardiand/admin.socket \
@ -86,6 +70,7 @@ ExecStart=/opt/wormhole/wormhole/build/bin/guardiand node \
--guardianKey "/opt/wormhole/keys/wormhole-guardian.key" \ # <-- your guardian key generated by "guardiand keygen"
--ethRPC "wss://your-eth-node" \ # <-- your ETH full/light node websocket URI (ws:// or wss://)
--bscRPC "wss://bsc-node.example.com" \ # <-- your BSC full/light node websocket URI
--polygonRPC "wss://polygon-node.example.com" \ # <-- your Polygon Bor full/light node websocket URI
--solanaRPC "http://solana-node:8899" \ # <-- Solana RPC URI
--solanaWS "ws://solana-node:8900" \ # <-- Solana WS URI (typically RPC +1)
--terraWS "ws://terra-node/websocket" \ # <-- Terra node websocket URI