dankrad
dankrad
https://spadina.beaconcha.in/validator/2621 Graffiti: 'sparkpool | prysm'
https://medalla.beaconcha.in/validator/6545 Graffitis: poapFA4yQ0B9peFxKji9NocEShBGTHwA, railgun.eth Eth1 address: 0xA29FD283430Ab091434161Ec847A125BDAB0230F
See https://medalla.beaconcha.in/validator/5212 (no blocks proposed, so graffiti not known)
Suggested API for VC to communicated with SSV node (SSV node will emulate BN API to VC, to keep things simple)
Starting a validator client for the same validator twice is of course a user error. However, it's probably the most common user error that leads to slashing. If the to...
**Rationale:** The quadratic inactivity leak is a penalty for being offline that increases in time quadratically in periods where the beacon chain doesn't finalized. It has the effect that should...
We need to prevent validators from exiting voluntarily if any of these conditions are fulfilled: - Open chunk/bit challenges - Custody keys not revealed This was originally implemented by the...
Suggestion, but not sure if it breaks when multiple operations are involved: move the last element to the index that is cleared, and reduce the length by one. That way...
I estimate that computing a custody bit comes at a CPU cost of ca. 1-5ms: The main computation is just to compute a Universal Hash Function, which is just evaluating...
At the moment, we have an architecture of a Beacon Node (BN) that does all networking, fork choice rule, state transition etc. work and a Validator Client (VC) whose very...