Tooling WG · Vote delegation & governance notifications

Two tools sat on this card from July 2026: vote delegation, and the Jazzer bot as the way to push proposals into Telegram. Delegation now has a written policy and no code. The bot was switched off five months before this card was created.

Vote delegation

The design came out of Peachy's January 2026 thread on governance tools and processes. Voting weight is stake units on validators, converted to their XRD equivalent and counted at a snapshot taken before the vote opens, so a holder cannot see a proposal, stake into it and vote. Holders who have delegated elsewhere are excluded from that count. linuxx proposed a membership NFT minted against a staking minimum, delegable by whoever holds it.

The DAO has since written the rule down. The Token Delegation Policy in the governance framework repository runs eleven sections: one delegate at a time, revocable at any point and effective from the next snapshot, self-delegation to take the vote back, delegated votes counting identically toward quorum, and a voluntary Public Delegate Registry that the Governance & Legal Working Group maintains. Where a single delegate approaches the constitutional quorum of 10% of circulating XRD, the Radix Accountability Council may flag the concentration and ask delegators to review it. The policy calls that advisory and leaves hard caps to a governance vote.

Two of its clauses describe a mechanism that does not exist yet. Section 3.1 records delegation on-chain; section 6.2 says every delegation relationship is visible there. The Radix DAO Consultations component, the instance the framework's on-chain register names, runs blueprint Governance version 1.0.0. Its twenty entry points, one function and nineteen methods, include no way to delegate a vote. The three voting methods each take the voting account itself, and the component stores parameter sets, temperature checks, proposals and elections, with nowhere to record who votes for whom. Read at epoch 338,958 on 28 August 2026, all three of its counters still read zero.

The DAO Parameters Registry is the document that reconciles them. Section 8 lists delegation as "Allowed (Phase 2, when platform supports delegation)". The policy is finished. The platform it depends on is the governance app, and delegation sits in that app's backlog.

None of this is law yet. The policy sits in the reference library, and the DAO's operative repository is the one that carries force: "if it's there, it's law". Read on 28 August 2026 its constitutional, governance, legal and parameters directories hold a .gitkeep and nothing else, with every document waiting in pending/, and the delegation policy is not among them. The library's own status table marks the Token Delegation Policy active on a trigger, "activates when delegation is supported on platform", which makes sections 3.1 and 6.2 dormant rather than contradicted.

One word to keep apart. The operative set uses Delegate in a different sense: the Delegate Mandate defines five Delegated Functions, execution agents the Radix Accountability Council seats to carry out decisions it has no part in making. A delegate under the Token Delegation Policy receives a vote. A Delegate under the Mandate signs a transaction someone else authorised.

The Jazzer bot is off

This card listed deploying the Jazzer bot for proposal alerts, and cited a thread that asked for the opposite. Austin opened RFC: Jazzer bot on 8 February 2026 with one line: he proposed turning the bot off in the main Telegram channel, where it had been posting repeating introductory messages. James.xrd agreed and called for a vote. Peachy and VandyILL each ran a poll. SaucyNoodle proposed a middle path, a one-line reply pointing back at the original message and sent from a dedicated account, so the text stopped breaking up conversations. On 20 February the bot's operator, Jazzer_9F, closed the thread himself: the vibe was clear, he would deactivate it over the weekend, and the functionality stays available if good content ever arrives for it.

That last clause is the open door. Proposal outcomes are published only inside the governance dApp today, and the person who ran the channel-side plumbing has said he can bring it back. Anyone who wants proposal alerts in Telegram has a working bot to ask for and a Working Group to ask in.

Deliverables

• Implement delegation in the governance component and expose it in the app, so sections 3.1 and 6.2 of the policy describe something real.
• Stand up the Public Delegate Registry the policy assigns to the Governance & Legal Working Group.
• Decide how proposals and elections reach Telegram now that the bot that did it is off.

Dependencies & cross-references

• Governed by Daffy's Radix DAO framework (repo Shadaffy/radix-dao); see the Governance Framework Reference Repo and Charter (Round 1).
• Extends the governance app, takes its snapshot rule from the Proposal & Voting Framework, and is recorded in the Parameters Registry.
• Delegate conduct falls under the conflict-of-interest policy and code of conduct.

Sources

• Token Delegation Policy (governance framework repository)
• DAO Parameters Registry, section 8, Identity & Participation Parameters
• Governance tools and processes needed (delegation design, January 2026)
• RFC: Jazzer bot (the shutdown thread, February 2026)
• Radix DAO Consultations component on the Radix Dashboard
• Operative governance repository and the reference library's precedence and document status
• Radix DAO Delegate Mandate v1.0.0, 25 August 2026