Governance Status
What you can and can’t vote on today, stated plainly. The Guild is a task marketplace first; governance is an optional layer on top. The on-chain surface lives at decisions.
The participatory layer runs in the Telegram bot. These are off-chain guild votesrecorded in the bot’s database — a way to organise and read the room, not on-chain governance and not a way to move escrowed funds.
/proposals · /new72h yes / no / amend proposals. Signalling, not settlement.
/pollUp to 6 options. A quick read of where members stand.
Teams with a lead and a member list. Charters, sunset dates and budgets are part of the PROPOSED working-group framework — not yet agreed, and no live group has any of them.
There is a working-group report & sunset watcher in the bot, and it is off. Read that as unbuilt rather than as a safeguard: nothing auto-expires because no reporting cadence or sunset policy has been agreed to expire against, not because a protection is holding the line. Leads and members drive this entirely today.
The Guild’s DAO portal is CrumbsUp (reachable via /dao in the bot). Muan is a candidate for a dedicated governance platform later — it is not asserted as live and hosts nothing for the Guild today.
The one thing to be precise about: members cannot cast on-chain governance votes on the Guild today. Here is exactly where each on-chain surface stands.
CV2 is our own deployment— a fork of the Radix Foundation’s Consultation-v2 blueprint, which the Foundation never deployed itself. bigdev deployed the package and instantiated the component in April 2026, both paid for by the Guild’s own operator account, and the Guild holds its owner role. The Foundation does not run it, does not moderate it, and has not endorsed it. Treat it as ours and judge it accordingly.
CV2 is PARKED as of 2026-07-31 — we are not developing it further until the Guild DAO needs it. That is a park, not a retirement: the component stays on mainnet and reads stay live, so you can still see existing checks at decisions. Create and vote are off in this app, and no vote has ever been cast through this component on mainnet. Note that switching them off is a gate in ourapp — the component’s own make and vote methods are public on-chain and stay callable by anyone building the transaction by hand.
Verify (on-chain, now): check the deployer and owner for yourself — they are the Guild’s, not the Foundation’s. component_rdx1cqj99hx2rdx04mrdvd3am7wcenh6c26m2w5uzv8vkv9pudveqzy7d2
CV3 conviction voting is parked. Its interface and transaction builders were removed from the app on 2026-07-18 (PR #216)— token-weighted funding governance is expected to move to a dedicated platform rather than live here. The reason no address is published here is narrower than “there is no such contract”: a real ConvictionVoting component does exist on-chain. What we will not publish is the address this app once had wired for CV3, because it resolves to a Task Escrow component, not a conviction voter — citing it would point you at the wrong thing.