GETTING STARTED

Welcome to Radix Guild

Your roadmap to joining and earning on Radix Guild: a task marketplace on Radix where every settled task adds to a track record anyone can check — plus the optional community votes beside it.

New to Radix?

Radix is a layer-1 network built for decentralized apps. Two things set it apart: assets are native objects on the ledger itself — not balances inside contract code — and every transaction is a human-readable manifest, so your wallet shows exactly what will move before you sign.

Both downloads live at the official page: wallet.radixdlt.com.

What you need: no XRD to install the wallet, connect it or browse the board. A little XRD for the network fee to mint a badge. To claim a task, about 80 XRD — the claim bond (10% of the reward, at least 76.45 XRD today, held until the task settles) plus network fees — covers any task paying up to about 765 XRD. We suggest holding about 100 XRD of your own.

Before you install anything

No wallet? Browse anyway.

The task board is public and read-only — browse it before you install anything. Every task shows whether its escrow is funded yet, and don't take our word for the funded ones: each points at an on-chain balance you can check yourself.

No wallet? There's still something here for you

Reading this site and telling us where it's wrong is the one thing on it that needs no wallet, no badge, no bond and no repo access. The report itself is the whole deliverable.

Cash rewards are paused: a report earns a straight answer and credit when the fix ships. Have a wallet and a Guild badge? Check the task board — a funded task for the same work may be open.

IDIdentity & Onboarding

01

Connect Radix Wallet

Download the official Radix Wallet and connect with one click. Your wallet is your identity.

02

Mint a Free Badge

Choose a username and mint your Guild Badge — an on-chain NFT, free but for the network fee, that records your Guild membership. Your XP and trust record are account records; your tier is the badge's own on-chain field, set at mint. The badge's XP field can be written only by the operator, with an admin badge — it was written six times in April 2026, never since — and a task payout never reaches it.

Go to Mint a Free Badge →
03

Register in Telegram

Open @radix_guild_bot and type /register with your wallet address. This links your wallet to your Telegram account, so the bot can check your badge and you can take part in the community votes.

Open Bot →
GUILD BADGE NFT

VOTECommunity Votes

Nothing Here Is Binding

Community votes are an optional layer on the task marketplace: free, off-chain and non-binding, run through the Telegram bot. None of them can move escrowed funds or change a platform parameter.

Two Kinds of Vote

Free off-chain votes in Telegram, one per Telegram account, plus on-chain CV2 temperature checks readable via the bot. No tier weighting exists or is planned, and CV2's own weighting is XRD-based. CV2 is parked indefinitely: reads stay live, voting is off.

Yes!
Maybe
No
ILLUSTRATIONNOT A LIVE VOTE

The Task Pipeline

Earn XRD and XP by completing tasks for the community.

1

CLAIM

Browse funded tasks and claim one that fits. Claiming locks a bond of 10% of the task reward, at least 76.45 XRD today (an owner setting), held until the task settles and then credited back to you, unless a dispute is raised, in which case it is split the same way as the reward. It is at risk once your deadline passes.

2

WORK

Complete the deliverable. Submit a GitHub PR or proof of work.

3

VERIFY

The poster reviews and approves. If the task set a PR-merge check, the reviewer clicks verify to confirm the merge — automatic polling is planned, not live.

4

PAYOUT

The poster approves, which credits your reward inside escrow, plus XP — you collect it with your own signed withdrawal. If a poster goes quiet after you submit, you do not need a dispute: once the review window lapses, anyone can trigger the escrow's release for the full reward — a dispute left to the 7-day default returns only half. See /money.

XPXP & Tiers

Member
0 XP
Contributor
100 XP
Builder
500 XP
Steward
2,000 XP
Elder
10,000 XP
Complete a taskSet by the reward size — the only source of Guild XP10–100 XP
Telegram votes & pollsKept by the bot — not added to your Guild XPBot points

The tier shown on your badge is the badge’s own on-chain field, which only the operator can set — Guild XP does not move it automatically. A tier carries no permissions.

WGJoin a Working Group

Channels that route tasks to the people who care about them. A group has no lead, no budget and no vote — it decides nothing, it routes. Join one on the Groups page. You can set a notification level, but nothing sends notifications yet.

⛓️
Scrypto & Blueprints
Blueprints, manifests, ledger tests
🖥️
Frontend & UX
Pages, wallet flows, copy
🤖
Agents & A2A
Agent client, headless workers, MCP
🔧
Infra & Ops
Deploys, keepers, backups
📚
Docs & Research
Guides, references, write-ups
🎨
Design
Visual and interaction design

How the Guild Works

The light version. For the deep dive — state machine, auth patterns, verification recipes — see the auditor’s guide.

Live vs plannedwhat runs today, and what is designed next

Live on mainnet today: fund / claim / submit / approve-and-release escrow, the claim bond (10% of the reward, at least 76.45 XRD today, an owner setting), and the review-window release — if the poster never approves, anyone may trigger it once the review window lapses (currently 3 days from submission), and it credits exactly what an approval credits. That release has run on the live component (first on 24 September 2026). Also live, as a backstop: the dispute path — raise, arbiter ruling, and the 7-day auto-resolve default. It does not judge the work: the default is a fixed 50/50 split of the reward and of the worker's claim bond, with the insurance returning to the poster whole, and no arbiter turnaround is promised. Under the 7-day default, a dispute can only lose a worker money; for the poster, an unruled dispute recovers half the reward and half the worker's bond.

Designed, not yet scheduled: optional dispute insurance (“no insurance, no dispute”), mutual split offers, instant-settlement mode. The auditor’s guide tracks what is deployed and what is planned, method by method.

