Thanks to @SinfulMeatStick and @toxicwaifu for hosting last Monday Beyond the NFT session with the DAO Council candidates. I didn’t join live; it was 2:00 AM where I am, but I watched the recording yesterday. While listening, I heard some questions and concerns that were better directed to current Council members or to me, as the Regenesis Labs Executive Director, rather than to the candidates. Combined with messages that current DAO Committee member @rizk posted on the DAO Discord, this made me want to write this note for clarity.
These are some of the concerns I heard. Please let me know in the comments below if I should address anything else.
Concern 1 — Transfers from the Regenesis Labs Treasury to the Regenesis Labs Operational Wallet
Why it happened: Regenesis Labs is an operating organization. Starting in September, we will have ~10 full/part-time contributors, we also have two project-based contributors, vendors, equipment, and monthly bills. Pulling funds from a co-managed treasury multisig for every invoice is inefficient and increases operational risk. Council members are usually available, but it’s not their job to be on call to sign transactions whenever I request it. That’s why, after the funding transfer from the DAO Treasury, a portion of the funds was transferred to the Operational Wallet. It’s worth mentioning that this happened in June. I’m not sure why this is being raised now as a concern, but I’m happy to clarify.
The Operational Wallet has existed since the original 18-month operating budget proposal (see the operational diagram I presented at the Town Hall where I walked through the operating budget).
The first treasury → operational transfer occurred in June, when we began operations. Two transfers were made: one in stablecoins to cover the first month of operations (before the large MANA transfer by the DAO Committee), and a second one in MANA.
The transfer was requested by me with Council approval and was signed by two Council members and me.
Regenesis Labs is solely responsible for the operational funds, and we can decide what we do to maximize them. Having a portion of the funds under our control allowed us to buy MANA at the best price possible over the last three months and deposit funds in low-risk stablecoin yield generation protocols. We will continue to do this because every MANA we exchange over our break-even price of 0.26 and every % of yield we generate from our budget is less MANA we will have to use from our budget.
Everything we did has been on-chain and has been reflected in our monthly updates. If you missed it, we’ll work to make it easier to see.
Concern 2 — Lack of transparency in spending
We’re executing what we committed to:
All vendor payments are invoiced and are paid on-chain via Request.finance, and are visible from the multisig in real time.
We’ll publish quarterly reports with a project narrative and spend breakdown (monthly financial reporting would require a dedicated reporting team we don’t have, and we don’t think that’s a priority right now). The first one is due in October, covering June–September (we aligned quarters to the calendar year from the start).
We’ve been publishing timely monthly updates at the beginning of each month. See June and July.
As we said when we proposed this structure, transparency should be built into how we operate. We are sharing an in-progress public dashboard now (originally planned for quarter-end) to centralize what matters—initiatives, progress, and spend.
If something is unclear, please comment with suggestions, and we’ll iterate.
Concern 3 — “One person has unilateral access to DAO funds”
Regenesis has operational autonomy only over the funds allocated to Regenesis (not the DAO treasury). The DAO Council provides oversight—think board-level accountability for spending and results against the approved plan, rather than day-to-day approvals.
A comment was made about me holding two keys of the Operational Wallet. Point taken. If something happens to me, the funds on that multisig would be locked. We have added a temporary trusted recovery key from a Regenesis Labs team member. I’ll ask the Council if a member is willing to serve as a recovery mechanism; if not, through this post, I’m inviting a DAO Committee member who is willing to complete KYC to fill that role.
Legal accountability: Regenesis operates under a Cayman Islands Foundation structure. I am personally accountable for the lawful use of Regenesis funds. As opposed to the DAO Treasury, which is not protected by any legal wrapper, the Regenesis Labs Treasury is. The Foundation bylaws are explicit about me not having any protection if I perform “actual fraud, wilful default, or Gross Negligence.” In addition, I must act in good faith in the Foundation’s best interests. Also, it prohibits distributing the Foundation’s income or property to members other than authorised remuneration for services.
Concern 4 — Double Spending between Decentraland Foundation and DCL Regenesis Labs
I’ve heard some concerns about duplicate efforts between the two entities. This is what I’m doing on my side to avoid them:
Active coordination: I sync weekly with Yemel (Executive Director, Foundation) and Kim (Head of Marketing & Partnerships, Foundation), and regularly with Nico R. (Head of Product, Foundation). Agus (DAO Council member) also advises and attends Foundation board meetings.
Unified ecosystem view: My goal is that by 2026, we operate against a shared ecosystem roadmap, with a clear division of initiatives between the Foundation and Regenesis Labs. We will soon announce the first joint initiative between the two entities.
Knowledge sharing: Hiring Gonzalo Pombo (ex-Foundation SDK team) as Regenesis Director of Engineering shows our commitment to continuity and knowledge transfer.
Independence with alignment: Regenesis must remain an independent entity, learn from what works at the Foundation, and avoid repeating mistakes. My commitment as ED is to minimize overlap, and I expect the same commitment from the Foundation.
Concern 5 — DAO Treasury management strategy
First, it’s important to note that this is the DAO Council’s responsibility. They are the ones to define and communicate it. But because Regenesis is mentioned in their post, I would like to clarify:
- We don’t set the treasury strategy. That mandate lies with the DAO Council.
- Our role is to manage the relationship with the third-party provider that implements the strategy, only because we’re the team with a legal entity that can sign the agreement.
- We will not move DAO treasury funds and will not have direct access to them. Our job is to help the Council and the selected provider implement a safer, more trust-minimized setup than what we have today.
If you want more clarity, have questions or comments, please use the spaces where discussion compounds and is easy to track:
Town Halls (bring questions; I’ll be there)
Forum Topics (for async discussion and permanent record)
Or book me directly over Calendly
Thanks again for your input!
GinoCT
Executive Director, DCL Regenesis Labs