Scams

The Unenforced Code: Why DAOs Must Learn from Congress's AI Oversight Failure

HasuBear

The House of Representatives quietly adopted a set of AI usage rules last year. They were elegant, rational, and utterly unenforced. No compliance officer, no audit trail, no penalty for a staffer who feeds a constituent's private data into a GPT-4 wrapper. By design, each office is left to police itself. The result? A system where the rules exist in spirit but vanish in practice — exactly the kind of governance failure that blockchain was supposed to fix.

This isn't a story about Washington. It's a story about every decentralized autonomous organization that has ever voted on a smart contract upgrade without a formal verification mandate. We in the crypto space love to mock centralized institutions for their bureaucratic inertia, but we are repeating the same mistake with AI governance. The protocol is cold, but the evangelist is warm — and sometimes the warmth creates blind spots.

Context: The Decentralization of Oversight

Let me pull back the chain. The House's AI rules are not a law; they are a non-binding guidance document. They say: "Don't use AI to generate official statements without human review. Don't upload non-public information. Do disclose when AI is used." But there is no enforcement mechanism. The Speaker's office has no technical means to audit the thousands of AI tools being used across 435 offices. Each office is a sovereign entity, operating its own servers, its own licenses, its own ethical thresholds.

Sound familiar? This is the exact architecture of a DAO. Every DAO member is a sovereign participant, responsible for their own actions. The DAO's code is law — but only if someone enforces it. In practice, multisigs, proposal systems, and token votes are often unenforced because the cost of policing every action is infinite. The House's AI problem is our AI problem, just with a different ledger.

Core: The Technical Debt of Self-Policing

I spent the summer of 2024 auditing a governance proposal for a DAO that was considering integrating an AI agent to automate treasury rebalancing. The proposal was beautifully written, full of buzzwords like "agentic autonomy" and "adaptive liquidity." But when I looked at the underlying code, I found a fatal flaw: the AI agent had no verifiable identity. It was a smart contract that called a private API, returning a decision that no one could audit. The proposal passed because the community trusted the proposer — not the code.

This is the unenforced code. The DAO had rules: the AI must not trade more than 5% of the treasury per day, it must not interact with unverified protocols, it must post a report every 24 hours. But there was no on-chain mechanism to enforce those rules. The rules were written in a Google Doc, not in Solidity. They were the legislative equivalent of the House's AI guidance — well-intentioned, unenforced, and eventually ignored.

Based on my audit experience, this pattern is epidemic. I've seen proposals that require "human-in-the-loop approval" for every transaction, but the human is a single address with no timeout. I've seen rules that mandate "weekly risk assessments" that are never automated. The blockchain community is obsessed with code as law, but we forget that law without enforcement is just a suggestion. The House's failure is not that they wrote bad rules — it's that they wrote unenforceable rules. And we are doing the same.

Let me give you a concrete example from a recent project I consulted for. A DAO called "Synthetic Trust" deployed an AI oracle that ingested news sentiment to adjust interest rates on a lending pool. The governance document said: "The AI model must be tested on historical data before deployment." But the test was a single Python script run on a local machine, with no on-chain proof. When the model was deployed, it misread a tweet and caused a cascading liquidation. The DAO's emergency multisig had to intervene, but by then the damage was done. The rule existed, but the enforcement was missing.

This is the core insight: the reliance on self-policing in AI governance, whether in Congress or in a DAO, creates a systemic risk that scales with the speed of the technology. AI moves fast. Human oversight is slow. If the rules are not codified into the execution layer — if they remain in a PDF or a forum post — they will be broken before anyone notices.

Contrarian: The Myth of Decentralized Behavioural Enforcement

Here is the counter-intuitive angle: many in crypto believe that self-policing is a feature, not a bug. They argue that the market will punish bad behavior, that reputation systems will replace enforcement, that the community will fork away from a broken DAO. This is the same logic that the House uses: "Each office will do the right thing because they are accountable to their constituents."

But this is a dangerous myth. The market punishes too late. By the time a DAO's reputation is damaged, the exploit has already happened. Forks are costly and rare. And constituents? They rarely have the technical expertise to audit AI usage. The House's AI rules are unenforced because the voters cannot see what the AI is doing. In a DAO, the same opacity exists: how many token holders actually read the smart contract code before voting? Very few.

I recall a discussion in the Ethereum Frontier days, when we argued about the need for a formal verification framework for ERC-20 tokens. The community said, "Let the market decide." A year later, millions of dollars were lost to reentrancy attacks. The market didn't decide — it just lost. The same is happening with AI. Self-policing is not a governance strategy; it's a gamble. The House might survive because its scale is smaller than a DAO's, but a protocol with billions in TVL cannot afford to rely on individual offices policing themselves.

Takeaway: Code as Law, But Law as Code

The lesson is not that we should abandon self-policing. It is that we must encode the enforcement into the protocol itself. The House needs a cryptographic audit trail for every AI query. The DAO needs an on-chain registry of AI agents with verifiable credentials. The rules must be executable, not aspirational.

I am currently working on a pilot program that links AI agents to decentralized identity protocols. The goal is to create a verifiable attestation for every decision an AI makes. If the rule says "the AI must not execute a trade without a human signature," the smart contract refuses to execute unless the signature is present. This is not a new idea — it's the same principle as a multisig wallet. But we resist applying it to AI because we think AI is too fast for on-chain governance. That's precisely why we need it.

Chasing the frontier where code meets belief, I see a future where every legislative rule and every DAO rule is enforced by the same immutable ledger. The House's failure is a gift to the crypto community: a warning that unenforced rules are not rules. They are just suggestions. And in the silence of the chain, we hear the future — a future where code does not just express intent, but guarantees it.

Curiosity is the only leverage in DeFi Summer. But leverage without control is just risk. The protocol is cold; the evangelist is warm. But the warmth of good intentions cannot replace the cold certainty of enforced code. Let's build the enforcement layer before the next AI agent eats the treasury.