Last night, I ran a node monitoring script to chew through the verifier specs for @Dusk _Foundation, and I just happened to run into the code’s trigger rules for Soft Penalty. My heart sank immediately. When everyone stakes $DUSK , they often only smile at the APY that’s displayed. But honestly, what truly determines whether your earnings get quietly wiped out—or even whether your principal gets damaged—comes down to the locked balance level and that hidden penalty frequency.

In the Succinct Attestation consensus framework for #dusk , whether you’re the Block Generator responsible for producing blocks or the Committee that later performs signature verification, the tokens you hold are not just fuel—they’re basically a bond that the network can seize at any time. The 1,000-token entry requirement is, plain and simple, a ticket. Once the node misses validation because of network jitter and gets hit with a Soft Penalty, the corresponding amount is immediately taken into locked. The portion that gets locked not only can’t earn dividends; if your active stake is even nudged below the minimum line, the node for the next epoch gets kicked out of the candidate set—then all delegated rewards shown up there become zero.$BTC

I actually fell into this trap when I recently built my own node to do testnet load testing. During a top-up, the protocol even comes with a built-in 10% locked dilution; when I added 4,000 more coins, only 3,600 of them were truly immediately able to do the work. Even worse, the shares frozen by penalties can’t be used as soon as they unlock—you have to have them tied to the epoch switch point so they can be unfrozen and restored. Some third-party custodial nodes that appear to advertise extremely high annualized returns on the surface, in their backend logs have missed participation every few days. They look impressive, but in reality the actual returns are just bleak.$ETH

Now when I pick a node, I’ve already quit the habit of blindly chasing high prices. I make sure to use an indexer to dig up—cleanly and thoroughly—how many times that operator has been penalized in the past and how high their locked ratio is. This isn’t something you can mindlessly copy. It all depends on how much validation effort you’re willing to spend for the safety of your funds.@Dusk