About Radix Guild

Radix Guild is experimental beta software provided as-is. Use at your own risk.

The platform facilitates community governance and task coordination on the Radix network. It does not provide financial advice, investment services, or guarantees of any kind.

Task escrow is on-chain. Reward and insurance XRD are deposited directly into a Scrypto smart contract vault, and no admin wallet can withdraw them. One exception, stated plainly: a worker's claim bond — 10% of the reward, never less than 76.45 XRD, capped on-chain — is forfeited if the claim expires — a small bounty pays whoever calls the public expire method, and the rest moves to a forfeited-bonds vault which only the operator badge can drain. Funding is verified on-chain before tasks become claimable. The escrow component is deployed on Radix mainnet and verifiable on the Radix Dashboard.

The admin badge and platform operations are managed by bigdev. Handover is gated on the Permanent RAC once elected under GP-ELECT-1 (not yet drafted) — no date is committed. This is an interim arrangement, not permanent centralisation.

The guild stores: Radix wallet addresses, task data, submissions, and XP in a PostgreSQL database; the Telegram bot keeps its own SQLite database of Telegram user IDs, registrations, and off-chain vote records. Both run on a private VPS.

On-chain data (badges, votes, transactions) is public by nature of the Radix ledger. The guild does not control or delete on-chain data.

No personal information (name, email, phone) is collected or required. Your identity is your Radix wallet address and optional Telegram username.

No analytics, no trackers, no third-party data services. The only cookie is a session cookie set when you sign in with your wallet — it holds a signed session token, is httpOnly, and is cleared when you sign out.

This is experimental software interacting with blockchain technology. Smart contract risk, network risk, and operational risk exist.

Task escrow uses a Scrypto smart contract vault on Radix mainnet. Reward and insurance XRD are locked in the component and cannot be withdrawn by any individual; forfeited claim bonds are the one balance the operator badge can drain. Never send XRD to a wallet claiming to be the guild treasury, and never transfer XRD to the escrow address directly — funding only happens through the Fund button, which builds a transaction your wallet shows you in full before you sign.

Dispute resolution is live. If a poster and worker disagree after submission, either can raise a dispute; a human arbiter can rule it for no fee — arbiter_fee_pct is 0 on every task this app funds, so insurance funds no arbiter — and if nobody does, the contract applies its own default after 72 hours: a plain 50/50 split of the reward, with the poster's insurance returning to them in full. We promise no turnaround time for a human ruling — there is no public SLA, only that 72-hour backstop — and our pre-deploy check now fails a release that compiles this surface off, the mirror of what it used to guard. Requesting a revision instead of disputing is a normal review step; it is a record we keep, not a chain event, so treat silence as a reason to check in rather than proof nothing was asked. Settlement pays only the accounts pinned when the task was created and claimed, so nobody else can end up holding the money. There is still no timer on review: the deployed escrow has no review-window auto-release, so if a poster goes quiet after a worker submits, the funds stay locked until someone acts — raising a dispute is the worker's one on-chain way out, and it recovers half the reward, not all of it. See Disputes & Arbitration for the full terms and the mainnet settlement we ran before turning this on.

XRD value fluctuates. Task rewards denominated in XRD may change in fiat value between creation and payment.

The guild is not a registered entity, financial institution, or investment vehicle. Participation is voluntary and at your own risk.