コンテンツにスキップ

このページのソース

このページの主張はすべて固定されたリビジョンに紐づいています。検証元のソースを正確に確認できます。

atomicals-electrumx-1.5.2.0

Atomicals ElectrumX

リビジョン v1.5.2.0 (2025-03-27)

固定パスを開く: splitAndInflation

Version-sensitive ARC-20 and Atomicals validation behavior used as the pinned reference baseline.

atomicals-js-cli

Atomicals JavaScript CLI

リビジョン 1333565efbfe

固定パスを開く: commandIndex

Reference command surface used for the documented CLI inventory and the visual asset provenance.

Split and combine ARC-20

Raw

Reshape your lots deliberately, and know when combining makes future transfers harder.

Protocol behavior Verified 2026-08-31 Metadata & Sources

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

このコンテンツはまだ日本語訳がありません。

  • Supported networks: mainnet.
  • Status: protocol behavior. Custom coloring is activation gated.
  • Both operations are allocation events. Model them before building.

Combining is ordinary allocation: several coloured inputs of the same token, one output large enough to take the whole sum.

  1. List the lots to combine and add their values.
  2. Create one output with exactly that satoshi value.
  3. Fund the fee from a cardinal input, with a cardinal change output.
  4. Model it. The burn figure must be zero.
  5. 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.

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 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.

  • 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.

Confirm, wait for indexing, and read your new lot structure. Record the new outpoints.

Split and combine and allocation.