tersec
tersec
> isn't this a post-deneb change? Sure, this is a draft/tracking PR. There are already two VCs known which aren't compatible with this, one of which is the Nimbus VC,...
https://github.com/status-im/nimbus-eth2/pull/5842 resolves the Nimbus VC side of this. In theory, post Dencun fork, all the VCs will have to support this, but would need to be verified first.
Apparently, Prysm's validator client is still gRPC-based, so not in scope here.
Alright, will refrain from removing this (and other similar endpoints) for some time.
Does this still apply to Windows Server 2022? https://learn.microsoft.com/en-us/lifecycle/products/windows-server-2019 states that as of `2024-01-09T22:59:59.999-08:00`, Windows Server 2019 is EOL.
This appears to trigger usage of `forkchoiceUpdatedV1` in Jenkins minimal testnet logs, which is (correctly) not in `unstable`. Will recreate and decompose into smaller steps when it comes to doing...
``` fatal: remote error: upload-pack: not our ref dc1992a73be5643cf4b06bd29a22478f8d32513b Errors during submodule fetch: vendor/nim-ssz-serialization ``` probably that's not available in the git repo, but this error triggers regardless on `git...
Is there consensus this is a misguided approach (which I'd tend to believe)? If so, it should be closed.
Incorporated into https://github.com/status-im/nimbus-eth2/pull/5873
- https://github.com/ethereum/remote-signing-api/pull/10