How to double-check your config settings are correct.
<aside> ⚠️ You should always double-check these against the docs and/or by querying the relevant contract for the info.
</aside>
Lido Docs: https://docs.lido.fi/deployed-contracts/
It is suggested that you set & keep these values updated in your .env file so that they are not overwritten by accidental git pull operations etc.
| Obol related settings | |
|---|---|
| CHARON_P2P_RELAYS | Value: |
https://0.relay.obol.tech,<https://1.relay.obol.tech/,https://charon-relay.dsrvlabs.dev/,https://obol-relay.infstones.com:3640/,https://relay-2.prod-relay.721.land/,https://relay-1.obol.figment.io/> |
Can be cross-checked against https://docs.obol.tech/docs/next/faq/risks#risk-obol-hosting-the-relay-infrastructure For possible security concerns, operators are encouraged to check the SSL certs of the listed relays to identify issuing authority and originator.
If clusters are interested in hosting their own relays, they should reach out to Obol and Lido contributors to learn more about how. |
| Lido protocol related settings | |
| VE_LOCATOR_ADDRESS | 0xC1d0b3DE6792Bf6b4b37EccdcC24e45978Cfd2Eb |
| VE_ORACLE_ADDRESSES_ALLOWLIST | Value:
["0x140Bd8FbDc884f48dA7cb1c09bE8A2fAdfea776E","0xA7410857ABbf75043d61ea54e07D57A6EB6EF186","0x404335BcE530400a5814375E7Ec1FB55fAff3eA2","0x946D3b081ed19173dC83Cd974fC69e1e760B7d78","0x007DE4a5F7bc37E2F26c0cb2E8A95006EE9B89b5","0xEC4BfbAF681eb505B94E4a7849877DC6c600Ca3A","0x61c91ECd902EB56e314bB2D5c5C07785444Ea1c8","0x1Ca0fEC59b86F549e1F1184d97cb47794C8Af58d","0xc79F702202E3A6B0B6310B537E786B9ACAA19BAf"]
List as at March 20, 2024 (if you double check and note this is outdated. please inform in Discord so that it can be updated).
Retrieved by calling getMembers() method (read) on the Validator Exit Bus (VEBO) HASH_CONSENSUS contract. If you want to fully double-check the list, you can go from Docs Deployed Contracts → Locator → Read: validatorExitBusOracle() → Read: getConsenusConsensusContract() to find the value of the hash consensus contract address. |
| VE_STAKING_MODULE_ID | Value: 2
Obtained by called getStakingModules() on the Lido Staking Router contract , look for the module with the “SimpleDVT” description. |
| LIDODVEXIT_EXIT_EPOCH | Value: 194048
Shapella Fork Epoch |
| VE_OPERATOR_ID | This is the Node Operator ID for your cluster on https://operators.lido.fi/module/2, available only once the cluster has been created by the Simple DVT Module Multisig. The required value is is the number without the “#” in front (e.g. 0, 1, 12, etc.) |
| Other settings | |
| NETWORK | Value: mainnet |
| LIGHTHOUSE_CHECKPOINT_SYNC_URL | Value: https://mainnet.checkpoint.sigp.io/
User is free to use other checkpoint sync endpoints. | | MEVBOOST_RELAYS | Can differ per cluster; all clusters should use the same set. All relays should come from vetted list by the Relay Maintenance Committee.
List of active and vetted relays for mainnet can be found here: https://enchanted-direction-844.notion.site/6d369eb33f664487800b0dedfe32171e?v=8e5d1f1276b0493caea8a2aa1517ed65&pvs=74 |
| Lido Obol Charon | Current latest version for mainnet: 0.19.1
https://github.com/ObolNetwork/lido-charon-distributed-validator-node/ |
| --- | --- |
| EL and CL clients | If you are using Obol Charon to manage these for you, updates will be pushed by the Obol team when possible so keep your eye on the discord for announcements, but you’re still responsible for maintaining up to date client versions. This can be easily done by pointing to the correct relevant release version for the clients that you are using in your .env, which will supersede possibly older versions specified in the docker-compose.
If you are using nodes external to the Obol Charon deployment, then you need to make sure you are using up to date versions. | | MEV Boost | If you are using Obol Charon to manage this for you, updates will be pushed by the Obol team when possible so keep your eye on the discord for announcements.
If you are using an MEV boost installation external to the Obol Charon deployment, then you need to make sure you are using an up to date version.
https://github.com/flashbots/mev-boost/ | | Ejector | Most likely you are using this and lido charon is installing it for you. You should be using the latest release appropriate for mainnet. If your version is out of date, please ask someone if you should update or not.
You can check the latest release here, but you should only install or use this separately if you know what you are doing. github: https://github.com/lidofinance/validator-ejector docker: https://hub.docker.com/r/lidofinance/validator-ejector/
Current latest version for mainnet: 1.5.0 | | KAPI | Most likely you are not using this if you are participating in Simple DVT, so you can ignore this.
If you are, you should be using the latest release. If your version is out of date, please ask someone if you should update or not.
github: https://github.com/lidofinance/lido-keys-api/ docker: https://hub.docker.com/r/lidofinance/lido-keys-api |