mirror of
https://github.com/ethereum/go-ethereum.git
synced 2026-08-09 05:23:47 +00:00
47 lines
1.8 KiB
Markdown
47 lines
1.8 KiB
Markdown
# 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](https://docs.hyperlane.xyz/docs/deploy/deploy-hyperlane#1.-setup-keys).
|
|
|
|
## 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](https://github.com/primevprotocol/deterministic-deployment-proxy). 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
|
|
|
|
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
|
|
```
|
|
|
|
Or if you will use keystore to store private keys, you will need to submit password in .env file:
|
|
```
|
|
MEV_COMMIT_GETH_PASSWORD=primev
|
|
```
|
|
|
|
To get a standard starter .env file from primev internal development, [click here.](https://www.notion.so/Private-keys-and-env-for-settlement-layer-245a4f3f4fe040a7b72a6be91131d9c2?pvs=4), populate only the `NODE1_PRIVATE_KEY` and `NODE2_PRIVATE_KEY` fields.
|