mirror of https://github.com/ethereum/go-ethereum.git synced 2026-07-29 08:03:48 +00:00

History

kant777 e680d3588b Update entrypoint.sh		2024-01-20 02:22:08 -08:00
..
local-l1	docs and naming	2023-12-19 02:50:58 -08:00
util	Update deploy_create2.sh	2024-01-19 02:29:14 -08:00
.env.example	name change	2023-12-26 16:07:07 -08:00
.gitignore	merging geth-poa into go-ethereum repo	2023-11-30 18:07:09 -08:00
docker-compose.yml	Merge pull request #15 from primevprotocol/rm-bridge	2024-01-11 12:57:20 -08:00
Dockerfile	Update Dockerfile	2023-12-21 04:33:01 -08:00
entrypoint.sh	Update entrypoint.sh	2024-01-20 02:22:08 -08:00
genesis.json	account funded on genesis - new hyperlane deployer	2024-01-10 02:51:16 -08:00
Makefile	Update Makefile	2024-01-05 23:56:59 -08:00
README.md	docs adjustment	2024-01-05 23:42:54 -08:00

README.md

geth-poa

Tool for spinning up a POA ethereum sidechain.

Metrics

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

Key Summary

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

POA signers

Node1

Address: 0xd9cd8E5DE6d55f796D980B818D350C0746C25b97

Node2

Address: 0x788EBABe5c3dD422Ef92Ca6714A69e2eabcE1Ee4

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

To run the local setup, set the .env file with the keys specified in .env.example.
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

The chain must be started with two private keys for POA signers.

.env file should look like:

NODE1_PRIVATE_KEY=0xpk1
NODE2_PRIVATE_KEY=0xpk2

To get a standard starter .env file from primev internal development, click here., populate only the NODE1_PRIVATE_KEY and NODE2_PRIVATE_KEY fields.