Many people look at OpenDusk for the first time and think: “Oh, here we go again—another DAO interface for making a proposal and casting votes. Grant hands out some money, and that’s it.” I read the proposal about the August 11.8 million implicit burn-to-treasury, and then the subsequent RFCs, three times—the conclusion is not the same. This is not a performative layer of community co-governance; it’s a transitional move by the Dusk Foundation itself, shifting the “ecosystem development rights” from a single-point trust to a multisig + return-allocation structure.
The evidence is in the boundaries of power.
In the traditional foundation model: the team controls the development wallet, manages the brand, and sets integration priorities—while the community can only complain on forums.
After OpenDusk was established, the on-chain assets side gained a treasury address. The funds come from what used to be explained in the foundation narrative as “unclaimed block rewards”—specifically, the unclaimed portion within the 10% conditional rewards, plus the early implicit burn. This portion of supply used to fall under the foundation’s authority. Now it’s minted out and assigned to a 5-person committee for execution, with return allocations to all mainnet stakers.
The foundation hasn’t disappeared, but the question “Where does the money for the next batch of XSC tooling development come from?” changes from “decided by the foundation” to “committee proposal + community vote.”
More concretely, this is a signal of transferring development rights. With the late mainnet of DuskEVM, the NPEX dApp frontend, the iterative upgrades to the AEGIS security framework, Citadel’s identity layer connecting to AFM channels—work that previously had been scheduled by the core team—going forward, Grant can fund external teams directly, bypassing the foundation. The foundation shifts from “the only employer” to “the first applicant.”
The risks are here as well: in a trial period, if the committee turns out badly or Grant keeps pumping the air, can the foundation still reclaim development leadership? The RFC doesn’t write any rollback provisions, which means this step is effectively one-way. But precisely this “no-turning-back handover of power” isn’t a toy—because toys come with one-click recovery.
Do you think the foundation’s handover of power is genuinely decentralized, or are they just dumping development responsibility onto the community to take the blame?
@Dusk $DUSK #dusk
The evidence is in the boundaries of power.
In the traditional foundation model: the team controls the development wallet, manages the brand, and sets integration priorities—while the community can only complain on forums.
After OpenDusk was established, the on-chain assets side gained a treasury address. The funds come from what used to be explained in the foundation narrative as “unclaimed block rewards”—specifically, the unclaimed portion within the 10% conditional rewards, plus the early implicit burn. This portion of supply used to fall under the foundation’s authority. Now it’s minted out and assigned to a 5-person committee for execution, with return allocations to all mainnet stakers.
The foundation hasn’t disappeared, but the question “Where does the money for the next batch of XSC tooling development come from?” changes from “decided by the foundation” to “committee proposal + community vote.”
More concretely, this is a signal of transferring development rights. With the late mainnet of DuskEVM, the NPEX dApp frontend, the iterative upgrades to the AEGIS security framework, Citadel’s identity layer connecting to AFM channels—work that previously had been scheduled by the core team—going forward, Grant can fund external teams directly, bypassing the foundation. The foundation shifts from “the only employer” to “the first applicant.”
The risks are here as well: in a trial period, if the committee turns out badly or Grant keeps pumping the air, can the foundation still reclaim development leadership? The RFC doesn’t write any rollback provisions, which means this step is effectively one-way. But precisely this “no-turning-back handover of power” isn’t a toy—because toys come with one-click recovery.
Do you think the foundation’s handover of power is genuinely decentralized, or are they just dumping development responsibility onto the community to take the blame?
@Dusk $DUSK #dusk