ETH-Staking-Service-22Cap-Signaling VS stressapptest

I tried to help u/superphiz with his 22% limit (see: my GitHub page where I tried to help community engagement). Outside of a few token responses by projects that would never reach 22% anyway, nothing. Funnily enough, to Lido's credit (yucky!) they were actually one of the few projects to take the request seriously, although it was shot down by governance pretty handily. I don't care enough to link the thread (unless you really want me too, I can), but Lido governance made it clearly it doesn't really think they are doing anything wrong. They view themselves as a Union type entity. And while I've saved my hear the struggle by not keeping up with it... I'm doubtful much of their internally proposed solutions to help mitigate risk made it to pass, or were super low hanging fruit.

If I became a HOP delegate, this would be my first time doing any type of delegated governance work. So I can understand some hesitation in delegating to a new coming. However, between the general knowledge throughout my history in the space and my involvement in other projects I think I can do a good job at it. Some examples where I've been part of projects to better the Ethereum ecosystem include content creation for Support1559.org (no longer functional, so here is the GitHub referencing that as part of a bigger EIP1559 signaling project), ethsunshine.com (commits), and ethmerge.com (joint commit). I also took a stab an aggregating commitments to 22% staking caps (GitHub Page), as well as am one of the multisig members of the EVMavericks project. Those have all had varying degrees of success, but they have been steps in my goal of being more than a passive investor. As noted above, I think trying out the delegate space is sort of a new mountain to conquer, hence my hemming and hawing about it broadly.

HERE is the current list of staking entities that have either committed, not committed, or haven't responded. As always, any suggestions, content to add, or Pull Requests are welcome!

As always, the list can be found here of entities who have not made commitments yet.

In the meantime, our work is not done. There are still 20 other staking entities with over .1% of network penetration that have not committed to capping at 22%. Over the weekend I created a page to track all the staking entities commitments - https://github.com/BobRossiETH/ETH-Staking-Service-22Cap-Signaling. Getting a big list of committed entities will go a long way to putting pressure on the Lido DAO to commit as well. It will be a harder sell for someone to limit themselves if no one else is doing it...

Quick update since last night. What started with just Stakewise now has Rockepool and Swell Network publicly committing to keep their Validator share under 22% of the network! Progress can be tracked here - https://github.com/BobRossiETH/ETH-Staking-Service-22Cap-Signaling

That's super old and not very useful anymore. Use Google's stressapptest Might also be worth booting Windows for TM5 or HCI Memtest.

I've personally used stressapptest a lot ( https://github.com/stressapptest/stressapptest ), it's not perfect but it's easy to use from a linux CLI. If that can run for a whole day without spitting out errors then it's probably not the RAM

You're running linux? You should try GSAT for validating memory OC stability and stress testing.

For what it's worth, this was one of the semi-popular "new" memory testing tools doing the rounds back when Ryzen was new: https://github.com/stressapptest/stressapptest

You need to run some memory stress test to verify that, like google's stressapptest (runs in Linux only)

It's not guaranteed that 2 kits will work together, but given the total dearth of 4-DIMM kits on the market, that's probably what you'll have to do. Give it a good overnight burn-in test with prime95 large FFTs, and maybe Google stressapptest, especially if you enable XMP.

If trying to repair the windows install does shit the bed, one debug step you could try would be making a bootable linux usb to see whether that exhibits the same crash behavior. It could pull a bit of double-duty if you run a memory-focused stress tester like: https://github.com/stressapptest/stressapptest to see if it throws up any errors. If you go with a semi-recent Ubuntu release, that one is already in the official software repositories and thus easy to install.

Prime95, Intel Linpack or Linpack Xtreme, y-cruncher, GSAT, Blender 3D rendering, Linux kernel compilation works very well too.

I'd recommend the (former) Google stressapptest: https://github.com/stressapptest/stressapptest