# Stake grinding

`kaal:entity:stake-grinding`

**Status.** derived

This node is assembled mechanically from the 2 claims that carry the concept tag `stake-grinding`. It is a roster of what the corpus says under this term. It is **not** an adjudicated definition: no single statement here has been ruled canonical, and no first-appearance call has been made. Read the claims and judge for yourself.

## Every claim under this term

2 claims across 2 works, 2018 to 2025.

**2018**

- [3125827-017](https://wulfkaal.github.io/claims/3125827-017) [mechanism/argued] -- SPoS makes stake grinding impossible by deriving the pseudo random seed from a hash of the alphabetized join of the symmetric keys all validators submit during vote revealing; the protocol holds even if only a single validator is not colluding.
  > in SPoS the seed used is a hash of the joined alphabetized symmetric keys that were submitted by all validators during the vote revealing process. This protocol completely prevents stake grinding even if only one validator is not colluding.
  Craig Calcaterra, Wulf A. Kaal, Secure Proof of Stake Protocol (2018). SSRN: https://ssrn.com/abstract=3125827

**2025**

- [5225296-014](https://wulfkaal.github.io/claims/5225296-014) [mechanism/argued] -- Stake-grinding, where validators manipulate randomness to favor their own selection, is countered in SPoS by reputation staking combined with community oversight.
  > Stake-grinding, where validators manipulate randomness to favor themselves, is countered by reputation staking and community oversight, ensuring consensus integrity
  Wulf A. Kaal, Cryptographic Foundations and Interdisciplinary Dimensions of the Secure Proof of Stake (SPoS) Conse (2025). SSRN: https://ssrn.com/abstract=5225296

## Verify

Every claim above resolves to a record carrying a verbatim source quote, the sha256 of the source PDF, and a preformatted citation. Nothing here asks to be taken on trust.

    curl -s https://wulfkaal.github.io/entities/stake-grinding.md | sha256sum

**Canonical form.** This markdown file is the canonical hashed representation of this entity node. Its sha256 is the content hash.