In Algorand, every user can participate in the blockchain verification and transaction baking / block production (Pure Proof of Stake). But there are no penalties when a user is malicious - all funds are never at risk. Why the authors disregard slashing for malicious behavior?

Penalizing a participant could be a double ended sword. What if someone is trying to attack the system by making the system believe that valid votes are malicious ? Instead of “punishing” malicious votes, Algorand implementation simply ignores them. Also keep in mind that what seems to you as mali…

What if someone is trying to attack the system by making the system believe that valid votes are malicious Then it’s a form of an attack (because someone is trying to corrupt the system by making true-negatives). Ideally this activity should be handled (and imho penalized). For example, […] int…

I would have to disagree regarding the second paragraph. These users never meant to disturb the system. They only tried to perform their role, and failed due to unexpected lack of resources ( network, cpu or other. it doesn’t matter ). I wouldn’t want to be penalized for trying to help. and I would…

I know that these user don’t want to disturb the system. But the problem is that if there are many of them they unintentionally harm it. Hence the idea to disincentive users who don’t help and almost don’t have any chance to get rewords.

Here is an Ethereum 2.0 design doc which explains there adaptive slashing mechanism. Nice reading: [image] Serenity Design Rationale - HackMD # Serenity Design Rationale See also: the 1.0 design rationale doc from 3-4 years ago https://githu

I agree with Tsachi. I don’t think slashing is necessary and all the slashing logic would increase the complexity of the codebase and the attack surface for no real value added. There is already a cost in making transactions (fee and electricity cost, even if both are low) so a malicious node whose…

This man went deep into the rabbit hole this weekend :rofl:

The problem is that this impacts “normal” users, and there is as time delay for increasing the TX cost.

Why there is no slashing / penalties in Algorand?

General

Andre_M July 30, 2022, 9:41am 8

Holy three years later dude

Topic		Replies	Views
Some Questions About Algorand	5	1308	September 7, 2019
Broken Algorand fork-free property: Another Look at ALGORAND General	4	1737	October 22, 2019
Forking in algorand network - Indefinite stuck better then forking? General	23	3340	June 27, 2021
[Temperature Check] Reward node runners through governance Governance Discussions	18	2013	January 14, 2023
Possible Algorand Attack? 'Continuing Attack' General	7	725	September 2, 2021

Why there is no slashing / penalties in Algorand?

Related topics