Spin-off

Create the spin-off asset

POST /api/v2/tokens deploys the new instrument with its own type, compliance modules, and roles. Model the spun-off business with the asset class that fits it (equity, fund, or another class); the distribution mechanics below are the same for all classes. The token lifecycle reference documents the create call and its per-class fields. Leave the new asset paused until the distribution completes if you want no secondary transfers before all holders are served.

Verify holder eligibility on the new asset

Every recipient must pass the new asset's compliance checks at mint time. Before you distribute, confirm the parent's holders carry the claims the new asset requires; where the new asset reuses the parent's compliance configuration this is already given. Handle the exceptions (holders who fail the new asset's rules) as separate cases before your mint run, not during it.

Snapshot the parent's holders

Read the parent's full holder set at the record date, walking every page of the result.

curl "https://your-platform.example.com/api/v2/tokens/0x9459D52E60edBD3178f00F9055f6C117a21b4220/historical-balances/holders-at-block?timepoint=1772323200&limit=200" \
  -H "X-Api-Key: sm_dalp_test_xxxxxxxxxxxxxxxx"

Compute each allocation as floor(parent balance x distribution ratio). Record the rounding remainders your policy leaves behind, because the verification step reconciles against them.

Batch mint the new asset to parent holders

Mint on the new asset's address, in groups of up to 100 recipients. Give each request its own Idempotency-Key so a timed-out call retries safely instead of minting twice.

curl -X POST "https://your-platform.example.com/api/v2/tokens/0x5bE39c3D8beD22B6ff8Eb0BEEEfD32Fa50e14D63/mints" \
  -H "X-Api-Key: sm_dalp_test_xxxxxxxxxxxxxxxx" \
  -H "Idempotency-Key: spinoff-nwlog-2026-batch-001" \
  -H "Content-Type: application/json" \
  -d '{
    "recipients": [
      "0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb",
      "0x8ba1f109551bD432803012645Ac136ddd64DBA72"
    ],
    "amounts": [
      "500000000000000000000",
      "125000000000000000000"
    ]
  }'

A batch fails whole if one recipient fails compliance, so the eligibility pass in the previous step is what keeps the run smooth. Remove a failing holder, rerun the batch under a fresh Idempotency-Key, and resolve that holder separately.

Verify and open the new asset

Confirm every transaction, check the new asset's total supply against your allocation table, and spot-check holder balances. If you created the asset paused, unpause it with DELETE /api/v2/tokens/{tokenAddress}/pause-state once the distribution reconciles.