Split and combine ARC-20
Reshape your lots deliberately, and know when combining makes future transfers harder.
Protocol behavior Verified 2026-08-31
Describes the Atomicals protocol itself at the pinned reference revision. It does not promise that any product exposes it.
- Page ID
-
guides/split-and-combine-arc20 - Normative authority
- Executed source code at a pinned revision
- Networks
- mainnet
- Documentation version
- 2026.08
- Activation boundary
- Custom coloring with the z operation is activation gated.
- Audience
- holder, developer
- Owner
- bitcoin-universe-docs
- Sources
-
- Atomicals ElectrumX
at
v1.5.2.0 - Atomicals JavaScript CLI
at
1333565efbfe
- Atomicals ElectrumX
at
Это содержимое пока не доступно на вашем языке.
Before you start
Section titled “Before you start”- Supported networks: mainnet.
- Status: protocol behavior. Custom coloring is activation gated.
- Both operations are allocation events. Model them before building.
Combining
Section titled “Combining”Combining is ordinary allocation: several coloured inputs of the same token, one output large enough to take the whole sum.
- List the lots to combine and add their values.
- Create one output with exactly that satoshi value.
- Fund the fee from a cardinal input, with a cardinal change output.
- Model it. The burn figure must be zero.
- Sign and broadcast.
Combine only lots of the same token. Mixing tokens creates a multi token transaction subject to the output zero fallback.
Think ahead. One large lot makes every future partial transfer depend on getting the change output size exactly right. Several right-sized lots are easier to move safely.
Splitting
Section titled “Splitting”Split is the y operation. It skips a total amount of value before colouring begins, which is
what lets a builder separate several tokens sharing one input.
yarn cli split <locationId>The payload keys the skip amount by the compact Atomical ID it applies to. That is an implementation specific structure. Build it with a compatible library, never by hand from a user interface field.
Custom coloring
Section titled “Custom coloring”Custom coloring is the z operation and is activation gated. Where active, it attaches outputs
even when the remaining value does not cover them fully, and the last attached output receives
what is left rather than nothing.
yarn cli custom-color <locationId>Do not assume it is available. Read the active rule set for your network and height.
Check before signing
Section titled “Check before signing”- Every coloured input is a lot you intend to spend.
- Output values in satoshis sum the way you expect.
- The burn figure is zero.
- The fee comes from a cardinal input.
- You modelled again after adding fee inputs and change.
After broadcast
Section titled “After broadcast”Confirm, wait for indexing, and read your new lot structure. Record the new outpoints.