Phil Ngo

As discussed in Turkey, it makes sense to PR a documentation structure change to outline the docs better, then continuously contribute to updating the content within it. This way, we...

As discussed on the [March 5, 2024 standup](https://github.com/ChainSafe/lodestar/wiki/Lodestar-Planning-&-Standup-Meetings#march-5-2024-planning-and-standup-meeting), it was discussed that we would begin migration to Docusaurus for Lodestar docs due to its flexibility, React-based framework, and compatibility with...

For some alignment on how other ChainSafe projects are setting up their Docusaurus pages, see https://handbook.chainsafe.io/development/documentation/

We only discussed this with Nethermind as they ran tests for which consensus client connected to them was delivering `newPayload` the fastest. My assumption as that all EL clients should...

Can you confirm @tuyennhv that we're no longer seeing this? I took a look at some of our mainnet Lido nodes and it doesn't seem to be that bad on...

This was also visible in Goerli nodes we run using `version=v1.14.0/5ac2fae` which was the stable release: ``` Jan-17 06:32:00.017[network] error: Error on ReqResp.registerProtocol protocolID=/eth2/beacon_chain/req/ping/1/ssz_snappy - Handler already registered for protocol...

I think we should get this fixed (Option 1 or 2) as a lot of contributors likely use Mac for development also. But, I've also never been asked by a...

I think from a design perspective, if we had a profile based solution, does this give us much more flexibility to adapt to various DVT infrastructures? Both Obol and SSV...

Would definitely prefer checksummed also as good standard practice. There's a lot of copying/pasting with these addresses and we should do our part to steward this practice. My preference is...

Ah interesting. I guess if people wanted to have multiple ELs connected to a beacon node, this would make sense to track all of the provider statuses. If they're the...