
Graffiti Watermarks
Title Image by MMT from Pixabay For a while now, we’ve been looking at client diversity, and sometimes beating the drum pretty hard admittedly, to try to make sure everyone understands what it is and why we care… Sites like clientdiversity.org have done a good job of socialising some of the data, and a lot of people are sitting up and taking notice, which is awesome. The gap, as always with these kinds of things, is a lot of data is ‘opt in’ - where people go out of their way to volunteer dat...

Withdrawals
Ethereum - WithdrawalsSince the advent of the Beacon Chain, we asked for a stake for validators. At the time our story was basically "Once the merge is done, you'll be able to get these funds back". So, the merge is done, and it was successful, but the elephant in the room was that it didn't actually include the ability to get your funds back. It turns out that the merge was pretty complicated, and withdrawals are a tiny bit complicated, and to add another feature was potentially in...

Synchronised functions vs Locks
Cover photo by Life Of Pix: https://www.pexels.com/photo/brass-colored-metal-padlock-with-chain-4291/ The year is winding down, so why not take a moment to revisit a bugbear. We have this really simple concept in Teku around slashing protection, where we’ve ensured someone can’t be slashed with quite a simple set of functionality and data. It all comes down to 1 validator, 1 file, 3 numbers. This works really really well. It’s backed by code that uses a synchronized function - the implication...
Protocol engineer on the Teku consensus-layer client.
I’ve setup this blog as a space to share ideas. Currently it’ll be consensus-layer centric, as that is my expertise. Maybe people will find it insightful, ultimately I’m representing my opinions, and it may not be 100% accurate. If there’s issues let me know and I’ll attempt to rectify any inaccuracies that you may have found.
I’ve setup this blog as a space to share ideas. Currently it’ll be consensus-layer centric, as that is my expertise. Maybe people will find it insightful, ultimately I’m representing my opinions, and it may not be 100% accurate. If there’s issues let me know and I’ll attempt to rectify any inaccuracies that you may have found.

Graffiti Watermarks
Title Image by MMT from Pixabay For a while now, we’ve been looking at client diversity, and sometimes beating the drum pretty hard admittedly, to try to make sure everyone understands what it is and why we care… Sites like clientdiversity.org have done a good job of socialising some of the data, and a lot of people are sitting up and taking notice, which is awesome. The gap, as always with these kinds of things, is a lot of data is ‘opt in’ - where people go out of their way to volunteer dat...

Withdrawals
Ethereum - WithdrawalsSince the advent of the Beacon Chain, we asked for a stake for validators. At the time our story was basically "Once the merge is done, you'll be able to get these funds back". So, the merge is done, and it was successful, but the elephant in the room was that it didn't actually include the ability to get your funds back. It turns out that the merge was pretty complicated, and withdrawals are a tiny bit complicated, and to add another feature was potentially in...

Synchronised functions vs Locks
Cover photo by Life Of Pix: https://www.pexels.com/photo/brass-colored-metal-padlock-with-chain-4291/ The year is winding down, so why not take a moment to revisit a bugbear. We have this really simple concept in Teku around slashing protection, where we’ve ensured someone can’t be slashed with quite a simple set of functionality and data. It all comes down to 1 validator, 1 file, 3 numbers. This works really really well. It’s backed by code that uses a synchronized function - the implication...
Share Dialog
Share Dialog
Protocol engineer on the Teku consensus-layer client.
Subscribe to Rolfy.eth
Subscribe to Rolfy.eth
<100 subscribers
<100 subscribers
No activity yet