6 ms·
You’re mistaken, validators and stakers are one and the same. A 51% attack becomes unbelievably more expensive in a proof of stake system, especially because at
by zaptrem 4y ago
You’re mistaken, validators and stakers are one and the same. A 51% attack becomes unbelievably more expensive in a proof of stake system, especially because at the end of it all of your money is burned (whereas with POW you get to keep the GPUs unless they change the algo).
- spywaregorilla 4y agostakers/validators vs. slashers
- PretzelPirate 4y agoThere is no defined role called a “slasher”. There are randomly-decided committees that are regularly updated as part of Ethereum PoS consensus that play different roles. Your validator could be in any one of those roles (or in a pending state) at any time.
- spywaregorilla 4y agoI'm almost certain that is incorrect. This is an optional, expensive seeming process. e.g. https://docs.prylabs.network/docs/prysm-usage/slasher https://docs.prylabs.network/docs/prysm-usage/slasher
- deleted 4y ago[deleted]
- AlexandrB 4y ago> Running a slasher is not meant to be profitable. Slashing is meant to be rare and whistleblower rewards are purposefully low. Running a slasher is meant to be an altruistic action, and as stated, only a single, honest, properly functioning slasher needs to be active in the network to catch slashable offenses. Hmmm. It seems dangerous to rely on altruistic enforcement in a network built around economic incentives. What if the altruistic slashers are simply paid money to turn off their nodes?
- exo762 4y agoHow can you detect that people are NOT running slasher nodes? This model assumes that 1/n is honest. This is almost as safe as it gets.
- AlexandrB 4y agoDepends how big "n" is. It's certainly not the number of ETH users. Running a slasher currently requires 1TB of SSD among other things[1]. I assume these requirements will grow with the popularity of ETH? If so, in a world where 100TB of SSD space is required the number of individuals who can run slashers drops rapidly. In the extreme case, aren't we looking at a small(er) number of well-funded organizations doing all the slashing? [1] https://docs.prylabs.network/docs/prysm-usage/slasher https://docs.prylabs.network/docs/prysm-usage/slasher > However, home stakers are advised not to run a slasher on personal hardware, as it is a tremendously resource-hungry process. Slasher is very heavy on database access and disk usage, and the slasher.db will quickly grow to 1TB or more when running on mainnet.
- NavinF 4y agoA 1TB SSD is like $50. I put one in a small USB-C M.2 case and use it as a flash drive. I’m pretty sure hardware costs will always be a rounding error compared to the $50k that “home stakers” need if they want to run their own validator.
- PretzelPirate 4y agoYou’re misunderstanding. Enabling the “slasher feature” on your validators is an option that any validator can do, not something that only “approved” validators can do. There’s no one gate keeping your ability to become a slasher as long as you run a validator, and there’s no centralized entity deciding whether or not to slash someone’s stake.
- mypastself 4y agoWhat happens if the majority of infrastructure is provided by a small number of cloud computing services? An attacker with access to those services needn’t stake their own funds, and an “attack” might simply entail complying with local laws.
- lupire 4y agoThe 51% is staked coins, not computers.
- mypastself 4y agoDoesn’t staking require active validator software on a computer with a great deal of uptime?
- deleted 4y ago[deleted]
- overtonwhy 4y agoWhat about a DDoS attack?