Builders Hub Application

Builders Hub

Create, control, and deploy XRPL systems without hiding authority, risks, or transaction flow.

Follow the six practical lessons below. Inspect public examples, work through decisions and check your understanding. No wallet connection or transactions are required.

Start with a project, finish with evidence

You do not need to code, own XRP or connect a wallet to learn here. Bring a notebook. If public addresses, signing keys and wallet custody are unfamiliar, begin with Wallet Basics and Safety. These six lessons teach you to explain and inspect an XRPL project before implementing it.

Follow a fictional neighborhood club from workshop credits to a collectible and a booking flow. Each lesson contains definitions, a guided paper worksheet, a worked decision, common mistakes and questions with explanations. Read the lesson, attempt the worksheet before checking the answer, and keep the resulting page of notes. There is no account, score certificate or saved learning profile.

  1. Create a token: write the purpose, exact asset identity, redemption promise and supply questions.
  2. NFT basics: separate token identity, ownership, media and rights.
  3. Trust lines: distinguish balance, limit, controls and reserves.
  4. Issuer control: map signing authority, recovery and irreversible choices.
  5. Xaman flows: design truthful signing and verification states.
  6. Project launch: combine the outputs into a release packet and failure/recovery plan.

Three environments that must not be confused

These pages are read-only learning material with fictional examples and local quiz feedback. Testnet is a separate ledger for later implementation rehearsal; its test assets do not pay Mainnet bills. Mainnet carries real assets and consequences. Devnet can include experimental changes; success there does not establish Mainnet availability. Do not reuse real secrets in experiments. Check official network guidance and the actual target amendment status before implementation.

Know the course boundary

This is a thorough foundation for the six topics, not an exhaustive SDK course or a one-click token launch tool. It does not implement custody, trading, smart contracts, legal rights, production authentication or payment processing. Follow the official references for the next technical step, and keep unresolved decisions visible. Finishing the quizzes is not security certification.

01

Create

Learn the primitives before launching anything.

Issued Assets

Currency code, issuer, supply, trustlines, and controls.

NFTs

Flags, URI, taxon, offers, transfer fees, and lifecycle.

Account Design

Separate issuer, operator, treasury, and public accounts.

Create a tokenStart with the asset promise, the issuer, and who can change the rules. A ticker is only the label.Start lesson →NFT basicsAn NFT has an on-ledger identity and transfer rules. Its artwork and promises need their own checks.Start lesson →
02

Control

Know what authority stays active after launch.

Freeze

Whether balances can be frozen.

Authorization

Whether holders need approval.

Regular Keys

How signing authority rotates.

Multisigning

How shared authority protects accounts.

Blackholing

What permanent loss of control does and doesn’t prove.

Disclosure

What users need to know.

Trust linesA trust line records a relationship between accounts for one currency. “Trust” here does not mean the issuer has been approved as safe.Start lesson →Issuer controlGood disclosure describes the authority that exists today, not just the project’s intentions.Start lesson →
03

Deploy

Connect ledger actions to an interface people can use.

Build transaction
→
Show signing request
→
Submit
→
Confirm validation
→
Explain result
Xaman flowsOpening a wallet, signing a request and completing a ledger action are different events. Your interface needs to tell the truth at each step.Start lesson →Project launchA launch is an operating system of people, permissions and failure handling. Make the evidence as clear as the interface.Start lesson →
04

Builder standard

A serious XRPL product should be understandable before it asks for a signature.

  • Show the exact asset identity.
  • Explain every permission and account setting.
  • Handle failed, queued, expired, and validated transactions correctly.
  • Never claim success before validation.
  • Give users transaction hashes and explorer paths.
  • Separate product revenue from XRPL network fees.
✓

Did it click?

Answer these without guessing.

Should a product claim success before validation?

Is blackholing proof a project is safe?

What should users see before signing?

→

Keep moving

Open the next application and keep building the full picture.

DefinitionsMaster the primitives.Open Definitions →WalletsUnderstand account authority.Open Wallets →UsageUnderstand transaction execution.Open Usage →