In January, the Foundation set out a transition plan to move to a community-led future for Radix.

From May, that plan moves to its next phase. The Foundation is reducing to essentials and entering maintenance mode. Most of what was committed in January has been delivered. What remains is the legal entity and the asset transfer, and the community has what it needs to land both.

What’s been shipped:

• The community elected a Radix Accountability Council (RAC) within 30 days of the announcement, and the RAC is now well underway with setting up the DAO entity. The Foundation approved a two-stage grant of $67,000 and 10m XRD to fund its set-up and initial operation.
• Token holder consultations have run with over one billion XRD participating, including a vote on the DAO's location. 
• RFPs for P1 services have been published and responded to. The Gateway, Signaling Server, and Radix Connect Relay are pre-funded by the Foundation through the end of December 2026. 
• The Foundation open-sourced the V2 Consultation dApp. Anyone in the community can now run governance tooling without the Foundation.
• Using Hyperlane, the eXRD↔XRD bridge route is now fully permissionless. 
• Outstanding contract credit with PrimeVault (asset custody) has been secured for the community entity to use. 
• The wallet has been updated to reduce dependency on Foundation-operated infrastructure. 
• The majority of the relevant P3 items in the Foundation operational map such as Dashboard, Dev Console, Supply API for CoinGecko and CMC, docs.radixdlt.com, academy.radixdlt.com, wallet.radixdlt.com, the image service, and the asset service, are now running on community-run or free-to-host alternatives. 

‍

That is significant progress. The DAO entity is the remaining piece, and the community has the funding, the operational framework, and the support in place to establish it. Treasury transfer follows from there.

What this means operationally

Since the 2025 restructure, the Foundation has been supporting a broad range of services including infrastructure, developer tooling, and community experiences. Detailed information on those services was published here in January. Many of these can (and should) be operated by others, and the transition process is designed to make that happen. 

For P1 services like the Gateway and Market Making for centralized exchanges, the focus has been on pre-funding to ensure continuation while the community decides what comes next. The Gateway is funded through December 2026; Market Making is funded through September.

For P2 items like Web2 logins and open-source code, the focus has been on improving documentation, reducing reliance on (or streamlining) specific hosting services, and cleaning up the code to minimise dependencies. This extended to items like eXRD, which is now fully permissionless with bridging backed and operated by Hyperlane. A clear example sits inside the Wallet with the implementation for users to select custom Radix Connect connectors, direct transaction manifest pasting, an APK released on GitHub, and similar features that mean the community isn't locked to defaults or specific providers.

For P3 items, the focus has been on moving services to community or free hosting. The asset and image services, docs.radixdlt.com, Dev Console, Sandbox, and Dashboard are all running on more sustainable alternatives, many of them already provided by community operators.

Some initiatives have been wound down. Outstanding Ignitions positions have been closed, Radix Rewards were distributed and the code open-sourced for future use, and RadQuest has been taken offline (also open-sourced, available for the community to restart if it wishes).

The Foundation has also supported the community with additional tooling: the V2 Consultation dApp, multi-sig options including PrimeVault credits and a reference design for on-chain multi-sig, and direct support to the RAC on entity set-up alongside the funding grant.

Maintenance mode from May

From May, the Foundation will move to an essentials only phase. This means:

• Active development of new features and services becomes minimal. 
• Social media moves to critical updates only. 
• Support and community management run in MVP mode. 
• Non-essential services such as RadQuest, Gumball Club, IDOS, and Radix Rewards will no longer be hosted on Foundation infrastructure. The code is open-sourced and any community entity can run them.

‍

The board made this decision in line with its obligations as directors, directing remaining resources toward network stability for as long as the Foundation is operational. Routine operating costs are still planned to be covered from existing fiat reserves and therefore the Foundation does not plan to sell XRD. Based on current projections, reserves are sufficient to fund the commitments set out in this post.

P1 Infrastructure

In January the Foundation committed that critical infrastructure would not be discontinued without reliable alternatives in place. That commitment is being met through the funded operation described below.

All three P1 services, the Gateway, Radix Connect Relay, and Signaling Server, have transferred to a standalone operation run by the previous Foundation DevOps team. Their proposal, submitted in response to the public RFP and available here, sets out pricing, SLA commitments, and operating terms. The Foundation has pre-funded these operations through the end of December 2026. This is the same team running these services today, so there is no handoff to an unknown operator and no gap in service.

Market Making across the main centralized exchanges that list XRD is also pre-funded through September with established Market Makers, with the option to extend if needed.

Next Steps

By the end of June, the remaining full-time development team will have completed handover of active workstreams. From that point, the handover and any remaining Foundation operations will carried by directors who will manage the financial and governance functions required for the transition. They will also have contracting capacity available if anything critical needs attention.

When a community entity is established, the intention is for the remaining treasury to transfer to it, subject to the legal and compliance steps any such transfer requires. Future decisions then sit with the community.

If a community entity is not established within the Foundation's operational timeline, assets and social logins will be held dormant where possible, with the intention of transferring them to a community entity if and when one is established. What transfers, and what doesn't, depends on the progress made within that window.

Many parts of the transition don't require a single unified entity to exist first. They require capable teams to step up for specific services. If you or your team can take on any part of the remaining stack, submit a proposal on RadixTalk.

The next concrete step is the legal entity, with treasury custody. That work is being led by the RAC, with the Foundation ready to assist where requested and the funding already in place to support it.

A note on the team

As part of the move to maintenance mode, several long-standing team members have wound down or will wind down their formal Foundation roles over the coming weeks. The most senior of these is Adam, who is stepping back from his role at the Foundation. With the transition in good shape, Adam's day-to-day role has naturally concluded. Stepping back at this point, with the operational handover ready, keeps the focus on a clean transition. The remaining directors continue, with financial and fiduciary oversight unaffected.

Adam said: "Radix has never been a straight line. There were good years and hard ones, real breakthroughs and real setbacks, plenty of things that went well, a fair few that didn't, plus a lot of unglamorous work in between. What's been built is down to the dedication of a lot of people: past and present staff, builders across the ecosystem, and a community that has stuck with it through all of it. I've spent a lot of time talking about decentralisation as a goal and the Radix community is what it actually looks like. I'm proud of what's been done and grateful to have been part of it. Radix started from Dan's vision, and I’m glad it’s passing to the community. I'm not going anywhere. I'm just changing seats, and I'm looking forward to seeing what comes next."

Where this leaves things

Four months ago, the transition was an intention. Today, the governance tooling exists, the accountability structure is in place, the critical infrastructure has a funded plan to carry forward, and the community has been active at every stage. The legal entity is the remaining piece. When that lands, what comes next is the community's to shape.

If you can run a service, build a tool, or step up for any part of the remaining stack, file a proposal. The next phase is yours.