---
title: "RadQuest"
url: "https://radix.wiki/ecosystem/radquest"
version: "1.0.0"
updated: 2026-08-20
license: CC-BY-4.0
license_url: "https://creativecommons.org/licenses/by/4.0/"
---

# RadQuest

| RadQuest |  |
| --- | --- |
| **Type** | Guided onboarding dApp for the [Radix Wallet](/contents/tech/core-protocols/radix-wallet) |
| **Status** | 🔴 Closed – last quest settled on ledger 27 April 2026; `radquest.io` registration expired 10 August 2026 |
| **Operated by** | [Radix Foundation](/ecosystem/radix-foundation) – a [Priority 3](/ecosystem/radix-accountability-council) service in the 2026 transition |
| **Launched** | [30 July 2024](https://www.radixdlt.com/blog/radquest-redefining-web3-onboarding), relaunched [4 September 2024](https://www.radixdlt.com/blog/update-radquest-relaunch) |
| **Source code** | [github.com/radixdlt/radquest](https://github.com/radixdlt/radquest) – public, TypeScript, eight [Scrypto](/developers/scrypto) packages, no licence file |
| **Hero Badges** | 200,158 minted (`resource_rdx1n2mvky7na57d832lypd9xy5ftxt7lynu3flyn084gfncayshmmdwga`) |
| **RadMorphs** | 10,984 forged (`resource_rdx1nt2q2rks2xgus6etcpeq4c8ysuj0l5pwhs9r3cxw6qtly5kxqddp2e`) |
| **Ledger read** | Epoch 336,703 / state version 552,583,231, 20 August 2026 |
| **Verified** | 20 August 2026 |

**RadQuest** was the [Radix Foundation](/ecosystem/radix-foundation)’s guided onboarding dApp: a gamified tour that walked a newcomer through installing the [Radix Wallet](/contents/tech/core-protocols/radix-wallet) and using the network’s distinguishing features – [native assets](/contents/tech/core-concepts/native-assets-vs-token-approvals), [Smart Accounts](/contents/tech/core-protocols/smart-accounts), [Personas](/contents/tech/core-protocols/personas) and readable [transaction manifests](/contents/tech/core-protocols/transaction-manifests) – by having them do it rather than read about it, and paid them in on-chain collectibles for finishing.

It launched on 30 July 2024, was reworked that September, and stopped. The last quest it settled on mainnet was on 27 April 2026; three days after the last Hero Badge was minted its repository had its build pipelines switched off; and on 10 August 2026 the `radquest.io` registration expired, leaving the address on a registrar parking page. No closure announcement was published – the four RadQuest posts on the Radix blog all date from 2024 – so what follows is the sequence the artefacts themselves record.

## The onboarding pitch, 2024

The launch post, [RadQuest: Redefining Web3 Onboarding](https://www.radixdlt.com/blog/radquest-redefining-web3-onboarding) of 30 July 2024, framed the problem as one of confidence rather than information: newcomers are held back by jargon, unfamiliar interfaces and the fear of an irreversible mistake. RadQuest’s answer was a guide character, Jetty, who led users through wallet setup and a sequence of quests, rewarding each with [XRD](/contents/tech/core-protocols/xrd-token) and with gift boxes whose contents could be combined into collectible NFTs.

The first week was, by the Foundation’s own account, larger than expected. The [relaunch post](https://www.radixdlt.com/blog/update-radquest-relaunch) of 4 September 2024 records over four million transactions processed by the network in that week, 60,000 Radix Wallet downloads across iOS and Android, and more than 1.15 million XRD of RadMorph trade volume on the [Trove](/ecosystem/trove) NFT marketplace.

It also records why that was a problem. The XRD rewards drew farming at a scale the Sybil defences did not absorb, and the transactional load degraded the experience for everyone else. The relaunch, timed for Token2049 Singapore, removed XRD rewards outright and replaced them with a “golden ticket” system – the post notes that a KYC gate was considered and rejected as disproportionate for an onboarding tool. RadQuest ran in that second form for the remaining nineteen months.

## The asset system

RadQuest’s rewards were real on-ledger resources, documented for third parties in [Tech Talk: Using RadQuest Assets With Your dApp](https://www.radixdlt.com/blog/tech-talk-using-radquest-assets-with-your-dapp) (29 July 2024) so that other dApps could recognise a RadQuest graduate and tailor what they showed them.

- **Hero Badge** – one non-fungible badge per quester, tracking progress and presented on every interaction. Because it is issued once per user, its supply is a headcount.
- **Gift Boxes** – earned by completing quests, in four grades (Starter, Simple, Fancy, Elite), each opening into ingredient assets.
- **Elements** – a fungible crafting material; five Elements fuse into one RadGem.
- **RadGems** and **Morph Energy Cards** – non-fungible ingredients with randomly generated colour, material and rarity traits.
- **RadMorphs** – the final collectible, forged from RadGems and a Morph Energy Card, with over 3,000 possible combinations.
- **Ottercoin** and **Clams** – two fungible tokens with no crafting role, kept as tradeable curiosities to teach the idea of a resource.

Each step of that chain was its own [Scrypto](/developers/scrypto) package rather than one monolith. The [repository](https://github.com/radixdlt/radquest/tree/main/scrypto-packages) carries eight: `radquest`, `hero-badge-forge-v2`, `gift-box-opener-v2`, `card-forge-v2`, `radgem-forge-v2`, `quest-rewards-v2`, `ticket-machine` and `clam-dex`. Their mainnet addresses are committed in the repository’s [shared constants file](https://github.com/radixdlt/radquest/blob/main/packages/common/src/constants.ts), which is why the system remains readable now that the front end is gone.

## What the ledger records

Read at epoch 336,703 / state version 552,583,231 on 20 August 2026, the two resources that count RadQuest’s reach are still there and still hold their totals:

| Resource | Address | Supply |
| --- | --- | --- |
| RadQuest Hero Badges | `resource_rdx1n2mvky7na57d832lypd9xy5ftxt7lynu3flyn084gfncayshmmdwga` | 200,158 |
| RadMorphs | `resource_rdx1nt2q2rks2xgus6etcpeq4c8ysuj0l5pwhs9r3cxw6qtly5kxqddp2e` | 10,984 |

Two hundred thousand badges is the number RadQuest is best measured by: one per person who started it, minted by the protocol rather than counted by an analytics script, and unaffected by the domain lapsing. Against that, 10,984 RadMorphs is the count of users who went far enough to forge the end-of-chain collectible – roughly one in eighteen.

The same records date the ending precisely. The last transaction to mint a RadMorph was committed at **06:24:15 UTC on 27 April 2026**, burning two RadGems and a Morph Energy Card; the last transaction against the quest-rewards component `component_rdx1cpklwp2zr6padewcxdkvnqydwp6mlzquyuuvlsztm8agdjdpmfzkxc` followed fourteen minutes later at 06:38 UTC the same morning. The Hero Badge resource saw one further transaction, on 1 May 2026, and nothing since.

## How it wound down

RadQuest was named in the Foundation’s [operational stack map](https://www.radixdlt.com/blog/the-foundation-operational-stack-mapping-the-2026-transition) of 26 January 2026 as a **Priority 3** service – “non-critical but maintained” – described there as a guided onboarding dApp whose front end and “essential backend/on-chain services” were both run by the Foundation. Priority 3 was the tier explicitly offered to the community to take over, open-source, or shut down.

On 17 February 2026 the Foundation opened [Action on P3 Foundation Services](https://radixtalk.com/t/action-on-p3-foundation-services/2238) on RadixTalk, asking for input on each service by name. RadQuest is the one the post singles out as carrying “ongoing monthly costs”, and the stated case for switching it off was to reduce recurring operating expense and maximise the assets transferred to the community. The thread drew seven posts and stopped on 22 February 2026.

The repository shows what happened next. On **4 May 2026** – three days after the last Hero Badge transaction – three commits landed together: a deployment guide covering local development and a production Kubernetes setup, a README link to it, and a change that renamed both GitHub Actions workflows to `ci.yaml.disabled` and `helm-changes.yml.disabled`. That is the shape of a handover rather than a deletion: turn the pipelines off, write down how someone else could stand it back up. Nothing has been committed since, and the repository is public but carries no licence file, so the code is readable rather than open source in the formal sense.

The last visible step was passive. The `radquest.io` registration expired on **10 August 2026 at 10:36 UTC**; the domain’s nameservers are now `ns1.lander.d.parity.domains` and it serves Namecheap’s expired-domain page, headed “Domain registration has expired”. A P3 service that ran for twenty-one months and issued two hundred thousand badges left the network by not being renewed.

## External links

- [github.com/radixdlt/radquest](https://github.com/radixdlt/radquest) – the full source, front end, backend and Scrypto packages
- [RadQuest: Redefining Web3 Onboarding](https://www.radixdlt.com/blog/radquest-redefining-web3-onboarding) – the Radix Blog, 30 July 2024
- [Tech Talk: Using RadQuest Assets With Your dApp](https://www.radixdlt.com/blog/tech-talk-using-radquest-assets-with-your-dapp) – the Radix Blog, 29 July 2024
- [Update: RadQuest Relaunch](https://www.radixdlt.com/blog/update-radquest-relaunch) – the Radix Blog, 4 September 2024
- [The Foundation Operational Stack: Mapping the 2026 Transition](https://www.radixdlt.com/blog/the-foundation-operational-stack-mapping-the-2026-transition) – the Radix Blog, 26 January 2026
- [Action on P3 Foundation Services](https://radixtalk.com/t/action-on-p3-foundation-services/2238) – RadixTalk, 17 February 2026