Echoes of "Smart Contracts" across the library

Every passage here circles the same anxious gap: a smart contract executes with certainty but cannot accommodate ambiguity, so the system reinvents the human intermediary under a new name — "oracle." De Filippi and Wright document this with visible discomfort: the whole point was to eliminate trusted third parties, yet the moment a contract touches the physical world (temperature, interest rates, whether someone actually delivered the goods), it needs a person or program to tell it what happened. This is Ian Macneil's relational contracting problem from 1980 dressed in Solidity syntax. Macneil argued that real contracts aren't discrete moments of agreement but ongoing negotiations shaped by trust accumulated over time — exactly the thing a trustless system cannot encode. The oracle isn't a patch. It's an admission that the gap between code-as-law and law-as-practiced is load-bearing, and always was.