# Redundancy

`kaal:entity:redundancy`

**Status.** derived

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

6 claims across 5 works, 2021 to 2024.

**2021**

- [3782191-033](https://wulfkaal.github.io/claims/3782191-033) [mechanism/argued] -- Centralized organizations are more effective and efficient than decentralized ones at the singular task they were designed for, because an optimally centralized structure has no redundancy while decentralization takes longer to locate the right components within its network.
  > Given a specific task, centralized organizations are more effective at the task they are designed for than decentralized organizations.
  Craig Calcaterra, Wulf A. Kaal, Preface to (2021). SSRN: https://ssrn.com/abstract=3782191
- [3782192-024](https://wulfkaal.github.io/claims/3782192-024) [design/argued] -- Decentralization, though it may look wastefully redundant, gives every member greater autonomous power, whereas centralization limits members' powers and reduces them to cogs in the machine.
  > Decentralization, while it may be seen as wastefully redundant, gives every member greater autonomous power. Centralization limits its members' powers, reducing them to mere cogs in the machine.
  Craig Calcaterra, Wulf A. Kaal, Introduction to Decentralization (2021). SSRN: https://ssrn.com/abstract=3782192
- [3782198-033](https://wulfkaal.github.io/claims/3782198-033) [failure/argued] *(failure mode)* -- Blockchain transactions will always be expensive whether or not proof of stake is solved, because full participation requires downloading the entire transaction history to verify validity, an extreme redundancy that cannot be removed.
  > If you want to fully participate in the network, you need to download a copy of the entire history of every transaction of every bitcoin in existence. This extreme re- dundancy and inefficiency means transactions will always be expensive.
  Craig Calcaterra, Wulf A. Kaal, Contemporary Decentralization (2021). SSRN: https://ssrn.com/abstract=3782198
- [3782198-039](https://wulfkaal.github.io/claims/3782198-039) [failure/argued] *(failure mode)* -- Ethereum is Turing complete in theory but cannot practically match even a cheap smartphone, because everything stored on the blockchain must be stored redundantly on thousands of nodes forever, so decentralized smart contract computation is necessarily primitive compared with centralized Web 2.0 services.
  > However, Ethereum is not practically capable of mimicking the power of even the cheapest smartphone. The storage limit is currently extremely small, because anything stored in the blockchain needs to be stored redundantly on thousands of nodes for all time in the future.
  Craig Calcaterra, Wulf A. Kaal, Contemporary Decentralization (2021). SSRN: https://ssrn.com/abstract=3782198
- [3782217-005](https://wulfkaal.github.io/claims/3782217-005) [failure/argued] *(failure mode)* -- Where a DAO is automated around a single centralized point of failure, the work of decentralizing and giving members redundant power is wasted, because the point of failure functions as a supreme leader and full centralization would be more efficient.
  > In that case it would be more efficient to completely centralize around the single point of failure the DAO is automated around. The effort you're making to decentralize and give each member redundant power is wasted, because the point of failure might as well be the supreme leader.
  Craig Calcaterra, Wulf A. Kaal, The Importance of History In Decentralization (2021). SSRN: https://ssrn.com/abstract=3782217

**2024**

- [4734750-034](https://wulfkaal.github.io/claims/4734750-034) [failure/argued] *(failure mode)* -- Centralized requesters buy quality through redundancy, assigning up to fifteen workers to the same task to form consensus, which multiplies cost, produces waste, and pushes micro task worker rates down.
  > Requiring requesters to pay proportionally (e.g. up to 15 times) for work per project results in waste. The necessity of multiplication of work also subjects micro task workers to lower rates and lack of payment increases.
  Wulf A. Kaal, Code Review DAO (2024). SSRN: https://ssrn.com/abstract=4734750

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

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