The debate has been structured as a custody problem — should the treasury transfer to the Foundation outright, stay onchain with the DAO, or move in tranches against milestones? That framing settles in advance which alternatives are visible. It has hidden a whole class of them. Custody determines who holds the assets. It does not determine who sees what happens to them. These are separable questions. The first has consumed this entire deliberation. The second has not been asked at all. This proposal asks the second question. And the answer it proposes applies regardless of how the first question is resolved — which means it can be adopted now, without waiting for the custody debate to settle. **Where Accountability Actually Breaks Down** The temp check offers three accountability mechanisms: annual audited financials, quarterly grant deployment reports, and a tokenholder removal process that requires a mission violation allegation, documentary evidence, a board response window, and a 30-day cooling-off period. Each of these mechanisms shares one structural property. They are all retrospective. They describe decisions that have already been executed, funds that have already moved, and structural changes that have already taken effect. This is not a criticism of the people who designed them. Retrospective accountability is the only kind available to organizations whose operations run behind closed systems. You report what happened because you cannot show it happening. ENS is not that organization. Its treasury exists on a public blockchain. Its governance contracts are publicly readable. Every transaction its multisig executes is permanently recorded the moment it occurs. ENS already has the raw infrastructure for real-time accountability. What it lacks is the layer that turns that raw infrastructure into a verification standard. The missing layer is not a better report. It is a system that makes self-reporting unnecessary. **The Structural Argument** In any principal-agent relationship, the agent controls the information the principal receives. The Foundation writes the reports. The Foundation frames the options. The Foundation decides which questions reach a vote. A DAO holding formal authority without independent verification capacity has kept the right to ratify while surrendering the capacity to choose. This holds regardless of the board's intentions. A single organized body producing its own accountability record will always — not from bad faith but from structural necessity — present information in ways that support its own continuation. This is not a character claim. It is an organizational property. The solution is not a better reporting standard. The solution is infrastructure that removes the Foundation's monopoly on its own accountability record. If every payment is verified against a DAO-controlled registry before it executes, if every structural decision is checked against a required process before it takes effect, if every action generates a permanent immutable public record automatically — the Foundation does not produce its own accountability record. The blockchain does. That is the upgrade this proposal introduces. **Two Tracks — Money and Decisions** The accountability gap runs across two surfaces that existing proposals treat separately or ignore entirely. The financial surface is where most attention has focused — who receives Foundation payments, under what authority, against what budget. The governance surface has been almost entirely overlooked — who changes the Foundation's signing rules, expands its mandate, adds a director, switches a key vendor, or amends its governing documents between formal votes. The most consequential risks are not always financial. A Foundation that quietly reduces its multisig threshold from five of eight signers to three of eight has shifted operational control without spending a dollar. A Foundation that expands its spending categories unilaterally has changed what it is authorized to do without a vote. A Foundation that switches its auditor to a connected party before a conflict of interest policy exists has created exactly the capture risk this deliberation is designed to prevent. Quarterly reports describe these decisions after they happen. Annual audits summarize them later still. This proposal covers both surfaces with the same verification requirement — pre-execution, automatic, onchain — so the community sees every consequential action before it becomes irreversible. **Track One — Treasury** The Tag. Every Foundation payment begins inside a Gnosis Safe multisig. Before a signer can propose any transaction, they select a spending category — Grant, Legal, Payroll, Treasury, Infrastructure, or Emergency. That selection is not a label. It is a commitment that triggers an automatic verification against a DAO-controlled registry the moment it is made. The Registry. The registry is an onchain contract controlled by the DAO — not the Foundation. It maps every approved spending category to its pre-verified recipient addresses. Before any payment proceeds the system checks one question automatically: is the recipient address of this payment registered under the declared spending category? If yes — the payment queues, an EAS attestation is created automatically. If no — the payment is blocked immediately, visible publicly before a single dollar moves. Who Controls The Registry. The DAO controls the registry at root level. A small committee manages day to day registrations under DAO mandate. The Foundation cannot register its own addresses. Only the committee can, under DAO authority. The committee model is not untested in ENS — SPP3 processed 26 applications on schedule with a published rubric, fixed timelines, and structured interviews. Tier Based Visibility. Under $5,000 executes normally, visible on the public dashboard immediately. $5,000 to $50,000 opens a 48 hour public visibility window before execution. Over $50,000 opens a 14 day public window. Routine payments stay fast. Large or unusual payments get proportional scrutiny. **Track Two — Governance Decisions** This is the track no other proposal in this deliberation addresses. The removal process the temp check establishes is deliberately slow. That is reasonable for a legitimate removal. It is not a real-time warning system. The governance track is the early warning system the removal process assumes but does not provide. Every structural Foundation decision gets tagged before it executes: Configuration Change, Board Change, Mandate Expansion, Registry Update, Vendor Change, Constitutional Amendment. Each governance action tag triggers an automatic check — was this action preceded by the required process? If yes, the action proceeds and a permanent record is created. If no, the action is flagged immediately, visible publicly before it takes effect. **The NFT Receipt — Accountability Cards** Every verified action — financial or governance — automatically generates a public NFT receipt. Not a collectible. A tamper-proof public record of what happened, who approved it, when it was verified, and a direct link to the underlying EAS attestation on Ethereum. The EAS attestation is the canonical record — permanent, immutable, queryable by any developer. The NFT receipt is the human-readable interface generated from that record. **The Public Dashboard** No login. No permission needed. One URL. Live Feed of every queued, pending, and executed Foundation action in real time. Budget View of spending per category versus approved envelope. Governance Timeline of every structural decision in chronological order. Sustainability Tracker of protocol revenue versus total spend, updated automatically. Anomaly Log of every flag the system raised. **What This Is Not** This does not replace anything proposed in the temp check or any amendment in this deliberation. Not the Foundation board. Not the Executive Director. Not the removal authority. Not the conflict of interest framework. Not the custody arrangements any proposal recommends. It sits underneath all of it. The Foundation keeps full operational independence. Routine payments under $5,000 flow without friction. It only creates friction for actions that were not properly declared. **The Trade-offs This Proposal Accepts** The registry committee introduces a new coordination layer. If poorly composed it could become a bottleneck. The SPP3 model answers this partially but not completely — a registry committee has different incentive structures than a grants committee and deserves its own scrutiny. The EAS attestation requirement places a procedural obligation on Foundation signers before every significant transaction — minimal, but a new step, and new steps have adoption costs. **What Would Change This Proposal's Mind** Show that the Foundation charter already requires pre-execution public disclosure of every structural decision with automatic onchain recording — and this layer becomes redundant. Show that the EAS attestation model introduces legal liability for Foundation signers that outweighs the transparency benefit — and the attestation mechanism needs redesign. Show that the registry committee introduces more coordination overhead than it removes in accountability value — and the design needs a different address verification model. The custody debate will resolve one way or another. The Foundation will receive some level of operational authority. This proposal does not contest that structure. It adds the one thing that structure currently lacks — continuous, automatic, onchain visibility into what the Foundation does with the authority it receives, across both financial and governance decisions, without requiring the Foundation to self-report. Whatever the DAO decides about custody — the community deserves to see what happens next. In real time. Automatically. Without waiting for a report.