{
 "@context": "https://schema.org",
 "@type": "DefinedTerm",
 "@id": "https://wulfkaal.github.io/entities/block-production",
 "identifier": "kaal:entity:block-production",
 "name": "Block production",
 "termCode": "block-production",
 "inDefinedTermSet": {
  "@id": "https://wulfkaal.github.io/entities/index.json"
 },
 "author": {
  "@type": "Person",
  "name": "Wulf A. Kaal",
  "identifier": "https://orcid.org/0000-0003-0757-275X"
 },
 "dateModified": "2026-07-29",
 "canonicalForm": "https://wulfkaal.github.io/entities/block-production.md",
 "sha256": "0ded97e932b2d2015ed1378330d4a92f4e32a2c8882ddb255fd07618c4891628",
 "additionalProperty": [
  {
   "@type": "PropertyValue",
   "name": "status",
   "value": "derived"
  },
  {
   "@type": "PropertyValue",
   "name": "claim_count",
   "value": 4
  },
  {
   "@type": "PropertyValue",
   "name": "work_count",
   "value": 3
  },
  {
   "@type": "PropertyValue",
   "name": "year_span",
   "value": [
    "2018",
    "2025"
   ]
  },
  {
   "@type": "PropertyValue",
   "name": "non_current_claims",
   "value": 0
  }
 ],
 "subjectOf": [
  {
   "@type": "Claim",
   "@id": "https://wulfkaal.github.io/claims/3125827-018",
   "identifier": "kaal:claim:3125827-018",
   "text": "In a distributed system, which cannot achieve constant perfect communication between nodes, it is never possible to determine with certainty that a block producer was censoring particular transactions rather than simply being unaware of them.",
   "abstract": "In a distributed system--which cannot achieve constant perfect communication between nodes--we can never certainly determine that a block producer was censoring certain transactions, instead of simply not being aware of them.",
   "citation": "Craig Calcaterra, Wulf A. Kaal, Secure Proof of Stake Protocol (2018). SSRN: https://ssrn.com/abstract=3125827",
   "datePublished": "2018",
   "claim_type": "failure",
   "confidence": "argued",
   "is_failure_mode": true,
   "scope_conditions": [
    "imperfect communication between nodes",
    "block producers with discretion over transaction inclusion"
   ],
   "source_pdf_sha256": "598d9bd95e4af7a0a35328677c6bfc069f69f2e32c30c720b3a0be98a23a40cb",
   "status": "current"
  },
  {
   "@type": "Claim",
   "@id": "https://wulfkaal.github.io/claims/3266953-019",
   "identifier": "kaal:claim:3266953-019",
   "text": "Under the Anchor Protocol, staking means anchoring reputation to a block, so a block producer whose block turns out to be invalid or is cancelled out suffers depreciation of their reputation.",
   "abstract": "Moreover, staking in the Anchor Protocol means anchoring your reputation to a block. In other words, Semada block producers anchor their reputation to a block, and if the block is invalid or cancelled out, their reputation depreciates.",
   "citation": "Craig Calcaterra, Wulf A. Kaal, Gopinath Sivalingam, Reputation Protocol for the Internet of Trust - Conceptual Whitepaper (2018). SSRN: https://ssrn.com/abstract=3266953",
   "datePublished": "2018",
   "claim_type": "mechanism",
   "confidence": "asserted",
   "is_failure_mode": false,
   "scope_conditions": [
    "Semada block production"
   ],
   "source_pdf_sha256": "781758dea356e55d79c73ad7f1debe7c83de398bd1cd9e0a9a6c2802f276b4c0",
   "status": "current"
  },
  {
   "@type": "Claim",
   "@id": "https://wulfkaal.github.io/claims/3266953-026",
   "identifier": "kaal:claim:3266953-026",
   "text": "Producing a bad block is punished by slashing, since the producer loses the availability stakes they posted to be considered in the random selection of block producers.",
   "abstract": "Producing bad blocks is slashed because the bad block producer will lose their availability stakes (the tokens the producer staked to be considered for the random selection of block producers) in the validation pool.",
   "citation": "Craig Calcaterra, Wulf A. Kaal, Gopinath Sivalingam, Reputation Protocol for the Internet of Trust - Conceptual Whitepaper (2018). SSRN: https://ssrn.com/abstract=3266953",
   "datePublished": "2018",
   "claim_type": "mechanism",
   "confidence": "asserted",
   "is_failure_mode": false,
   "scope_conditions": [
    "blocks rejected by the validation pool"
   ],
   "source_pdf_sha256": "781758dea356e55d79c73ad7f1debe7c83de398bd1cd9e0a9a6c2802f276b4c0",
   "status": "current"
  },
  {
   "@type": "Claim",
   "@id": "https://wulfkaal.github.io/claims/5225296-008",
   "identifier": "kaal:claim:5225296-008",
   "text": "SPoS avoids the delegate centralization of DPoS, where block production concentrates among a small elected set, by distributing block production opportunities across validators in proportion to both reputation and stake.",
   "abstract": "Unlike DPoS, which centralizes block production among a small set of delegates (e.g., 21 in EOS), SPoS balances fairness and randomness by distributing opportunities across validators proportionally to their reputation and stake",
   "citation": "Wulf A. Kaal, Cryptographic Foundations and Interdisciplinary Dimensions of the Secure Proof of Stake (SPoS) Conse (2025). SSRN: https://ssrn.com/abstract=5225296",
   "datePublished": "2025",
   "claim_type": "mechanism",
   "confidence": "argued",
   "is_failure_mode": false,
   "scope_conditions": [
    "contrast with DPoS implementations such as EOS with 21 delegates"
   ],
   "source_pdf_sha256": "b2fec675d906334ad67e13b2d97261dc31e38061022867eb3f9ceadd95f4878d",
   "status": "current"
  }
 ],
 "description": "4 claims in the published works of Wulf A. Kaal carry the concept tag 'block-production'. Derived node: a roster, not an adjudicated definition."
}