# Oracles `kaal:entity:oracles` **Status.** derived This node is assembled mechanically from the 16 claims that carry the concept tag `oracles`. 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 16 claims across 5 works, 2021 to 2025. **2021** - [3782201-035](https://wulfkaal.github.io/claims/3782201-035) [failure/argued] *(failure mode)* -- The hope of most Web3 engineers that overhead institutions can be automated away until they vanish is largely misplaced, because business contracts are not getting simpler as technology becomes more sophisticated. > Decentralized oracles will eliminate the need for any original investigation from independent media. Automated systems will eliminate the middleman. These hopes are largely misplaced. Craig Calcaterra, Wulf A. Kaal, Future of Decentralization (2021). SSRN: https://ssrn.com/abstract=3782201 - [3782205-036](https://wulfkaal.github.io/claims/3782205-036) [design/asserted] -- News services acting as oracles and information repositories must themselves be decentralized if the decentralized economy is to have a trustworthy information layer. > News services (oracles) and information repositories need to be decentralized. Craig Calcaterra, Wulf A. Kaal, Eight Institutions for the Evolution of Decentralization (2021). SSRN: https://ssrn.com/abstract=3782205 - [3782217-004](https://wulfkaal.github.io/claims/3782217-004) [failure/argued] *(failure mode)* -- 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. > 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. Craig Calcaterra, Wulf A. Kaal, The Importance of History In Decentralization (2021). SSRN: https://ssrn.com/abstract=3782217 - [3782217-006](https://wulfkaal.github.io/claims/3782217-006) [mechanism/argued] *(failure mode)* -- A DAO that relies on a centralized oracle will eventually be exploited, because the people controlling the oracle will become aware of their power over automated contract triggers and, given the competitive nature of capitalism, are right to take advantage of it. > Eventually, the people who have the relevant power in the centralized oracle will become aware of the power they have over the DAO. Eventually there will be an opportunity to exploit that information. Craig Calcaterra, Wulf A. Kaal, The Importance of History In Decentralization (2021). SSRN: https://ssrn.com/abstract=3782217 - [3782217-008](https://wulfkaal.github.io/claims/3782217-008) [mechanism/argued] -- A robust decentralized oracle finds better information because averaging across a crowd is typically better for complex situations, being less subject to the prejudices of individuals who hold more limited information, so overestimates and underestimates offset each other. > A robust decentralized oracle would find better information. The wisdom of the crowd can be employed to discover the truth. Averaging information is typically better for any complex situation, since they're less subject to the prejudices of the individual, who has more limited information. Craig Calcaterra, Wulf A. Kaal, The Importance of History In Decentralization (2021). SSRN: https://ssrn.com/abstract=3782217 - [3782217-010](https://wulfkaal.github.io/claims/3782217-010) [condition/argued] -- An oracle DAO must filter its network so that the average member is correct at least slightly more often than incorrect; once that filter holds, larger and more decentralized networks converge on the truth more quickly and more certainly. > So an oracle DAO needs to filter its network to guarantee the average member is correct, at least slightly more than they are incorrect. Then the larger and more decentralized the network becomes, the quicker and more certainly it will converge on the truth. Craig Calcaterra, Wulf A. Kaal, The Importance of History In Decentralization (2021). SSRN: https://ssrn.com/abstract=3782217 - [3782217-011](https://wulfkaal.github.io/claims/3782217-011) [design/argued] -- In the SchellingCoin approach to oracle design, members stake reputation tokens on their answer to the question a DApp is asking and are rewarded according to how close they came to the resulting median value, which functions as the game theoretic Schelling point. > The idea is to have your Oracle DAO members stake their reputation tokens on their answer to a question a DApp is asking. Then you reward those closer to the resulting median value Craig Calcaterra, Wulf A. Kaal, The Importance of History In Decentralization (2021). SSRN: https://ssrn.com/abstract=3782217 - [3782217-012](https://wulfkaal.github.io/claims/3782217-012) [design/argued] -- The protocols governing how a particular oracle question is answered should be set by the subject matter experts themselves rather than by a static centralized hierarchy, because the experts know best how their own system can be gamed and how to prevent that gaming to protect their hard earned reputation. > Giving the experts, them- selves, control of their own organization is better than relying on a static centralized hierarchy. The experts know best how to game their own system, and how to prevent gaming to protect their hard-earned reputation. Craig Calcaterra, Wulf A. Kaal, The Importance of History In Decentralization (2021). SSRN: https://ssrn.com/abstract=3782217 - [3782217-013](https://wulfkaal.github.io/claims/3782217-013) [failure/argued] *(failure mode)* -- Robust decentralized oracles do not yet exist despite well funded proposals, because decentralized oracles are themselves DAOs and therefore inherit the same missing incentive structure, governance processes, and history that all DAOs suffer from. > Put simply, decentralized oracles are DAOs, so they still lack the proper incentive structure and governance processes and history that all DAOs suffer from. Craig Calcaterra, Wulf A. Kaal, The Importance of History In Decentralization (2021). SSRN: https://ssrn.com/abstract=3782217 - [3782217-014](https://wulfkaal.github.io/claims/3782217-014) [condition/argued] -- A decentralized oracle is not secure until it has significant momentum and history, and it is not even truly decentralized until it has a large network of active members. > A decen- tralized oracle is not secure until it has significant momentum and history—an oracle is not even truly decentralized until this is achieved, until it has a large network of active members. Craig Calcaterra, Wulf A. Kaal, The Importance of History In Decentralization (2021). SSRN: https://ssrn.com/abstract=3782217 - [3782217-015](https://wulfkaal.github.io/claims/3782217-015) [design/argued] -- Until decentralized oracle protocols are secure and robustly enacted, projects should rely on centralized oracles while keeping the network's monetary value below the level at which the centralized newsfeed would gain an incentive to manipulate the data. > Until the decentralized protocol is secure and robustly enacted, it is better to rely on centralized oracles, and make sure your network doesn't grow to gain such a large monetary value that an incentive arises for the centralized newsfeed to manipulate the data. Craig Calcaterra, Wulf A. Kaal, The Importance of History In Decentralization (2021). SSRN: https://ssrn.com/abstract=3782217 - [3782217-016](https://wulfkaal.github.io/claims/3782217-016) [failure/argued] *(failure mode)* -- Oracle DAOs and decentralized finance DAOs face a bootstrapping deadlock because each relies on the other for its very existence, a chicken and egg problem the authors address by having participants prove their worth in a development period before they can charge other DAOs fees. > Unfortunately, oracle DAOs and deFi DAOs rely on each other for their very existence. Which will come first, the chicken or the egg? Craig Calcaterra, Wulf A. Kaal, The Importance of History In Decentralization (2021). SSRN: https://ssrn.com/abstract=3782217 **2023** - [4529715-023](https://wulfkaal.github.io/claims/4529715-023) [failure/argued] *(failure mode)* -- Blockchains cannot access off-chain data, and resolving this by using centralized oracles nullifies the advantages of decentralized systems while creating major security risks such as bribing and intimidation. > There is something known as the oracle problem, which is the fact that blockchains themselves can't access off-chain data. Using centralized oracles nullifies the advantages of decentralized systems, and are major security risks (such as bribing, intimidation, etc.) Wulf A. Kaal, Josh Bykowski, Decentralized Autonomous Organizations (DAO) – A Market Meta Analysis (2023). SSRN: https://ssrn.com/abstract=4529715 - [4529715-035](https://wulfkaal.github.io/claims/4529715-035) [failure/evidenced] *(failure mode)* -- Chainlink's white-list response to the 2020 gas fee attack was only a temporary fix: had the attack impacted 50 percent of Chainlink node operators, the price feed would not have updated until enough nodes returned. > Temporary solution known as "white-list", but if the attack had impacted 50% of Chainlink node operators, that feed wouldn't have updated until enough came back up and nodes would not be able to feed information. Wulf A. Kaal, Josh Bykowski, Decentralized Autonomous Organizations (DAO) – A Market Meta Analysis (2023). SSRN: https://ssrn.com/abstract=4529715 **2025** - [5554218-006](https://wulfkaal.github.io/claims/5554218-006) [failure/argued] *(failure mode)* -- Physical goods cannot be fully governed by code, so contracts requiring tangible performance need external mechanisms to verify compliance, and smart contracts may therefore fail to satisfy the consideration requirement in such contexts. > Unlike digital assets, physical goods cannot be fully governed by code, requiring external mechanisms to verify compliance with contractual terms. This limitation suggests that smart contracts may struggle to fulfill the consideration requirement in contexts requiring tangible performance, Furrer Andreas, Wulf A. Kaal, Universal Digital Law Codex (UDLC) Building the Legal Infrastructure for the Digital Era (2025). SSRN: https://ssrn.com/abstract=5554218 - [5554218-018](https://wulfkaal.github.io/claims/5554218-018) [condition/argued] *(failure mode)* -- Escrow based enforcement is effective for automation only if it is supported by reliable oracles and robust governance, without which the mechanism is open to manipulation. > Escrow mechanisms, while effective for automation, require reliable oracles and robust governance to prevent manipulation, as emphasized by Zhao and Chen. Furrer Andreas, Wulf A. Kaal, Universal Digital Law Codex (UDLC) Building the Legal Infrastructure for the Digital Era (2025). SSRN: https://ssrn.com/abstract=5554218 ## 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/oracles.md | sha256sum **Canonical form.** This markdown file is the canonical hashed representation of this entity node. Its sha256 is the content hash.