# Design requirements

`kaal:entity:design-requirements`

**Status.** derived

This node is assembled mechanically from the 4 claims that carry the concept tag `design-requirements`. 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

4 claims across 3 works, 2017 to 2026.

**2017**

- [2992962-028](https://wulfkaal.github.io/claims/2992962-028) [condition/asserted] -- The first of the two core requirements the authors set for distributed jurisdiction is that the anonymity of blockchain based smart contracting be maintained as the technology evolves.
  > Our proposal in this paper for a distributed jurisdiction over blockchains has to fulfill two core requirements: 1. The anonymity of blockchain-based smart contracting has to be maintained as the technology evolves.
  Wulf A. Kaal, Craig Calcaterra, Crypto Transaction Dispute Resolution (2017). SSRN: https://ssrn.com/abstract=2992962
- [2992962-029](https://wulfkaal.github.io/claims/2992962-029) [condition/argued] -- The second core requirement of distributed jurisdiction is governance from within the blockchain technology itself, which is what allows the problems inherent in blockchain based smart contracts to be effectively addressed.
  > Distributed Jurisdictional means necessitate governance from within the blockchain technology itself to effectively address the problems inherent in blockchain-based smart contracts.
  Wulf A. Kaal, Craig Calcaterra, Crypto Transaction Dispute Resolution (2017). SSRN: https://ssrn.com/abstract=2992962

**2021**

- [3808859-039](https://wulfkaal.github.io/claims/3808859-039) [design/asserted] -- A truly decentralized public blockchain must satisfy three simultaneous requirements: no points of centralization and corruption, full security at the level of proof of work, and transaction throughput above one hundred thousand transactions per second.
  > That is, a public blockchain that is not subject to points of centralization and corruption, that is fully secure at the level of proof of work security with a transaction throughput of over one hundred thousand transactions per seconds.
  Wulf A. Kaal, Decentralization – Why We Need Technology Infrastructure Upgrades (2021). SSRN: https://ssrn.com/abstract=3808859

**2026**

- [6192998-007](https://wulfkaal.github.io/claims/6192998-007) [empirical/argued] *(failure mode)* -- The Calcaterra, Kaal, and Andrei 2018 framework satisfied manipulation resistance, autonomous operation, and computational tractability, but struggled with capturing nuanced quality, attributing value across cumulative contributions, and incentivizing knowledge sharing; existing frameworks achieve at most two or three of the six properties at once.
  > The Calcaterra-Kaal-Andrei framework (2018) achieved properties 1, 5, and 6 but struggled with 2, 3, and 4. Existing frameworks achieve at most 2-3 of these properties simultaneously.
  Wulf A. Kaal, Evolution of Domain-Specific Reputation Systems From Binary Validation to Citation-Weighted Knowledge Attribution (2026). SSRN: https://ssrn.com/abstract=6192998

## 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/design-requirements.md | sha256sum

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