cerc-io/lighthouse
16
0
Fork 0
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity
1b4545cd9d
lighthouse/scripts/tests/vars.env

65 lines
1.6 KiB
Bash
Raw Normal View History

Fix deneb doppelganger tests (#4124) * Temp hack to compile * Fix doppelganger tests * Kill in groups instead of storing pid * Install geth in CI * Install geth first * Fix eth1_block_hash * Fix directory paths and block hash * Fix workflow for local testnets; reset genesis.json after running script * Disable capella and deneb forks for doppelganger tests * oops not capella * Spin up a spare bn for the doppelganger validator * testing * Revert "testing" This reverts commit 14eb178bca5b7d27b9cd9b665b5cd2c916f50901. * Modify beacon_node script to take trusted peers * Set doppelganger bn as a trusted peer * Update var * update another * Fix port * Add a flag to disable peer scoring * Disable peer scoring in local testnet bn script * Revert trusted peers hack * fmt * Fix proposer boost score
2023-04-26 17:26:00 +00:00
# Path to the geth binary
GETH_BINARY=geth
EL_BOOTNODE_BINARY=bootnode
Doppelganger detection (#2230) ## Issue Addressed Resolves #2069 ## Proposed Changes - Adds a `--doppelganger-detection` flag - Adds a `lighthouse/seen_validators` endpoint, which will make it so the lighthouse VC is not interopable with other client beacon nodes if the `--doppelganger-detection` flag is used, but hopefully this will become standardized. Relevant Eth2 API repo issue: https://github.com/ethereum/eth2.0-APIs/issues/64 - If the `--doppelganger-detection` flag is used, the VC will wait until the beacon node is synced, and then wait an additional 2 epochs. The reason for this is to make sure the beacon node is able to subscribe to the subnets our validators should be attesting on. I think an alternative would be to have the beacon node subscribe to all subnets for 2+ epochs on startup by default. ## Additional Info I'd like to add tests and would appreciate feedback. TODO: handle validators started via the API, potentially make this default behavior Co-authored-by: realbigsean <seananderson33@gmail.com> Co-authored-by: Michael Sproul <michael@sigmaprime.io> Co-authored-by: Paul Hauner <paul@paulhauner.com>
2021-07-31 03:50:52 +00:00
# Base directories for the validator keys and secrets
DATADIR=~/.lighthouse/local-testnet
# Directory for the eth2 config
TESTNET_DIR=$DATADIR/testnet
Fix deneb doppelganger tests (#4124) * Temp hack to compile * Fix doppelganger tests * Kill in groups instead of storing pid * Install geth in CI * Install geth first * Fix eth1_block_hash * Fix directory paths and block hash * Fix workflow for local testnets; reset genesis.json after running script * Disable capella and deneb forks for doppelganger tests * oops not capella * Spin up a spare bn for the doppelganger validator * testing * Revert "testing" This reverts commit 14eb178bca5b7d27b9cd9b665b5cd2c916f50901. * Modify beacon_node script to take trusted peers * Set doppelganger bn as a trusted peer * Update var * update another * Fix port * Add a flag to disable peer scoring * Disable peer scoring in local testnet bn script * Revert trusted peers hack * fmt * Fix proposer boost score
2023-04-26 17:26:00 +00:00
EL_BOOTNODE_ENODE="enode://51ea9bb34d31efc3491a842ed13b8cab70e753af108526b57916d716978b380ed713f4336a80cdb85ec2a115d5a8c0ae9f3247bed3c84d3cb025c6bab311062c@127.0.0.1:0?discport=30301"
Doppelganger detection (#2230) ## Issue Addressed Resolves #2069 ## Proposed Changes - Adds a `--doppelganger-detection` flag - Adds a `lighthouse/seen_validators` endpoint, which will make it so the lighthouse VC is not interopable with other client beacon nodes if the `--doppelganger-detection` flag is used, but hopefully this will become standardized. Relevant Eth2 API repo issue: https://github.com/ethereum/eth2.0-APIs/issues/64 - If the `--doppelganger-detection` flag is used, the VC will wait until the beacon node is synced, and then wait an additional 2 epochs. The reason for this is to make sure the beacon node is able to subscribe to the subnets our validators should be attesting on. I think an alternative would be to have the beacon node subscribe to all subnets for 2+ epochs on startup by default. ## Additional Info I'd like to add tests and would appreciate feedback. TODO: handle validators started via the API, potentially make this default behavior Co-authored-by: realbigsean <seananderson33@gmail.com> Co-authored-by: Michael Sproul <michael@sigmaprime.io> Co-authored-by: Paul Hauner <paul@paulhauner.com>
2021-07-31 03:50:52 +00:00
Fix deneb doppelganger tests (#4124) * Temp hack to compile * Fix doppelganger tests * Kill in groups instead of storing pid * Install geth in CI * Install geth first * Fix eth1_block_hash * Fix directory paths and block hash * Fix workflow for local testnets; reset genesis.json after running script * Disable capella and deneb forks for doppelganger tests * oops not capella * Spin up a spare bn for the doppelganger validator * testing * Revert "testing" This reverts commit 14eb178bca5b7d27b9cd9b665b5cd2c916f50901. * Modify beacon_node script to take trusted peers * Set doppelganger bn as a trusted peer * Update var * update another * Fix port * Add a flag to disable peer scoring * Disable peer scoring in local testnet bn script * Revert trusted peers hack * fmt * Fix proposer boost score
2023-04-26 17:26:00 +00:00
# Hardcoded deposit contract
DEPOSIT_CONTRACT_ADDRESS=4242424242424242424242424242424242424242
Doppelganger detection (#2230) ## Issue Addressed Resolves #2069 ## Proposed Changes - Adds a `--doppelganger-detection` flag - Adds a `lighthouse/seen_validators` endpoint, which will make it so the lighthouse VC is not interopable with other client beacon nodes if the `--doppelganger-detection` flag is used, but hopefully this will become standardized. Relevant Eth2 API repo issue: https://github.com/ethereum/eth2.0-APIs/issues/64 - If the `--doppelganger-detection` flag is used, the VC will wait until the beacon node is synced, and then wait an additional 2 epochs. The reason for this is to make sure the beacon node is able to subscribe to the subnets our validators should be attesting on. I think an alternative would be to have the beacon node subscribe to all subnets for 2+ epochs on startup by default. ## Additional Info I'd like to add tests and would appreciate feedback. TODO: handle validators started via the API, potentially make this default behavior Co-authored-by: realbigsean <seananderson33@gmail.com> Co-authored-by: Michael Sproul <michael@sigmaprime.io> Co-authored-by: Paul Hauner <paul@paulhauner.com>
2021-07-31 03:50:52 +00:00
GENESIS_FORK_VERSION=0x42424242
Fix deneb doppelganger tests (#4124) * Temp hack to compile * Fix doppelganger tests * Kill in groups instead of storing pid * Install geth in CI * Install geth first * Fix eth1_block_hash * Fix directory paths and block hash * Fix workflow for local testnets; reset genesis.json after running script * Disable capella and deneb forks for doppelganger tests * oops not capella * Spin up a spare bn for the doppelganger validator * testing * Revert "testing" This reverts commit 14eb178bca5b7d27b9cd9b665b5cd2c916f50901. * Modify beacon_node script to take trusted peers * Set doppelganger bn as a trusted peer * Update var * update another * Fix port * Add a flag to disable peer scoring * Disable peer scoring in local testnet bn script * Revert trusted peers hack * fmt * Fix proposer boost score
2023-04-26 17:26:00 +00:00
# Block hash generated from genesis.json in directory
Update testnet ETH1_BLOCK_HASH value
2023-05-31 01:54:56 +00:00
ETH1_BLOCK_HASH=add7865f8346031c72287e2edc4a4952fd34fc0a8642403e8c1bce67f215c92b
Fix deneb doppelganger tests (#4124) * Temp hack to compile * Fix doppelganger tests * Kill in groups instead of storing pid * Install geth in CI * Install geth first * Fix eth1_block_hash * Fix directory paths and block hash * Fix workflow for local testnets; reset genesis.json after running script * Disable capella and deneb forks for doppelganger tests * oops not capella * Spin up a spare bn for the doppelganger validator * testing * Revert "testing" This reverts commit 14eb178bca5b7d27b9cd9b665b5cd2c916f50901. * Modify beacon_node script to take trusted peers * Set doppelganger bn as a trusted peer * Update var * update another * Fix port * Add a flag to disable peer scoring * Disable peer scoring in local testnet bn script * Revert trusted peers hack * fmt * Fix proposer boost score
2023-04-26 17:26:00 +00:00
Doppelganger detection (#2230) ## Issue Addressed Resolves #2069 ## Proposed Changes - Adds a `--doppelganger-detection` flag - Adds a `lighthouse/seen_validators` endpoint, which will make it so the lighthouse VC is not interopable with other client beacon nodes if the `--doppelganger-detection` flag is used, but hopefully this will become standardized. Relevant Eth2 API repo issue: https://github.com/ethereum/eth2.0-APIs/issues/64 - If the `--doppelganger-detection` flag is used, the VC will wait until the beacon node is synced, and then wait an additional 2 epochs. The reason for this is to make sure the beacon node is able to subscribe to the subnets our validators should be attesting on. I think an alternative would be to have the beacon node subscribe to all subnets for 2+ epochs on startup by default. ## Additional Info I'd like to add tests and would appreciate feedback. TODO: handle validators started via the API, potentially make this default behavior Co-authored-by: realbigsean <seananderson33@gmail.com> Co-authored-by: Michael Sproul <michael@sigmaprime.io> Co-authored-by: Paul Hauner <paul@paulhauner.com>
2021-07-31 03:50:52 +00:00
VALIDATOR_COUNT=80
GENESIS_VALIDATOR_COUNT=80
Create a local testnet (#2614) The testnet will be on the local computer and have 1 eth1 node, 4 beacon nodes, 1 validator with 20 vc's.
2021-10-01 06:32:37 +00:00
# Number of beacon_node instances that you intend to run
BN_COUNT=4
Doppelganger detection (#2230) ## Issue Addressed Resolves #2069 ## Proposed Changes - Adds a `--doppelganger-detection` flag - Adds a `lighthouse/seen_validators` endpoint, which will make it so the lighthouse VC is not interopable with other client beacon nodes if the `--doppelganger-detection` flag is used, but hopefully this will become standardized. Relevant Eth2 API repo issue: https://github.com/ethereum/eth2.0-APIs/issues/64 - If the `--doppelganger-detection` flag is used, the VC will wait until the beacon node is synced, and then wait an additional 2 epochs. The reason for this is to make sure the beacon node is able to subscribe to the subnets our validators should be attesting on. I think an alternative would be to have the beacon node subscribe to all subnets for 2+ epochs on startup by default. ## Additional Info I'd like to add tests and would appreciate feedback. TODO: handle validators started via the API, potentially make this default behavior Co-authored-by: realbigsean <seananderson33@gmail.com> Co-authored-by: Michael Sproul <michael@sigmaprime.io> Co-authored-by: Paul Hauner <paul@paulhauner.com>
2021-07-31 03:50:52 +00:00
Fix some typos (#3376) ## Proposed Changes This PR fixes various minor typos in the project.
2022-07-27 00:51:06 +00:00
# Number of validator clients
Create a local testnet (#2614) The testnet will be on the local computer and have 1 eth1 node, 4 beacon nodes, 1 validator with 20 vc's.
2021-10-01 06:32:37 +00:00
VC_COUNT=$BN_COUNT
# Number of seconds to delay to start genesis block.
# If started by a script this can be 0, if starting by hand
# use something like 180.
Doppelganger detection (#2230) ## Issue Addressed Resolves #2069 ## Proposed Changes - Adds a `--doppelganger-detection` flag - Adds a `lighthouse/seen_validators` endpoint, which will make it so the lighthouse VC is not interopable with other client beacon nodes if the `--doppelganger-detection` flag is used, but hopefully this will become standardized. Relevant Eth2 API repo issue: https://github.com/ethereum/eth2.0-APIs/issues/64 - If the `--doppelganger-detection` flag is used, the VC will wait until the beacon node is synced, and then wait an additional 2 epochs. The reason for this is to make sure the beacon node is able to subscribe to the subnets our validators should be attesting on. I think an alternative would be to have the beacon node subscribe to all subnets for 2+ epochs on startup by default. ## Additional Info I'd like to add tests and would appreciate feedback. TODO: handle validators started via the API, potentially make this default behavior Co-authored-by: realbigsean <seananderson33@gmail.com> Co-authored-by: Michael Sproul <michael@sigmaprime.io> Co-authored-by: Paul Hauner <paul@paulhauner.com>
2021-07-31 03:50:52 +00:00
GENESIS_DELAY=0
# Port for P2P communication with bootnode
BOOTNODE_PORT=4242
# Network ID and Chain ID of local eth1 test network
Unify execution layer endpoints (#3214) ## Issue Addressed Resolves #3069 ## Proposed Changes Unify the `eth1-endpoints` and `execution-endpoints` flags in a backwards compatible way as described in https://github.com/sigp/lighthouse/issues/3069#issuecomment-1134219221 Users have 2 options: 1. Use multiple non auth execution endpoints for deposit processing pre-merge 2. Use a single jwt authenticated execution endpoint for both execution layer and deposit processing post merge Related https://github.com/sigp/lighthouse/issues/3118 To enable jwt authenticated deposit processing, this PR removes the calls to `net_version` as the `net` namespace is not exposed in the auth server in execution clients. Moving away from using `networkId` is a good step in my opinion as it doesn't provide us with any added guarantees over `chainId`. See https://github.com/ethereum/consensus-specs/issues/2163 and https://github.com/sigp/lighthouse/issues/2115 Co-authored-by: Paul Hauner <paul@paulhauner.com>
2022-06-29 09:07:09 +00:00
CHAIN_ID=4242
Doppelganger detection (#2230) ## Issue Addressed Resolves #2069 ## Proposed Changes - Adds a `--doppelganger-detection` flag - Adds a `lighthouse/seen_validators` endpoint, which will make it so the lighthouse VC is not interopable with other client beacon nodes if the `--doppelganger-detection` flag is used, but hopefully this will become standardized. Relevant Eth2 API repo issue: https://github.com/ethereum/eth2.0-APIs/issues/64 - If the `--doppelganger-detection` flag is used, the VC will wait until the beacon node is synced, and then wait an additional 2 epochs. The reason for this is to make sure the beacon node is able to subscribe to the subnets our validators should be attesting on. I think an alternative would be to have the beacon node subscribe to all subnets for 2+ epochs on startup by default. ## Additional Info I'd like to add tests and would appreciate feedback. TODO: handle validators started via the API, potentially make this default behavior Co-authored-by: realbigsean <seananderson33@gmail.com> Co-authored-by: Michael Sproul <michael@sigmaprime.io> Co-authored-by: Paul Hauner <paul@paulhauner.com>
2021-07-31 03:50:52 +00:00
# Hard fork configuration
Fix deneb doppelganger tests (#4124) * Temp hack to compile * Fix doppelganger tests * Kill in groups instead of storing pid * Install geth in CI * Install geth first * Fix eth1_block_hash * Fix directory paths and block hash * Fix workflow for local testnets; reset genesis.json after running script * Disable capella and deneb forks for doppelganger tests * oops not capella * Spin up a spare bn for the doppelganger validator * testing * Revert "testing" This reverts commit 14eb178bca5b7d27b9cd9b665b5cd2c916f50901. * Modify beacon_node script to take trusted peers * Set doppelganger bn as a trusted peer * Update var * update another * Fix port * Add a flag to disable peer scoring * Disable peer scoring in local testnet bn script * Revert trusted peers hack * fmt * Fix proposer boost score
2023-04-26 17:26:00 +00:00
ALTAIR_FORK_EPOCH=0
BELLATRIX_FORK_EPOCH=0
CAPELLA_FORK_EPOCH=1
Rename eip4844 to deneb (#4129) * rename 4844 to deneb * rename 4844 to deneb * move excess data gas field * get EF tests working * fix ef tests lint * fix the blob identifier ef test * fix accessed files ef test script * get beacon chain tests passing
2023-03-26 15:49:16 +00:00
DENEB_FORK_EPOCH=18446744073709551615
Doppelganger detection (#2230) ## Issue Addressed Resolves #2069 ## Proposed Changes - Adds a `--doppelganger-detection` flag - Adds a `lighthouse/seen_validators` endpoint, which will make it so the lighthouse VC is not interopable with other client beacon nodes if the `--doppelganger-detection` flag is used, but hopefully this will become standardized. Relevant Eth2 API repo issue: https://github.com/ethereum/eth2.0-APIs/issues/64 - If the `--doppelganger-detection` flag is used, the VC will wait until the beacon node is synced, and then wait an additional 2 epochs. The reason for this is to make sure the beacon node is able to subscribe to the subnets our validators should be attesting on. I think an alternative would be to have the beacon node subscribe to all subnets for 2+ epochs on startup by default. ## Additional Info I'd like to add tests and would appreciate feedback. TODO: handle validators started via the API, potentially make this default behavior Co-authored-by: realbigsean <seananderson33@gmail.com> Co-authored-by: Michael Sproul <michael@sigmaprime.io> Co-authored-by: Paul Hauner <paul@paulhauner.com>
2021-07-31 03:50:52 +00:00
Fix deneb doppelganger tests (#4124) * Temp hack to compile * Fix doppelganger tests * Kill in groups instead of storing pid * Install geth in CI * Install geth first * Fix eth1_block_hash * Fix directory paths and block hash * Fix workflow for local testnets; reset genesis.json after running script * Disable capella and deneb forks for doppelganger tests * oops not capella * Spin up a spare bn for the doppelganger validator * testing * Revert "testing" This reverts commit 14eb178bca5b7d27b9cd9b665b5cd2c916f50901. * Modify beacon_node script to take trusted peers * Set doppelganger bn as a trusted peer * Update var * update another * Fix port * Add a flag to disable peer scoring * Disable peer scoring in local testnet bn script * Revert trusted peers hack * fmt * Fix proposer boost score
2023-04-26 17:26:00 +00:00
TTD=0
Create a local testnet (#2614) The testnet will be on the local computer and have 1 eth1 node, 4 beacon nodes, 1 validator with 20 vc's.
2021-10-01 06:32:37 +00:00
# Spec version (mainnet or minimal)
SPEC_PRESET=mainnet
Doppelganger detection (#2230) ## Issue Addressed Resolves #2069 ## Proposed Changes - Adds a `--doppelganger-detection` flag - Adds a `lighthouse/seen_validators` endpoint, which will make it so the lighthouse VC is not interopable with other client beacon nodes if the `--doppelganger-detection` flag is used, but hopefully this will become standardized. Relevant Eth2 API repo issue: https://github.com/ethereum/eth2.0-APIs/issues/64 - If the `--doppelganger-detection` flag is used, the VC will wait until the beacon node is synced, and then wait an additional 2 epochs. The reason for this is to make sure the beacon node is able to subscribe to the subnets our validators should be attesting on. I think an alternative would be to have the beacon node subscribe to all subnets for 2+ epochs on startup by default. ## Additional Info I'd like to add tests and would appreciate feedback. TODO: handle validators started via the API, potentially make this default behavior Co-authored-by: realbigsean <seananderson33@gmail.com> Co-authored-by: Michael Sproul <michael@sigmaprime.io> Co-authored-by: Paul Hauner <paul@paulhauner.com>
2021-07-31 03:50:52 +00:00
# Seconds per Eth2 slot
SECONDS_PER_SLOT=3
# Seconds per Eth1 block
SECONDS_PER_ETH1_BLOCK=1
Fix doppelganger script (#3988) ## Issue Addressed N/A ## Proposed Changes The doppelganger tests were failing silently since the `PROPOSER_BOOST` config was not set. Sets the config and script returns an error if any subprocess fails.
2023-02-21 23:45:43 +00:00
# Proposer score boost percentage
Post merge local testnets (#3807) ## Issue Addressed N/A ## Proposed Changes Modifies the local testnet scripts to start a network with genesis validators embedded into the genesis state. This allows us to start a local testnet without the need for deploying a deposit contract or depositing validators pre-genesis. This also enables us to start a local test network at any fork we want without going through fork transitions. Also adds scripts to start multiple geth clients and peer them with each other and peer the geth clients with beacon nodes to start a post merge local testnet. ## Additional info Adds a new lcli command `mnemonics-validators` that generates validator directories derived from a given mnemonic. Adds a new `derived-genesis-state` option to the `lcli new-testnet` command to generate a genesis state populated with validators derived from a mnemonic.
2023-05-17 05:51:54 +00:00
PROPOSER_SCORE_BOOST=70
Fix doppelganger script (#3988) ## Issue Addressed N/A ## Proposed Changes The doppelganger tests were failing silently since the `PROPOSER_BOOST` config was not set. Sets the config and script returns an error if any subprocess fails.
2023-02-21 23:45:43 +00:00
Update `BlindedBlobsBundle` SSZ list max length and update builder tests (#4710) * Update mev-rs and ethereum-consensus * Fix mock buidler open bid to return fork versioned response * Update `mev-rs` and `ethereum-consensus` * Remove BuilderKzgCommitments and use BlockBodyKzgCommitments everywhere. * Update testnet scripts to support builder testing and update README.md. * Add comment on `mev-rs` version. * Add `BN_ARGS` config to `./scripts/tests/vars.env` * Update builder testing command in README.md * Reject zero block hash payloads after Bellatrix. * Update scripts/local_testnet/README.md Co-authored-by: realbigsean <seananderson33@GMAIL.com> --------- Co-authored-by: realbigsean <seananderson33@GMAIL.com>
2023-09-09 06:10:15 +00:00
# Command line arguments for beacon node client
BN_ARGS=""
Doppelganger detection (#2230) ## Issue Addressed Resolves #2069 ## Proposed Changes - Adds a `--doppelganger-detection` flag - Adds a `lighthouse/seen_validators` endpoint, which will make it so the lighthouse VC is not interopable with other client beacon nodes if the `--doppelganger-detection` flag is used, but hopefully this will become standardized. Relevant Eth2 API repo issue: https://github.com/ethereum/eth2.0-APIs/issues/64 - If the `--doppelganger-detection` flag is used, the VC will wait until the beacon node is synced, and then wait an additional 2 epochs. The reason for this is to make sure the beacon node is able to subscribe to the subnets our validators should be attesting on. I think an alternative would be to have the beacon node subscribe to all subnets for 2+ epochs on startup by default. ## Additional Info I'd like to add tests and would appreciate feedback. TODO: handle validators started via the API, potentially make this default behavior Co-authored-by: realbigsean <seananderson33@gmail.com> Co-authored-by: Michael Sproul <michael@sigmaprime.io> Co-authored-by: Paul Hauner <paul@paulhauner.com>
2021-07-31 03:50:52 +00:00
# Enable doppelganger detection
Post merge local testnets (#3807) ## Issue Addressed N/A ## Proposed Changes Modifies the local testnet scripts to start a network with genesis validators embedded into the genesis state. This allows us to start a local testnet without the need for deploying a deposit contract or depositing validators pre-genesis. This also enables us to start a local test network at any fork we want without going through fork transitions. Also adds scripts to start multiple geth clients and peer them with each other and peer the geth clients with beacon nodes to start a post merge local testnet. ## Additional info Adds a new lcli command `mnemonics-validators` that generates validator directories derived from a given mnemonic. Adds a new `derived-genesis-state` option to the `lcli new-testnet` command to generate a genesis state populated with validators derived from a mnemonic.
2023-05-17 05:51:54 +00:00
VC_ARGS=" --enable-doppelganger-protection "
Reference in New Issue Copy Permalink