Pular para o conteúdo

Choose your path

Raw

Four short routes through this documentation, one for each thing people actually come here to do.

Editorial Verified 2026-08-31 Metadata & Sources

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

Este conteúdo não está disponível em sua língua ainda.

Pick the row that matches what you are doing today. Every route is short on purpose.

You own units, an NFT, or a Realm, and you want to keep them.

  1. Learn the model: what is ARC-20 and what are Atomicals.
  2. Run the checks in safety fundamentals.
  3. Pick a wallet that understands coloured outputs: choose a wallet.
  4. Separate fee money from coloured money: protect coloured outputs.
  5. Before any move, model it: allocation visualizer.
  6. After broadcast, confirm the result: verify a transaction.

You are launching a token, a collection, or a name.

  1. Decide the issuance shape: direct, fixed DFT, or perpetual DFT.
  2. Understand what a ticker actually reserves: tickers and candidates.
  3. Budget the work: Bitwork and the Bitwork estimator.
  4. Build the command: CLI reference and the command builder.
  5. For collections: Containers then DMINT.
  6. For names: claim a Realm and Unicode and IDNA.

You are integrating an API, a wallet, or an indexer.

  1. Read the source of truth model first. It decides how much you can trust any response.
  2. Take the contracts: OpenAPI and schemas.
  3. Generate a client: TypeScript client.
  4. Handle the hard parts: cursors, reorgs, readiness.
  5. Prove your builder: conformance vectors.
  6. Wire the wallet: wallet integration.

You run or depend on the indexes.

  1. Generations, checkpoints, and rollback.
  2. Readiness against configured and what each state means to a caller.
  3. Unavailable index against empty balance, the difference that causes support tickets.
  4. Versioning and deprecation so consumers are warned before behavior changes.