ARC-20 allocation visualizer

ARC-20 allocation visualizer

Local only. Never signs or broadcasts

Implementation

Start from a known case Blank Clean split into two outputsOversized next output burns the remainderWhole lot into one outputFirst output larger than the whole lotOutputs run out before the value doesUnspendable outputs are skipped, not fundedCombining two lots of the same tokenTwo different tokens take sequential output slotsA non-clean slot triggers the output zero fallbackA remainder smaller than the change output burnsA change output larger than the remainder burns itCustom coloring assigns a partial value to the last outputExact single output, exact-cover eraPartially coloured output, current eraEleven inputs consolidated into one small outputOne satoshi short destroys the whole balanceOne unit over the output value burns that unitTwo lots merged into one output, one unit as feeA transaction carrying no tokensPaying the fee out of coloured value burns itNo output able to take colourSplit skips a satoshi amount before colouringCustom colouring clamps an over-requestCustom colouring burns what the payload does not place Every preset is an executed conformance vector, so the result here matches the tests.

Input ordering FIFO, by first input index then Atomical ID Legacy, by Atomical ID

Custom coloring Off, normal allocation On, activation gated Custom coloring is activation gated. Do not assume it is available on your network.

Coloured inputs

Add input

Outputs, in order

Add output

Copy as a vector

Explanatory only. It models normal allocation from the pinned reference revision. Validate a concrete transaction against the validator revision you target before broadcasting.

How to use it

1. Start from a preset, or enter your own coloured inputs.
2. Enter the outputs in the exact order your transaction will have them, in satoshis.
3. Read the burn figure. It should be zero.
4. Add the fee inputs and the cardinal change output, then read it again.
5. Only build the transaction once the figure is still zero.

Step four is where wallet-added change silently changes the result.

This runs the same engine as the tests

The presets are the executed conformance vectors, and the computation is conformance/allocation.mjs, the same module tests/conformance-allocation.test.mjs calls. The tool and the tests cannot disagree.

What it models

Modelled	Not modelled
Normal allocation, exactly as the pinned builder performs it	Live chain state
The output zero fallback when a plan is not clean	Whether an output is actually coloured today
Unspendable outputs, skipped without consuming value	Whether your wallet will reorder outputs
Activation gated custom coloring	Whether custom coloring is active on your network
The no-inflation rule	Anything on the non-fungible branch

Copy as a vector

The copy control produces a JSON object in the same shape as the committed vector set. If you find a case this documentation should cover, that object is what to attach to an issue.

See conformance vectors.