Nimbus ethereum client, More channels on discord: https://discord.gg/XRxWahP
github-actions[bot] on sim-stat
github-actions[bot] on sim-stat
github-actions[bot] on sim-stat
github-actions[bot] on sim-stat
mjfh on master
Snap sync extractor test sub ra… (compare)
mjfh on snap-sync-extractor-test-sub-range-proofs
AdamSpitz on shanghai
Snap sync fix trie interpolatio… bump submodules to further redu… fluffy ci: both testutp and lin… and 3 more (compare)
mjfh on free-parking
mjfh on snap-sync-extractor-test-sub-range-proofs
mjfh on free-parking
Run sub-range proof tests for e… (compare)
mjfh on free-parking
Unit tests to verify calculatio… Changed argument order for `hex… Run sub-range proof tests for e… (compare)
kdeme on master
Fix potential overflow error on… (compare)
kdeme on quick-fix-toPC
jangko on eip-4844
EIP-4844: add pointEvaluation p… EIP-4844: Implement calcExcessD… EIP-4844: Implement gas account… and 10 more (compare)
jangko on bump-submodules
mratsim@discord: Termux, just type on screen.
But you can use a bluetooth keyboard.
zahary@discord: For the record, I did try to program with Salon while holding a baby 😛 Felt like these guys:
merp@discord: Is it possible to compile nimbus for mainnet where the validation client is it’s own separate thing?
It could make for safer setups. The Eth1 and BN don’t contain sensitive info so could be hosted on rented servers with no risk, don’t have info worth stealing, could make setting up failovers simpler (simply duplicate that image), etc.
Meanwhile the one thing actually containing valuable info (the validate client) can be kept safely at home (or maybe even carried on you, powered with a low bandwidth $3/mo IOT sim), with only the BN endpoint connection whitelisted.