UTXO Safety Planner

Raw

Classify asset-bearing UTXOs, see the risks, and generate deterministic candidate plans before you construct a transaction.

Protocol behavior Verified 2026-09-02 Metadata & Sources

Describes the Atomicals protocol itself at the pinned reference revision. It does not promise that any product exposes it.

Page ID

tools/utxo-safety

Normative authority

Executed source code at a pinned revision

Networks

mainnet, testnet, signet, regtest

Documentation version

2026.08

Audience

holder, developer, everyone

Owner

bitcoin-universe-docs

Sources

Atomicals ElectrumX at v1.5.2.0 the burn and allocation behaviour every warning cites

Known limitations

Classification is only as good as the assignment data you import. Without indexer data the planner says unknown and never claims safety.
Plans are unsigned intents. The planner never signs, never broadcasts, and never performs an address lookup without an explicit action at a chosen endpoint.

Esta página aún no está disponible en tu idioma.

The planner classifies UTXOs and generates candidate plans when JavaScript runs. Without it, read the safety rules this tool cites: every warning links to the rule page that explains the risk and the safe alternative.

Treat everything you paste here as sensitive local data. It stays in this page's memory, is never stored, never sent anywhere, and disappears when you close the tab.

1. Import UTXOs

Paste UTXO JSON, Bitcoin Core listunspent output, or the sample.

2. Choose an objective

Objective ARC-20 amount or BTC amount in sats Fee rate (sat/vB)

Classification

Every imported output with its classification and evidence
Output	Satoshis	Class	Confidence	Evidence

Candidate plans

Plans are compared on several axes at once. There is no single score: read the warnings and pick with your own eyes.

Export

The planner never signs and never broadcasts. When fields for a structurally valid unsigned PSBT are missing, it exports an explicit transaction intent instead and says what is missing.

What the planner checks

Every candidate plan is examined for the classic loss patterns: accidental asset burns, mixed token inputs, unknown assignment state, insufficient asset change, unsafe output ordering, dust, fees that cannot cover the virtual size, unconfirmed input chains, and reused change addresses. Each warning links to the rule page and the pinned source revision behind it.

Unknown stays unknown: an output with no assignment data is classified as unknown with no confidence, and the planner refuses to call it safe.

Comparing plans

Plans are compared on asset safety, fee, input count, and privacy impact side by side. There is no single score, because collapsing those axes into a number hides exactly the trade-offs you need to see.

Exports

Export the plan as JSON, as a Protocol Lab scenario to replay its effects, or as a CLI command sequence to run against your own setup. When fields for a structurally valid unsigned PSBT are missing, the planner exports an explicit transaction intent and names what is missing instead of fabricating values.