Choose your path
Four short routes through this documentation, one for each thing people actually come here to do.
Editorial Verified 2026-08-31
Navigation or explanatory writing with no source-sensitive claim of its own.
- Page ID
-
start/choose-your-path - Normative authority
- No normative source. Navigation only.
- Networks
- mainnet
- Documentation version
- 2026.08
- Audience
- everyone
- Owner
- bitcoin-universe-docs
Ce contenu n’est pas encore disponible dans votre langue.
Pick the row that matches what you are doing today. Every route is short on purpose.
Holder
Section titled “Holder”You own units, an NFT, or a Realm, and you want to keep them.
- Learn the model: what is ARC-20 and what are Atomicals.
- Run the checks in safety fundamentals.
- Pick a wallet that understands coloured outputs: choose a wallet.
- Separate fee money from coloured money: protect coloured outputs.
- Before any move, model it: allocation visualizer.
- After broadcast, confirm the result: verify a transaction.
Creator
Section titled “Creator”You are launching a token, a collection, or a name.
- Decide the issuance shape: direct, fixed DFT, or perpetual DFT.
- Understand what a ticker actually reserves: tickers and candidates.
- Budget the work: Bitwork and the Bitwork estimator.
- Build the command: CLI reference and the command builder.
- For collections: Containers then DMINT.
- For names: claim a Realm and Unicode and IDNA.
Developer
Section titled “Developer”You are integrating an API, a wallet, or an indexer.
- Read the source of truth model first. It decides how much you can trust any response.
- Take the contracts: OpenAPI and schemas.
- Generate a client: TypeScript client.
- Handle the hard parts: cursors, reorgs, readiness.
- Prove your builder: conformance vectors.
- Wire the wallet: wallet integration.
Operator
Section titled “Operator”You run or depend on the indexes.
- Generations, checkpoints, and rollback.
- Readiness against configured and what each state means to a caller.
- Unavailable index against empty balance, the difference that causes support tickets.
- Versioning and deprecation so consumers are warned before behavior changes.