# kaal:claim:3782217-004

**Claim.** Any reliance by a DAO on a centralized feature creates a centralized point of failure that threatens the survival of the organization and renders the system technically centralized despite its decentralized appearance.

**Type.** failure  **Support.** argued

**Holds when.**

- DAOs with any centralized dependency, including oracles

**Source quote.**

> Any time your DAO relies on a centralized feature, that is a centralized point of failure that is a threat to the survival of the organization. That means the system is technically centralized.

**From.** Craig Calcaterra, Wulf A. Kaal, *The Importance of History In Decentralization* (2021), Oracles, page 3

**Cite as.** Craig Calcaterra, Wulf A. Kaal, The Importance of History In Decentralization (2021). SSRN: https://ssrn.com/abstract=3782217

**Verify.** sha256 of source PDF `358779557d8e7dcd101720ca0fad90b9146d24f1c7c03909eb431fcf1fb7e103` at https://raw.githubusercontent.com/wulfkaal/Academic-Papers/main/papers/pdf/Calcaterra%20and%20Kaal%20-%202021%20-%20The%20Importance%20of%20History%20In%20Decentralization.pdf

**Failure mode.** centralized-dependency-nullifies-decentralization  (family: recentralization-drift)

**Topics.** smart-contracts, decentralization, dao

**Keywords.** single-point-of-failure, oracles, centralization, dao-design

**Related claims.**

- generalizes: https://wulfkaal.github.io/claims/4015908-026
- generalizes: https://wulfkaal.github.io/claims/4941807-014
- specializes: https://wulfkaal.github.io/claims/3782192-027
- specializes: https://wulfkaal.github.io/claims/3782191-026

**Canonical form.** This markdown file is the canonical hashed representation of the claim. Its sha256 is the content hash used for attestation.