Fix and Maintain the DAO's Transparency Infrastructure

by 0x7bbea9c18cd0541acab8c19da2b11d0c03faef1c (MetaBeast)

Linked Pre-Proposal

The DAO's Transparency Log is Broken. 18 Months Missing Data. Should We Fix It?

Summary

Establish a named owner, a published maintenance standard, and a clear path for any community member to find the DAO's transparency information — so that the infrastructure the DAO built to serve the community actually serves the community.

Abstract

The Decentraland DAO launched a transparency system in 2022 to give the community visibility into how DAO funds are used. The DAO had a Governance Core Unit that maintained this infrastructure until January 2025, when the Grants Program ended and there was no longer a way to sustain its operations. Since then the system has operated without a formally named maintainer and without a published standard for how it should be kept current.

In 2024 a gap developed in the transaction display. Steps were taken in March 2026 to address it, and the system is now operational. This proposal moves forward from that experience by putting the structural pieces in place to prevent a similar situation from occurring again.

Those pieces are straightforward: a named owner for each part of the transparency infrastructure, a basic maintenance standard with clear expectations, a single accessible place for community members to find all DAO transparency information, and a clear distinction between DAO governance records and the operational reporting produced by Regenesis Labs. The specific parties responsible will be formally identified in the binding Governance Proposal that follows if this Draft Proposal passes.

Motivation

The DAO's transparency infrastructure currently has no formally named maintainer and no published standard for how it should be maintained. The community built this infrastructure because transparency matters. Keeping it working should not depend on someone noticing a problem and raising it publicly

The following gaps exist today

• No named, accountable owner for the DAO's main transaction and treasury records
• No published standard for how often data must be updated or what the process is when something breaks
• The DAO website does not link to either the DAO's own transparency records or the Regenesis Labs quarterly operational reports
• Multiple broken links exist on the DAO website
• The DAO website does not reference or link to Regenesis Labs, the entity operating the platform on the DAO's behalf
• Two dashboards exist with no public explanation of which covers what and who maintains each
• The difference between DAO governance transparency records and Regenesis Labs quarterly contractor reports has never been formally defined

These are not difficult problems to solve. They require clarity, ownership, and follow-through — none of which currently exist in a documented form.

Specification

If this proposal passes and advances to a binding Governance Proposal, the following requirements will be put into effect.

1. Named Ownership

Every part of the DAO's transparency infrastructure must have a formally named, publicly documented responsible party that can be identifiable by wallet address and/or community handle. This includes the main transaction record, the treasury dashboard, the DAO website, and the quarterly reporting infrastructure. Why: Without a named owner, no one is accountable when something breaks. This is the single most important structural change this proposal makes.

2. A Single Place to Find DAO Transparency Information

One publicly accessible page must exist linking to all DAO transparency resources, reachable in no more than two clicks from the main governance portal. It must include the transaction record, quarterly reports, the operational dashboard, a plain-language explanation of what each is and who maintains it, and a contact point for questions or concerns.

3. Basic Maintenance Standards

The following minimum standards apply:

• Transaction data updates automatically every 24 hours. A window of up to 72 hours is allowed to account for any technical issues that may arise. Anything beyond that is a reportable issue.
• Dashboard: reviewed and verified monthly.
• Broken links: resolved within 14 days of being identified.
• Critical or availability issues: addressed immediately. Any other failure affecting data visibility: publicly acknowledged within 7 days, with cause and estimated resolution timeline posted.

4. Clear Distinction Between Two Types of Transparency

A plain-language public document must define and distinguish between:

• DAO governance transparency records: the on-chain record of treasury movements, governance activity, and fund disbursements. This is the primary accountability record for how the DAO's assets and authority are used.
• Regenesis Labs contractor reporting: quarterly financial and operational reports covering how Regenesis Labs is executing against its approved budget. These reports cover Regenesis Labs operations, not the DAO itself.

Both must be maintained, both must be linked from the DAO website, and neither replaces the other.

5. Accountability Requirements

Named owners are expected to:

• Post a brief monthly update confirming their system is operational, or documenting any issues and their current status. For Regenesis Labs, this takes the form of a fixed section in their existing monthly updates covering: (a) known issues currently being worked on, and (b) issues resolved since the last update.
• Publicly document any change in scope, tools, or approach within 30 days of the change occurring.
• Follow an explicit public handoff process if ownership transfers — both outgoing and incoming parties must acknowledge it publicly. Responsibility cannot move silently or simply stop being carried.
• Publicly acknowledge any breach of maintenance standards within 7 days, with a plain explanation and a revised timeline.

If a named owner can no longer fulfill their role, they must raise this publicly. The DAO Council is responsible for ensuring a successor is identified. No part of this infrastructure becomes ownerless by default.

Why: The goal is not punishment, it is ensuring the community always knows who is responsible, what is working, and what is being fixed. Silent exits and assumed handoffs are how things quietly stop being maintained.

Conclusion

The DAO built a transparency system because the community deserves to know how its resources are being used. For over a year that system operated without a named maintainer, without published standards, and without a clear way for the average community member to find the information it was built to provide. That is not a technology failure. It is a structural one.

This proposal fixes the structure. Named ownership means someone is always accountable. A maintenance standard including monthly dashboard verification and 14-day resolution for broken links gives the community a clear baseline to hold owners to. A single accessible entry point means transparency is no longer something you have to already know how to find. And a formal distinction between DAO governance records and Regenesis Labs contractor reporting means the community can finally read both with confidence about what each one is and who is responsible for it. Without that clarity, confusion about the DAO's financial picture is inevitable.

Passing this proposal does not complete the work. It authorizes it. The binding Governance Proposal that follows will formally name the responsible parties for each requirement and put these standards into effect. The goal is a transparency infrastructure that works quietly in the background, requires no community pressure to maintain, and is there when anyone needs it.

For:

Vote YES to establish named ownership, a basic maintenance standard, and a single accessible entry point for DAO transparency information.

Against:

Vote NO if you believe the current transparency infrastructure is adequate without formal ownership or maintenance standards.

This proposal is summarized due to technical limitations. To view it complete and vote on it, visit the DCL DAO Governance dApp