A few items I’d like the Council to address:
June 2026 Update — Looking for the monthly report. Can someone confirm when it will be posted?
Community Questions Form — Fehz posted about a form for community questions earlier but I can no longer find it. When can we expect responses?
2030 Planning — The proposal didn’t pass but my understanding was the Council would move forward with something on post-2030 sustainability regardless. What is the current status and is there anything I can do to help?
POI Status — I have a POI that passed March 25, 2026 that has not been implemented. There is also one that passed January 13, 2026 — unclear if that one was ever enacted. Can someone confirm the status of both and provide a timeline?
Transparency Accountability — GinoCT has stated publicly and verbally that he takes responsibility for DAO transparency. I’ve raised specific accessibility issues on multiple occasions over several months and they remain unresolved. Does the Council have any mechanism to set deadlines or hold Regenesis Labs accountable on this, or does “I take responsibility” remain open-ended indefinitely?
— MetaBeast
1 Like
Found the link to the request for information from May 12, 2026
FORM . Once the current round of submissions is complete, a new round will be opened for further inquiries.
Please visit the specifications thread for a better understanding of the procedure and the form.
REM…
ginoct
July 7, 2026, 12:45pm
3
Hi @Existential14 , I’ve been personally taking care of most of the reports you’ve made when we talked and proactively fixing other things with the team:
main ← worktree-qa-docs-links
opened 01:02PM - 16 Jun 26 UTC
## Summary
Two related changes from a fresh-eyes QA pass on the governance dApp… :
1. **Fix broken documentation links.** `docs.decentraland.org` reorganized to a `/dao/dao/*` structure and the ADR repo moved `docs/` → `content/`, leaving several in-product help links returning 404 — including the "Grants Framework" link used on the grant-submission consent checkbox.
2. **Add a warning-only CI link-checker** so this class of rot is caught automatically going forward.
## Link fixes (10 links, 4 files)
- `src/constants/index.ts` — `DOCS_URL` → `/dao/dao/what-is-the-dao`
- `src/pages/transparency.tsx` — `ABOUT_DAO_URL` → `/dao/dao/how-does-the-dao-work`
- `src/components/Projects/Current/ProjectsBanner.tsx` — FAQ link → `/dao/dao/the-dao-fund`
- `src/intl/en.json` (7 links) — DAO-overview links repointed to their exact new pages; ADR-42 → `/content/...`
⚠️ **For a content owner to confirm:** the docs no longer have dedicated "Grants Framework" / "grant categories" pages — that content was consolidated into `/dao/dao/the-dao-fund`, so the grant-related links now point there. A working, relevant page beats a 404, but the DAO may want a richer canonical grants doc.
## Link checker
- `scripts/check-links.js` — no-dependency Node script. Scans product-owned source (`intl`, `constants`, `components`, `pages`, `hooks`, `utils`) for http(s) links and reports unreachable ones as GitHub Actions `::warning::` annotations. **Always exits 0 — never fails the build.** Skips `candidates.json` (delegate-maintained) and test/story fixtures; ignores API base-URLs that 404 at root.
- `.github/workflows/link-check.yaml` — runs on push/PR (Node 24).
- `npm run check-links` — local runs.
## Verification
- `en.json` validated as parseable JSON.
- Checker run: 42 product links checked, all fixed docs links return 200, script exits 0.
- Only remaining warning is a genuinely-down third-party catalyst (`peer.decentral.io`, HTTP 521) — out of scope, and exactly what the warning is meant to surface without blocking.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
main ← feat/disputed-wallets-warning
opened 03:07PM - 16 Jun 26 UTC
## Summary
Surfaces wallet status on the transparency page: warns that the form… er DAO Committee multisigs' funds are not under DAO control, and lets the new DAO Council Operational Multisig appear automatically.
Refs proposal [DAO Committee Deprecation & Replacement](https://decentraland.org/governance/proposal/?id=bb2b8234-42aa-4ca2-a049-3c7355d4caa4).
## ⚠️ Depends on the transparency pipeline PR — merge that first
**Requires:** Decentraland-DAO/transparency#121 (adds `status` + the Council multisig to `balances.json`).
This PR is **backward-compatible**: `status` is optional, so nothing changes until the pipeline publishes the updated `balances.json`. Merging this before #121 is safe but inert (no warnings/new wallet shown until the data carries `status`).
## Changes
- **`types/transparency.ts`** — optional `status` (`active` | `disputed`) on `TokenInWallet`; flows straight from `balances.json` (the client casts the response directly).
- **`TokensPerWalletPopup.tsx`** + CSS — disputed wallets get a ⚠ icon next to the name and a warning note:
> Funds withheld from the DAO. The former DAO Committee retains control of these wallets and has not returned the assets to the DAO. [Learn more →]
"Learn more" links to the deprecation proposal.
- **`constants`** — `COMMITTEE_DEPRECATION_PROPOSAL_ID`.
- **`en.json`** — warning copy.
## Product decisions baked in
- **Totals unchanged**: disputed funds remain in the per-token totals and are flagged in the popup (not excluded).
- **Prominence**: popup badge only (no page-level banner).
- The **new Council multisig** needs no UI work — it renders automatically once it's in the published balances data.
## Testing notes
Couldn't run `tsc`/tests locally (no `node_modules` in the worktree); CI will typecheck. Change is small and type-checked by inspection.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
main ← fix/exclude-internal-transfers-from-expenses
opened 04:56PM - 24 Jun 26 UTC
## Summary
Internal treasury movements between DAO wallets were being counted a… s **expenses** in the income/expenses section of the transparency page. As of today this inflated the "Other expenses" figure to **~\$1,638,962** — driven entirely by the **Aragon Agent** funding the newly tracked **Council Operational** (`0x184e…16d7`) and **Treasury Management** (`0x96e2…4407`) multisigs (added in #121). Moving funds from one DAO wallet to another is not spending.
## Root cause
`calcOtherExpensesUSD` in `src/export-api-v2.ts` queries every transfer **out of** a DAO treasury address and books it as an expense, excluding only the committee/council/curator **payout recipient** sets. It never excluded transfers **to other DAO wallets**, so wallet-to-wallet reallocations counted as real outflows.
(Note: `transactions.json` / `api.json` already handle this correctly — they tag a transfer `INTERNAL` when both ends are tracked wallets. Only the `api-v2.json` expense path was missing the check.)
## Change
- Import `Wallets` and build `DAO_WALLET_SET` from `Wallets.getAddresses()` — a single source of truth, so any wallet added to `entities/Wallets.ts` is automatically treated as internal.
- In `calcOtherExpensesUSD`, skip any transfer whose recipient is in `DAO_WALLET_SET`.
```ts
// Skip internal movements between DAO wallets (e.g. Aragon Agent funding a
// new multisig). These are not expenses, just treasury reallocations.
if (DAO_WALLET_SET.has(toAddrLower)) continue
```
## Effect
`main` already includes the Council and Treasury Management addresses (merged in #121), so once the daily job regenerates `api-v2.json`, the ~\$1.6M of internal movements drops out of "Other expenses". No dependency on any other PR.
## Testing notes
- Couldn't run the pipeline locally (needs Alchemy/CoinGecko keys); corrected figures appear when the scheduled job runs with real credentials.
- Change is additive and type-consistent; the import mirrors the existing pattern in `export-transactions.ts`.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
main ← feat/track-council-multisig
opened 03:06PM - 16 Jun 26 UTC
## Summary
Adds **wallet status tracking** to the balances pipeline and registe… rs two new DAO wallets:
1. **DAO Council Operational Multisig** (`0x184e…16d7`, ETH) — replaces the deprecated DAO Committee.
2. **DAO Treasury Management Multisig** (`0x96e2…4407`, ETH) — funded from the Aragon Agent for treasury/DeFi operations.
It also flags the former **DAO Committee** wallets, whose funds are not currently under DAO control.
Refs proposal [DAO Committee Deprecation & Replacement](https://decentraland.org/governance/proposal/?id=bb2b8234-42aa-4ca2-a049-3c7355d4caa4).
## Changes
- **`entities/Wallets.ts`**
- New `WalletStatus` enum (`active` | `disputed`) on the `Wallet` model.
- Adds the **Council Operational Multisig** (`0x184e…16d7`, active).
- Adds the **Treasury Management Multisig** (`0x96e2…4407`, active).
- Flags both former **DAO Committee** multisigs (ETH + Polygon) as `disputed`.
- **`export-balances.ts`** — propagates `status` into `balances.json` / `balances.csv`.
## ⚠️ Known limitation — DeFi positions not yet tracked
Balances only cover the fixed token list in `entities/Tokens.ts` (MANA, ETH, MATIC, DAI, USDT, USDC, WETH). The Treasury Management wallet is meant to deploy funds into DeFi, where holdings become **untracked** tokens — staked ETH (stETH/wstETH/rETH), LP tokens, vault receipt tokens (aTokens, yVault shares). Those positions will **under-report** here until a follow-up extends `TOKENS` or integrates a portfolio API (DeBank/Zapper/Zerion). Documented inline.
## Polygon note
Balances are scanned on **both** networks for every tracked address, so a **same-address** Polygon Safe will be picked up **automatically** once deployed. If deployed to a *different* address, add a second entry in `Wallets.ts` (documented inline).
## Rollout — merge this first
⚠️ **Merge before the UI PR.** The companion UI change is backward-compatible and only renders the new wallets / disputed warnings once this pipeline publishes the updated `balances.json` (daily job or manual run).
**Companion UI PR:** decentraland/governance-ui#250
## Testing notes
- Couldn't run the pipeline locally (needs Alchemy/CoinGecko keys); new balances appear when the scheduled job runs with real credentials.
- Change is additive and type-consistent; CI/ts-jest will typecheck.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
main ← docs/improve-readme
opened 02:01PM - 01 Apr 26 UTC
## Summary
- Rewrote README with complete setup instructions, environment varia… ble reference table, per-script descriptions, and automated workflow overview
- Fixed outdated **Infura** reference — the codebase uses **Alchemy**
- Fixed script paths in contributing section (added `./src/` prefix)
- Removed unnecessary `npm link typescript` step
- Added missing environment variables to `.env.example`: `ALCHEMY_ETH_URL`, `ALCHEMY_POLYGON_URL`, `DCL_SUBGRAPH_API_KEY` (all used in the workflow but previously undocumented)
- Grouped and commented `.env.example` entries by service for clarity
## Test plan
- [ ] Review README renders correctly on GitHub
- [ ] Verify all links in the README are valid
- [ ] Confirm `.env.example` covers all variables referenced in `.github/workflows/pull-data.yml`
🤖 Generated with [Claude Code](https://claude.com/claude-code)
main ← improve-transaction-tagging
opened 05:43PM - 25 Mar 26 UTC
- Detect MATIC Marketplace and ETH Marketplace transactions via event log topics… (ported from original export-transactions.ts)
- Add OpenSea, Rental Fee, SAB, and Facilitator address-based tag rules
- Use eth_getTransactionByHash called contract as primary tag source for NAME mints, Curation Fees, Vesting, etc.
- Fall back to TagType.OTHER for untagged transactions (consistent with original behavior)
- Fix USD amount rounding: store full precision instead of rounding to 2 decimals
main ← upload-full-tx-history
opened 03:03PM - 25 Mar 26 UTC
Add historical transaction years (2020–2023), fix current year tab, fix USD deci… mal rounding
Extend the manual dispatch step to fetch and upload transactions for 2020, 2021, 2022, and 2023 (in addition to the existing 2024 and 2025)
Change the daily current-year step to upload to the Transactions tab (without year suffix) instead of Transactions{YEAR}, matching the existing sheet structure
Remove rounding of USD amounts so small values (e.g. 0.0003 MANA) are stored with full precision instead of showing $0.00
main ← get-historic-transactions
opened 04:23PM - 24 Mar 26 UTC
Added src/getAllTransactions.ts — a new script that fetches all DAO wallet trans… actions (IN, OUT, INTERNAL) from Alchemy for a given year, applies historical USD pricing via CoinGecko (with DeFiLlama as fallback), and tags each transaction using the existing Tags entity. Outputs transactions-{year}.json and transactions-{year}.csv to ./public/.
Updated .github/workflows/pull-data.yml with two new steps:
Upload historical transactions (manual runs only): generates and uploads 2024 and 2025 data to the Google Sheet tabs Transactions2024 and Transactions2025.
Pull transactions current year: runs daily, generates and uploads the current year's transactions to Transactions{year}.
main ← add-dao-council-expenses
opened 03:05PM - 02 Dec 25 UTC
In this PR:
- Track DAO Council compensation as a dedicated expense category
I’m working on a PR to automate the Poll > Draft proposals, that’s the only remaining thing that I have noted from our conversation.
What are the things that are still missing? Please let me know and will review (Or as I suggested in our call, create a bug report on any of the related Github repositories)
About the monthly updates: We post them on the first two weeks of the following month, I’m planning to publish June early next week.
Thanks!
ginoct
July 7, 2026, 12:49pm
4
Regarding RFI responses, @toxicwaifu personally pinged the Council a week ago about this topic, and I also mentioned it yesterday in my monthly call with them.
Based on what I know, they were working on the 2030 vision and will publish something soon.
2 Likes
Thank you for the updates. I’ll take a look when I can. I’ve pretty much listed what I’ve come across. A couple new questions though.
with the Foundation dis associating with DAO, how will people find accurate information on the DAO? Is there plans for a DAO dedicated web page that is run by the DAO?
2nd, many documents are outdated, will someone be in charge of making sure things are accurate and links aren’t broken?
