tersec

> I find the inconsistency created here a bit hard to justify. What is the evidence that we have users reluctant to use the DEBUG log level specifically due to...

Because that specific inconsistency isn't worthwhile, https://github.com/status-im/nimbus-eth2/pull/4175/commits/a0ae8235b9018423a02a21d0ef891409e1ec730e removes it

As an immediate observation, it should provide this value if and only `value.consensusValue.isSome`: https://github.com/status-im/nimbus-eth2/blob/7c731a2bfb4820ef5c08e5e35df635b986ed4857/beacon_chain/spec/eth2_apis/eth2_rest_serialization.nim#L3397-L3399 The code is there, but for some reason, it doesn't have a consensus value. https://ethereum.github.io/beacon-APIs/?urls.primaryName=dev#/Validator/produceBlockV3 doesn't...

In progress in https://github.com/status-im/nimbus-eth2/pull/5873

https://github.com/status-im/nimbus-eth2/pull/5873

https://github.com/status-im/nimbus-eth2/pull/6022 doesn't replace the "front-end" parts of this, but does provide a new back-end calculation approach

Until https://github.com/ethereum/consensus-specs/pull/3230#issuecomment-1435989902 is done, it's not realistically mergeable.

https://github.com/status-im/nimbus-eth2/pull/5887 might let this build

Why is this a requirement? ``` enr:-LK4QPgEk5jhwZl_XERheLR4VVUZjMHyeWb10n43DloI2jSyLuwtvO0jzl4b6m_pRDYDUjP9sm_f1zDMJ1I7A9ZrtS0Bh2F0dG5ldHOIAAAAAAAAAACEZXRoMpBqlaGpBAAAAP__________gmlkgnY0gmlwhAIDBQeJc2VjcDI1NmsxoQLmX-CWStKtE5U4Gl4AZGzwdWV1_qzeHNiVRQdasc2TO4N0Y3CCFyuDdWRwghQW ``` via https://enr-viewer.com/ has a TCP multiaddr of ``` /ip4/2.3.5.7/tcp/5931/p2p/16Uiu2HAmAvxYZ8XFubDxZb9CiAyxwX1wCh2Q1HyjWqaUDDEk6AiN ``` and a UDP multiaddr of ``` /ip4/2.3.5.7/udp/5142/p2p/16Uiu2HAmAvxYZ8XFubDxZb9CiAyxwX1wCh2Q1HyjWqaUDDEk6AiN ``` And in general, people...

> For reference what are the JSON files we can edit as a workaround in the meantime? (If the validator is imported via API) Either [`keystore.json` or `remote_keystore.json`](https://nimbus.guide/data-dir.html#secrets-and-validators), depending on...