20-Question Expert Quiz — Class 3.2: Nick Szabo & Smart Contracts: Hardcoding Consideration

1. What is the central 'detective story' unpacked in Class 3.2 ('Nick Szabo & Smart Contracts: Hardcoding Consideration')?

A) How the centuries-old contract law doctrine of 'consideration' (quid pro quo) solved the decentralized network dilemma and made modern blockchains possible. B) How to litigate a maritime insurance claim. C) How to design a corporate logo.

2. In Section 2 ('The Smart Contract Problem: The Decentralized Dilemma'), why wouldn't a distributed network of peer computers simply run your contract code for free?

A) Without a built-in economic incentive, independent peer nodes have no reason to burn electricity and CPU cycles to verify and execute stranger's transactions. B) Because peer-to-peer networks cannot transmit text. C) Because the internet shuts down at night.

3. How did legal scholar and computer scientist Nick Szabo solve this decentralized execution dilemma?

A) By translating the legal requirement of 'consideration' (the quid pro quo exchange of value) directly into protocol-level digital payment ('gas fees') for network validators. B) By asking governments to subsidize all servers. C) By making all smart contracts non-binding.

4. In the step-by-step blockchain execution flow in Class 3.2, why do network validators receive 'gas fees'?

A) As hardcoded digitized consideration compensating them for expending real computational energy to validate and record the contract state transition. B) To pay for gasoline for delivery trucks. C) As a charitable donation with no obligation.

5. Who envisioned the 'Ricardian Contract' in 1996 (highlighted in Section 5 of Class 3.2), and what does it do?

A) Ian Grigg; it formats a legal agreement so that it is simultaneously machine-readable software and text-readable prose for human lawyers. B) David Ricardo; it calculates agricultural tariffs. C) Charles Dickens; it serializes novels.

🎓 Expert Mastery Questions (Questions 6–20)

6. In Section 1 of Class 3.2 ('The Calculus of Law'), how does a traditional paper contract after signing contrast with a software runtime?

A) On paper, the ink dries and the document sits dormant in a filing cabinet; in a runtime, you hit play and the performance executes autonomously start to finish. B) Paper contracts execute themselves automatically. C) Software runtimes require wet-ink signatures on every block.

7. What syntax shift does Class 3.2 remind lawyers to make when reading code?

A) Training your brain to read variable assignments from right to left instead of natural English left to right. B) Reading only the odd-numbered lines of a contract. C) Ignoring all punctuation marks.

8. What does the Latin legal phrase 'quid pro quo' mean in the doctrine of consideration?

A) 'Something for something' — the mutual bargained-for exchange of value required to form an enforceable contract. B) 'Let the buyer beware.' C) 'After the fact.'

9. In traditional contract law, what happens to a promise that lacks consideration?

A) It is generally treated as a gratuitous, unenforceable gift rather than a binding contractual obligation. B) It automatically becomes a federal statute. C) It is enforced with triple damages.

10. How does hardcoding consideration into peer-to-peer nodes (like the Ethereum Virtual Machine) transform the architecture of the internet?

A) It creates self-sustaining market dynamics inside the network, allowing equal peer-to-peer nodes to execute smart contracts trustlessly without a central corporate intermediary. B) It requires every user to ask permission from a central bank. C) It restricts the network to a single mainframe computer.

11. What happens on an EVM blockchain if a transaction is submitted without sufficient gas (digitized consideration)?

A) Validators refuse to execute the state transition and the transaction reverts—mirroring how a contract without consideration fails to bind performance. B) The network executes it for free out of generosity. C) The blockchain deletes the sender's wallet.

12. In Section 5 ('The Future of Automated Law'), how does Class 3.2 compare 19th-century analog law, current mechanized law, and future automated law?

A) 19th-century analog law was a manual horse-and-buggy; mechanized law is a high-speed car; automated law is a self-driving Waymo that executes without human steering. B) Bicycles, trains, and submarines. C) Carrier pigeons, telegraphs, and radios.

13. How does the 1980s Unix philosophy protect automated legal tools from technological obsolescence in Class 3.2?

A) By writing modular programs that do one thing perfectly and communicate strictly via universal plain-text streams. B) By locking all legal data inside proprietary binary databases. C) By requiring new hardware every six months.

14. Why is Ian Grigg's Ricardian Contract described as 'incredibly precise' in Class 3.2?

A) Because it binds human-readable legal intent and machine-executable parameters into a single cryptographically verifiable document. B) Because it eliminates all human language. C) Because it can only be read by a single proprietary app.

15. What two parallel developments occur in the legal workforce as contracts move from paper to code in Class 3.2?

A) Dedicated Legal Engineers build the underlying runtime infrastructure, while traditional lawyers naturally adopt programming syntax to draft and audit agreements. B) All lawyers become courtroom sketch artists. C) Software developers stop using version control.

16. How did Nick Szabo's 1990s smart contract work relate chronologically to the invention of Bitcoin (2009)?

A) Szabo architected the smart contract paradigm and hardcoded consideration in the 1990s—more than a decade before Bitcoin launched. B) Szabo invented smart contracts in 2020 after Ethereum. C) Smart contracts were invented after NFTs.

17. Why does Class 3.2 say 'the code is basically just a brand-new medium for the contract'?

A) Because the underlying legal principles—offer, acceptance, consideration, and performance—remain the same, but the medium shifts from passive paper to an active runtime. B) Because code abolishes the concept of mutual agreement. C) Because code is only used for graphic design.

18. In the composer metaphor reviewed in Class 3.2, when does the legal engineer do their work?

A) Before hitting 'play'—designing the system, verses, conditions, and looping choruses ex-ante so runtime execution is seamless. B) Only after a breach of contract lawsuit is filed. C) Only during appellate oral arguments.

19. How do Charles Goldfarb (Class 3.1) and Nick Szabo (Class 3.2) together prove that legal engineering built our digital world?

A) Goldfarb mechanized legal document structure to create the Web's markup (GML/HTML), and Szabo mechanized legal consideration to create smart contracts and blockchain economics. B) Both worked at the same law firm in 2015. C) Neither studied law or contracts.

20. What closing question does Class 3.2 leave with legal practitioners?

A) Will you master the syntax of automated legal runtimes, or will you be left trying to draft paper for a horse and buggy? B) How much does a horse and buggy cost today? C) Which filing cabinet has the strongest lock?

Keccak-256 Attestation Payload Hash:

View Public Student Attestation Ledger ➔ ⬅ Back to Class 3.2 Lesson

20-Question Expert Quiz — Class 3.2: Nick Szabo & Smart Contracts: Hardcoding Consideration