go-ethereum/geth-poa
2023-12-20 19:47:04 -08:00
..
frontend new rpc urls for frontend 2023-11-30 19:13:08 -08:00
hyperlane-deployer remove verbose ism config 2023-12-19 13:31:04 -08:00
hyperlane-relayer chore: fix bootnode address in scripts 2023-12-12 16:06:11 +05:30
hyperlane-validator chore: fix bootnode address in scripts 2023-12-12 16:06:11 +05:30
local-l1 docs and naming 2023-12-19 02:50:58 -08:00
util bridge test sh script 2023-12-20 19:47:04 -08:00
.env.example merging geth-poa into go-ethereum repo 2023-11-30 18:07:09 -08:00
.gitignore merging geth-poa into go-ethereum repo 2023-11-30 18:07:09 -08:00
docker-compose.yml docs and naming 2023-12-19 02:50:58 -08:00
Dockerfile working version for block size in bytes 2023-11-30 18:21:37 -08:00
entrypoint.sh Merge branch 'master' into shawn/local-l1 2023-12-19 02:38:05 -08:00
genesis.json Add more funds to initial accounts 2023-12-14 14:09:54 +05:30
Makefile Revert "Update agent images" 2023-12-20 16:24:46 -08:00
README.md Update README.md 2023-12-19 14:00:04 -08:00

geth-poa

Tool for spinning up a POA ethereum sidechain bridged to sepolia via hyperlane token warp route.

Metrics

Metrics recorded by bootnode are exposed to host at http://127.0.0.1:6060/debug/metrics

Key Summary

Testnet private keys are in notion, and need to be copied into an .env.

All relevant accounts are funded on sidechain genesis, you may need to fund these accounts on L1 with faucets. See hyperlane docs.

Contract deployer

Address: 0xBe3dEF3973584FdcC1326634aF188f0d9772D57D

Note if the relayer is emitting errors related to unexpected contract routing, try using a new deployer key pair. It's likely that the current bridge contract deployments are clashing with previous deployments.

You'd need to replace Address above, the allocs field of genesis.json, and the CONTRACT_DEPLOYER_PRIVATE_KEY in .env.

Validator Accounts (also POA signers)

Node1

Address: 0xd9cd8E5DE6d55f796D980B818D350C0746C25b97

Node2

Address: 0x788EBABe5c3dD422Ef92Ca6714A69e2eabcE1Ee4

Relayer

Address: 0x0DCaa27B9E4Db92F820189345792f8eC5Ef148F6

Create2 Deployment Proxy

A Create2 deployment proxy is can be deployed to this chain at 0x4e59b44847b379578588920ca78fbf26c0b4956c. see more here. Note this proxy is required to deploy the whitelist bridge contract, and is consistent to foundry's suggested process for create2 deployment. The deployment signer, 0x3fab184622dc19b6109349b94811493bf2a45362 is funded on genesis.

Local Run

  1. To run the local setup, set the .env file with the keys specified in .env.example.
  2. Run $ make up-dev-build to run the whole stack including bridge, or $ make up-dev-settlement to bring up only the settlement layer.

Starter .env file

To get a standard starter .env file from primev internal development, click here.