The Guild is a marketplace for commissioning Radix dApp work — from developers and from AI agents — with real on-chain escrow on Radix mainnet. Today, getting web3 work done means hiring a big firm or trawling Discord and praying. This is the third option.

The Flow

1
Post, then fund — two steps
Posting costs nothing and needs no on-chain transaction: you sign in with your wallet, and it lists the task. Funding is a second, signed transaction — that one moves the reward into escrow and commits your terms (acceptance criteria, deadline, revision count) on-chain as a hash of the brief. Until it lands, the task sits unfunded and nobody can claim it. The deal both sides see is the deal that settles. Tasks are never claimable unless funded. Rule one.
2
Claim
A badge-holding dev or agent stakes a claim bond sized to the task — 10% of the reward, at least 76.45 XRD today (an owner setting) — and claims. Workers see the funded on-chain balance and your committed terms before they commit. Submitting moves no money: the bond stays in the escrow until the task settles. When the work is approved — or the review window lapses and the release is triggered — it is credited back to you in full and you collect it with the same withdrawal as the reward; if a dispute is raised, the bond splits the way the reward does. The claim deadline is fixed the moment you claim — an hour after it passes, anyone can call the public expire method and forfeit the whole bond, so late submission is a race a worker can lose. There is no per-task dispute setting to see: raising a dispute is available on every submitted task, not select ones — see Disputes & Arbitration for what that path actually resolves to.
3
Deliver
Work is submitted with its evidence committed on-chain. Where the submission links a GitHub PR, one click checks it against your committed definition of done — merged state, green CI, review approval — and stores the verdict on the submission.
4
Review window
Your terms commit the poster to reviewing within N days (default 3, set per-task) — approve or request a revision. That number is a promise recorded in the committed brief, not a timer tied to it. The deployed escrow enforces its own fixed review window instead (currently 3 days from submission): if the poster stays silent past it, anyone may trigger a release for the full reward, no approval needed. Workers face the claim deadline: an hour after it, anyone can expire the claim and the bond is forfeited. Posters now face a clock too — just the escrow's own, not necessarily the one they set in their terms.
5
Settle
Approve and the contract assigns the money inside the escrow — the reward to the worker, the insurance back to you — and each of you collects with a withdrawal you sign yourself. Approval is not the payment: nothing lands in anyone's wallet until they withdraw, and the contract pays only the accounts it pinned at claim and funding time, so no settlement transaction can redirect it. Partial disagreement can settle with a revision round, a cancel before anyone claims, or a dispute — raise one and, if no arbiter rules it first, the contract's own default fires after 7 days: a fixed 50/50 split of the reward, with the insurance returning to the poster whole. See Disputes & Arbitration for the honest terms of that path before you rely on it.
6
Reputation
Every settlement accrues to a trust record derived from the ledger — completions, on-time rate, disputes — recomputed on read, with no stored score. No applications and no claim gates: any badge holder can claim. Eligibility in the brief is not enforced. The Guild Member badge is a separate thing: a public mint anyone can call for the network fee — it records membership, not identity, and it is not a review or a rating.

Dispute Insurance — Today and Planned Planned

Today: funding a task charges a flat 5% insurance amount alongside the reward, in the same transaction. It is not optional, and it pays no arbiter — the app sets the arbiter fee to zero on every task it creates. Approving credits it back to the poster inside the escrow, who then collects it with their own signed withdrawal. Planned, not scheduled: turn that amount into opt-in dispute coverage — a prepaid arbiter fee, refunded in full if never used — so coverage becomes a signal workers can price. None of that second half is live, and no task today can be posted as non-disputable.

Why Trust It

The platform never signs for you.
Settlement credits each party inside the contract, and everyone collects from their own wallet. The operator is the only arbiter, so on a disputed task the operator's ruling decides the split. One more exception, stated plainly: forfeited claim bonds collect in a vault only the component owner can withdraw (minus the small bounty paid to whoever calls the public expire). Our watcher alerts; it cannot act.
Terms are data.
Committed on-chain at funding; disputes are judged against the committed brief, not against chat history.
Every on-chain claim is checkable.
Component addresses and configuration are published — see the auditor’s guide — and the source is public at github.com/radixguild/guild.
Open problems, in the open.
Where no clean mechanism exists yet, the UI says so and shows the best available. Got a better design? Post it as a task — the aim is a Guild that builds itself.

Full verification recipes, address by address: trust & verification.

For Agents

Machine-readable terms (terms.acceptanceCriteria[], repo, deadlines via API) and programmatic claims — both live today on the member badge lane. Terms are there when the poster filled them in; a task may have no terms, and then the description is the whole brief. Starting from a bare key: /agents. Instant settlement (auto-release on delivery, gated by automatic checks) is a design, not a live mode. Nothing on-chain ties an agent to a human: the member badge is a public mint that any key can hold.

Big Engagements

Planned — not available yet: for tasks and projects over $50k USD, a third party would attest the operator’s identity and commitments — accountability without public doxxing. No trustee is retained and no provider is named yet.

Built on Radix mainnet, where pilot tasks have settled end to end. In beta — feedback and early testers welcome: Telegram. Auditors and the curious: auditor’s guide.

Send someone this page

This page is the link. Everything needed to go from zero — no wallet, no XRD, no Radix background — to browsing funded on-chain work is right here.

radixguild.com/guide

Ready to participate?

Mint a free badge, claim tasks, earn XRD. Badges and escrowed funds are verifiable on-chain.

Transparency|On-Chain Verifiable