RADIX WikiRADIX Wiki

This page indexes every project page on this wiki under Ecosystem by whether the project is still running. It exists because the wiki already recorded the answer one page at a time, and nobody could read it as a list: on 3 August 2026 a Radix holder asked in the hyperscale-rs channel for "a list of which Radix dapps are still operational and which have been abandoned", so that the dApps that are still around could be part of the migration conversation, and a second member asked this wiki to curate it.

The question has a deadline attached. Xi’an replaces the Radix Engine with a purpose-built VM (t.me/hyperscale_rs/10334), and existing dApps are expected to migrate rather than carry over untouched (t.me/hyperscale_rs/10346). Which teams are still present to do that migration is a different question from which contracts are still deployed, and this index answers the first one.

What each status means

  • 🟢 Active — the project is running and reachable. For an organization rather than a dApp this means the entity still operates, which is not the same as operating at full strength: the Radix Foundation is listed as active and has been in maintenance mode since May 2026.
  • 🟡 Testnet · 🟠 In development · 🟡 Pre-launch — being built, not yet live on mainnet for general use.
  • 🟠 Dormant — the project has not shut down and has not been withdrawn, but shows no current development or operation. Contracts already deployed may still respond; nobody is answering for them.
  • 🔴 Closed — wound down, shut off, or abandoned outright. 🔴 Departed means the project still exists but has moved off Radix.

The status on each project page is the authority; this index only groups it. Where a page's status is wrong, correcting that page and rebuilding this one is the fix — the index is generated from those fields rather than maintained by hand.

How this is checked, and what it does not prove

When this page is rebuilt, every project that publishes its own website is probed — the ones listed as running and the ones listed as dead. On 2026-08-03, 57 of 57 live-claimed projects resolved (a further 5 publish no website to probe), and 35 of 42 dormant or closed projects also resolved. Any live-claimed project that failed is flagged inline in the lists below rather than quietly listed as operational.

Those two numbers are the reason this index is built from curated status rather than from uptime. A domain outlives the project on it: a closed project's site keeps answering until someone stops renewing, and answering proves only that. Ploughshare is the clean illustration — ploughshare.nz returned HTTP 200 on 2026-08-03, and the page it returned reads "Ploughshare is under maintenance". A crawler counts that as alive. Two stronger checks have been run on parts of the directory and are worth knowing about:

  • Validator registration is read from the ledger. Staking entries here are validators, and a validator can be delisted while its website stays up. Reading the registration flag for every validator address on this wiki in August 2026 found four holding roughly 47 million XRD of delegated stake while unregistered — earning no emissions for their delegators. See the individual pages for Topradixnode, Juicy Stake, Phoenix and RadixUID.
  • Token pages carry on-ledger supply. For entries in the Token category, the resource address in the page's infobox can be read directly on the Radix Dashboard — current supply and holder count are a better liveness signal than a landing page.

Per-dApp on-ledger activity — last transaction against each project's components — is not part of this index yet. It is the check that would answer the migration question properly, and it is the obvious next thing to add.

Testnet, pre-launch and in development (8)

DAO Platform

Finance

Infrastructure

Oracle