---
title: "Daffy"
url: "https://radix.wiki/community/daffy"
version: "2.3.0"
updated: 2026-08-20
last_verified: 2026-08-20
license: CC-BY-4.0
license_url: "https://creativecommons.org/licenses/by/4.0/"
---

# Daffy

| Daffy |  |
| --- | --- |
| Type | Community contributor (pseudonymous) |
| Known for | Radix DAO governance framework; community-run [Stokenet](/contents/tech/releases/stokenet) |
| GitHub | [@Shadaffy](https://github.com/Shadaffy) |
| Repositories | [radix-dao-governance](https://github.com/Shadaffy/radix-dao-governance) (operative), [radix-dao](https://github.com/Shadaffy/radix-dao) (reference library) |
| Works with | [Radix Accountability Council](/ecosystem/radix-accountability-council) |
| Category | [Community](/community) |

**Daffy** is a pseudonymous contributor to the [Radix](/ecosystem) community who drafted and maintains the governance framework for the **Radix DAO**, and who hosts most of the community-operated [Stokenet](/contents/tech/releases/stokenet) test network. Both roles sit at the centre of the network's 2026 handover from the [Radix Foundation](/ecosystem/radix-foundation) to community control, and both are documented in the public update record of the [Radix Accountability Council](/ecosystem/radix-accountability-council) (RAC), the body stewarding that transition. Daffy publishes under the GitHub handle [@Shadaffy](https://github.com/Shadaffy); the RAC refers to the same work as ["daffy's DAO draft github repo"](https://t.me/RadixAccountabilityCouncil/814) and [points the community to it](https://t.me/RadixAccountabilityCouncil/887) as the governance repository of record.

## The Radix DAO governance framework

The framework Daffy authored is published in two repositories. [radix-dao-governance](https://github.com/Shadaffy/radix-dao-governance) holds the operative documents of Radix DAO LLC – the Operating Agreement, the Charter, the operational policy library, and the DAO Parameters Registry – while the older [radix-dao](https://github.com/Shadaffy/radix-dao) repository keeps the drafts, templates, analysis material, and the activation roadmap behind them. Its stated design principle is that ["the DAO makes decisions, the system executes them, and no single entity controls both"](https://github.com/Shadaffy/radix-dao).

The documents are not adopted in one founding vote. The Operating Agreement sets out a [four-step founding sequence](https://github.com/Shadaffy/radix-dao-governance/blob/master/PROPOSALS.md): a Constitutional Ratification vote (GP-PRE-1) approves the Charter and policy library; the Transition RAC then files the Certificate of Formation, leaving the company member-managed and community governance advisory; an election seats a permanent RAC (GP-ELECT-1); and a final Activation Vote (GP-ACTIVATE-1) makes the company algorithmically governed, at which point governance outcomes become binding and the Transition RAC sunsets. As of the repository's current state, **no documents are yet operative** – GP-PRE-1 is marked ready for review and the two later proposals remain scaffolds. The repository's own convention is that each merge corresponds to a passed vote, so its commit history doubles as the governance audit trail.

The framework was drafted alongside the RAC's legal counsel rather than in isolation. RAC updates record Daffy joining the [first meeting with the lawyers in May 2026](https://t.me/RadixAccountabilityCouncil/844) to introduce the repository, [continuing through the drafting of the Operating Agreement](https://t.me/RadixAccountabilityCouncil/866), and [bridging community contributions into counsel's drafts](https://t.me/RadixAccountabilityCouncil/871). In April the RAC credited the near-complete Marshall Islands DAO LLC wrapper to ["Daffy sweat and community's feedbacks"](https://t.me/RadixAccountabilityCouncil/814) and asked the community to attack it for governance-capture and low-quorum failure modes. For how the resulting structures fit together, see [Radix Governance](/contents/tech/core-concepts/radix-governance) and the discussion-stage [Radix Network DAO Charter](/ideas/radix-network-dao-charter).

## Running Stokenet for the community

[Stokenet](/contents/tech/releases/stokenet) is the Radix test network. When the Foundation began winding down in 2026, its Stokenet validators, stake, and Gateway had to move to community hands or stop. The RAC recorded the migration through May 2026: Daffy [hosting the validators and the new Gateway](https://t.me/RadixAccountabilityCouncil/850) with Timan running one validator alongside, the [node and validator transition completing](https://t.me/RadixAccountabilityCouncil/853), and control passing [effectively to the community](https://t.me/RadixAccountabilityCouncil/857). By mid-June the RAC described the transition as complete and noted that [Daffy was "responsible for running and supporting most of it at this point and taking on full risk"](https://t.me/RadixAccountabilityCouncil/876), pending community sign-off and funding.

That funding gap is the reason the arrangement matters beyond one person's server bill: the network's developer test environment ran for months on an individual's own account, uncompensated, while the entity meant to pay for it was still being formed.

## The Stokenet proposal (2026)

In July 2026 the Stokenet arrangement was put to the community through the on-ledger consultation dApp. The RAC [opened a Temperature Check](https://t.me/RadixAccountabilityCouncil/904) on 25 July for Daffy's proposal – asking the Foundation to fund the Stokenet operation it had handed over, since the DAO is not yet in a position to be the accepting entity – alongside a separate website proposal from Timan. On 28 July the RAC confirmed that [both Temperature Checks had passed](https://t.me/RadixAccountabilityCouncil/906) and were lifted to full Governance Proposals, opened for voting at [consultation.mountain-top.live/proposal/1](https://consultation.mountain-top.live/proposal/1) (Stokenet) and [/proposal/2](https://consultation.mountain-top.live/proposal/2) (website). Both ran the component's standard seven-day window and closed on 4 August 2026.

Voting is XRD-weighted and non-custodial – one [XRD](/contents/tech/core-protocols/xrd-token) equals one vote, read from an on-ledger balance snapshot, with no tokens locked or transferred. The two-stage route these proposals took, Temperature Check first and a binding Governance Proposal second, is the pattern the transition-era process uses; it was exercised earlier in 2026 for [a milestone-funding proposal that followed the same escalation](https://t.me/RadixAccountabilityCouncil/841). Proposals are discussed on [RadixTalk](/ecosystem/radixtalk) before votes open.

## How the vote closed

The proposal Daffy put on-ledger asks the [Radix Foundation](/ecosystem/radix-foundation) for a fixed **$4,000 in XRD covering May–December 2026** – eight months of one Gateway, two supporting full nodes, three validators, redundant ledger and database backups and a monitoring node, all hosted in the EU/EEA, run on a best-effort basis at a stated 98–99.5% uptime with monthly reporting. The [XRD](/contents/tech/core-protocols/xrd-token) would be staked rather than sold, he wrote, since selling was never the point: “had my intention been to sell, I would have requested stablecoins”. It is a revision of a [28 March 2026 proposal](https://radixtalk.com/t/stokenet-call-to-action/2251/30), repriced downward after two months of actually operating the network removed the unknowns.

Voting opened on 28 July 2026 at 06:42 UTC and closed seven days later, on 4 August. The record sits in the [Governance component](https://dashboard.radixdlt.com/component/component_rdx1czn9hrgd30x742k6jw2e6psj9jlkqvu2cj4hcry60p7f38hxd3k3xt), whose parameters set a seven-day proposal window, a 0.5 approval threshold and a **671,470,000 XRD quorum** – about 5% of circulating supply. The Stokenet proposal drew **55 votes, every one of them “Yes”**; the companion website proposal drew 56, every one “Approve”. Not a single account voted against either.

Both proposals cleared that quorum. Recomputing the weight behind the votes from the voting accounts’ holdings gives **910,989,217 XRD on the Stokenet proposal and 910,406,795 XRD on the website proposal** – about 136% of the 671,470,000 written into each. Liquid XRD is the small part of it: 125,897,148 of the Stokenet total, with the other 785,092,070 held as stake units and converted back at each validator’s current exchange rate. Counting only liquid balances understates these accounts more than sevenfold and is the reason an earlier version of this page reported the vote as falling short. The May 2026 [Xi’an](/contents/tech/research/hyperscale-rs) kickoff vote clears its own bar the same way: 1,186,155,329 XRD against a 940,046,370 quorum, from 254 accounts casting 256 votes, 255 approve to one reject. (These are balances read on 9 August 2026 rather than the snapshot the dApp weighted at voting time, so the figures are indicative; the margin is wide enough that the direction is not in doubt.) Meeting a quorum does not by itself release money. The Xi’an milestone was paid by the Foundation directly, on the strength of clear community consensus.

What follows for the testnet was stated in the proposal itself: without funding, Daffy said he would limit further losses and **decommission the Stokenet Gateway in mid-August**, leaving developers to stand up their own at an estimated $350–400 per month each. That deadline passed without the Gateway going down: it answered a status call on 20 August 2026 at ledger epoch 255,095, state version 425,461,885, on release v1.10.6. No funding decision has appeared in the Council’s public updates, and the operator has since committed to a reset cadence that runs well past the point at which he said he would stop.

## Resetting Stokenet (August 2026)

Running a test network includes destroying it on schedule. On 16 August 2026 Daffy [told the Radix Developer Discussion group](https://t.me/RadixDevelopers/65974) that Stokenet would be reset, with no date attached and a commitment that one would follow no later than seven days in advance. The date came two days later, at 17:57 UTC on 18 August, in the main Radix Telegram group: [Saturday 29 August 2026, 07:00 UTC](https://t.me/radix_dlt/998662). That is eleven days’ notice against the seven promised. The [Radix Accountability Council](/ecosystem/radix-accountability-council) [relayed it](https://t.me/RadixAccountabilityCouncil/915) to its own channel 24 minutes later, addressed to the developers and beta testers who stand to lose deployed work.

The date moved earlier because the reset was rehearsed rather than scheduled on plan. On separate hardware he had a fresh genesis running with four validators reaching consensus, a Gateway in sync and a dashboard showing live activity, and reported that reset testing had gone faster than anticipated. The network goes down at 07:00 UTC and stays down for several hours, because he is taking the same window for server maintenance.

What survives is what the ledger derives; what goes is what the ledger stored. The network ID, the [Gateway](/contents/tech/core-protocols/radix-gateway-api) URL and the well-known addresses for test [XRD](/contents/tech/core-protocols/xrd-token), the faucet and the native packages are unchanged, and so is every account address, since addresses are derived from keys. Balances, transaction history, every resource, package, component and [dApp definition](/developers/frontend/04-dapp-definition-and-verification), and all on-ledger persona data are destroyed. The full terms, and the list of what a developer has to redo afterwards, are on the [Stokenet](/contents/tech/releases/stokenet) page.

Two lines in the announcement are the operator speaking rather than the release notes. He intends to **repeat the reset every 9–12 months**, which turns a one-off cleanup into a published cadence a team can plan a launch around. And he offered to move the date for anyone whose launch it breaks, asking them to say so in the [Radix Developer Discussion](https://t.me/RadixDevelopers) group. A network run by one person can be negotiated with directly, and it stops when that person does – which is what the funding proposal above was about.

## External links

- [GitHub – @Shadaffy](https://github.com/Shadaffy)
- [radix-dao-governance – operative governance documents](https://github.com/Shadaffy/radix-dao-governance)
- [radix-dao – reference library and activation roadmap](https://github.com/Shadaffy/radix-dao)
- [Radix Consultation – on-ledger governance voting](https://consultation.mountain-top.live)
- [Radix Accountability Council – Telegram](https://t.me/RadixAccountabilityCouncil)