Jacek Sieka

my preferred solution would involve dynamic runtime selection rather than separate binaries - one approach is to fork blst such that the different platform options each get a fully separate...

their objections so far have been that the optimized operations are too "low-level" to warrant dynamic runtime selection - instead, I'd aim to get a separate symbol namespace all the...

#3080 suggests one approach It's indeed a problem both for VC:s and BN:s, though with the VC, it's very easy to put in the same data dir in the two...

Just noticed this is logged in `Slot start` - however, the times are negative and growing, suggesting something is not quite right :) ``` INF 2022-05-31 15:50:12.001+02:00 Slot start slot=3124751...

> Another reason to why separating the Beacon Node from the Validator Client is attack surface reduction. While this is often mentioned, it is generally the case that the complexity...

> Is there any documented real-world instance where having the VC separate from the BC has resulted in decreased security? A good example is https://blog.staked.us/blog/eth2-post-mortem - this is a professional...

the original nix files remained mostly broken and unmaintained - what's makes this time around different? does anyone else use nix really?

Before we merge this, we should likely do 2 things: * add an option in nimbus to enable/disable it * add metrics in libp2p to monitor the outcome of the...

TODO: * [ ] Evaluate backfill mode in automated checkpoint sync - this is going to trip people syncing from infura etc * [ ] Consider what to do when...

For those looking for behavior similar to checkpoint sync in other clients: ``` # Run TNS when database is missing, skipping the backfill [ -f "$DATADIR/db/nbc.sqlite3" ] || build/nimbus_beacon_node --data-dir:"$DATADIR"...