The Wyoming wrapper architecture — what changes when the LLC gets sued

The 3-layer architecture

Why three layers?

Each layer answers a different question that comes up the day a regulator, opposing counsel, or insurance adjuster asks "show me the chain."

A DAO with just the smart contracts gets sunk on question 1. A DAO with just the LLC filing gets sunk on question 3. The wrapper bundles all three so every question has an artifact.

Layer 1 — what Wyoming actually buys you

Wyoming Statute §17-31 (Decentralized Autonomous Organization Supplement) is, as of 2026, the most-tested DAO LLC statute in the United States. The relevant clauses for our purposes:

• §17-31-104 — A DAO LLC has all the powers of a regular Wyoming LLC, including the power to sue, hold property, and pay taxes
• §17-31-106 — Smart contracts may be designated as part of the operating agreement, with on-chain governance recognized as legally binding
• §17-31-110 — Members of a DAO LLC are not personally liable for the DAO's debts solely by reason of being members
• §17-31-114 — Annual report filing required; failure to file results in administrative dissolution after 60 days

What this means in practice: the LLC has its own bank account, its own taxpayer ID, can sign contracts in its own name, and any judgment against it does not pierce through to individual members. The on-chain governance the DAO already uses is recognized as binding. Token-holders aren't suddenly partners in a general partnership with unlimited liability.

What it doesn't buy you: a free pass on securities law, federal AML/KYC, or MiCA Title V. The wrapper is necessary but not sufficient. That's why Layer 3 — the compliance hooks — is in the bundle.

Layer 2 — the EIN-to-passport anchor

The ERC-8004 passport is the bridge between the LLC's off-chain identity (EIN, registered agent address, operator key) and its on-chain identity (the wallet that signs the DAO's governance transactions). The anchor looks like this:

# Conceptual — issued during Q3 2026 onboarding
passport = {
    "agent_id":       "did:erc8004:0x<DAO-governance-wallet>",
    "operator_id":    sha256(EIN + Wyoming-filing-number).hexdigest(),
    "activation_proof": {
        "kind": 30012,
        "signer": "<operator-key>",  # held by the LLC's responsible party
        "issued_at": "2026-Q3-XX",
        "hmac_sig": "<...>",
    },
    "scope": ["governance", "treasury", "agent_spawn"],
    "revocation_url": "https://craigmbrown.com/api/erc8004/revoke",
}

Two things to notice:

1. operator_id is the EIN hash. Not the EIN itself — the SHA-256 of the EIN concatenated with the Wyoming filing number. The regulator who needs to verify it can reconstruct the hash from public Wyoming filings; the public can't reverse it.
2. activation_proof is signed by an operator key. The key is held by the LLC's "responsible party" (the human Wyoming requires as the contact for any DAO LLC). When the LLC files its annual report, the operator key signs a re-anchor proof — tying the LLC's continued existence to its on-chain identity.

Layer 3 — every agent action signed

The third layer is where the DAO's day-to-day operations live. Every agent the DAO spawns — a treasury agent that swaps stablecoins, a grant agent that pays out RFPs, a moderation agent that votes on governance — produces a ProofOfDelegation (kind 30014) at spawn time and a Compliance Hook proof at action time.

# Treasury agent spawn — happens inside the DAO's governance flow
parent_session = governance_proposal_id
delegation = client.emit_delegation_proof(
    parent_session_id=parent_session,
    delegatee_id="treasury_agent_2026Q3",
    scope=["swap", "transfer"],
    expires_at="2026-09-30T23:59:59Z",
    signer=operator_key,  # held by LLC's responsible party
)

# Treasury agent action — happens many times
result = client.check_address(
    address=destination_wallet,
    preset=presets.kyc_ofac_sanctions,
)
if not result.allowed:
    raise PermissionError(f"Blocked: {result.reason}")
# Execute the swap; both delegation + compliance proofs in audit log

The audit log retains both proofs for 365 days (legal opinion attach). If a regulator wants the chain from the DAO's governance vote → spawn → action, every step has a signature, and the chain is unbroken.

What changes when the LLC gets sued — three scenarios

The revocation path — how to kill an agent fast

The wrapper's revocation guarantee is what makes the agency chain useful. If a treasury agent goes rogue (or its operator key gets compromised), the LLC's responsible party can revoke the passport in a single transaction:

POST /api/erc8004/revoke
Authorization: Bearer <operator-signed-token>
Content-Type: application/json

{
  "agent_id": "did:erc8004:0x...treasury_agent_2026Q3...",
  "revocation_reason": "compromised-key-2026-08-15",
  "effective_at": "2026-08-15T14:00:00Z"
}

Once the revocation proof (kind 30013) is in ProofDB, every downstream system that verifies the chain sees the revocation and refuses further actions. The market-maker who was about to fill an agent-initiated trade pulls the trade; the on-chain governance contract that was about to honor a vote from the revoked agent rejects it.

This is the part Wyoming's statute alone doesn't give you. §17-31 lets you sue the LLC; the ERC-8004 + Compliance Hook layer lets you stop the agent from causing more damage in the meantime.

Pricing recap

A DAO LLC without the on-chain anchor is paperwork. An on-chain governance system without the LLC is sue-able but undefendable. The wrapper is what makes both sides whole.

Related

• Post 1 of 4: The Legal Agent Stack manifesto
• Post 2 of 4: Compliance Hook Code-Walk
• Post 3 of 4: MASSAT × MiCA worked example
• Wyo. Stat. §17-31 — Decentralized Autonomous Organization Supplement
• UETA / E-SIGN §202 — Electronic agents (agency)
• Wedge 3 page — pricing + waitlist form
• Reliability Manifesto — the 4 accountability rules backing the chain

Post 4 of 4 — series complete · Operated by Craig M. Brown · Back to blog