Skip to main content

UTXO assets and Syscoin Platform Tokens

Syscoin Platform Tokens (SPTs) are assets represented in the Syscoin UTXO model. An asset-bearing output has a spending condition, an asset identifier, and an amount. Spending consumes specific outputs and creates new outputs. Core checks asset conservation for transfers and applies separate rules to protocol mint and burn operations. This is the model described in the Syscoin whitepaper, with a simplified representation since Core 5.0. Syscoin 4 whitepaper · Asset output representation · Core asset validation

Why put an asset in an output?​

Imagine a workshop owns an output holding 10 units of an SPT. It spends that output, sends 7 units to a supplier, and sends 3 back to itself as change. Core checks the asset ID and accounts for all 10 units across the new outputs. The supplier can point to the exact output it received. A separate workshop spending its own asset outputs can pay another supplier independently. Core accounts for the native SYS fee separately from the token amounts. Native fee and asset accounting · Allocation conservation

  • Explicit ownership and dependencies. To verify a transfer, a node follows the inputs to the outputs they spend and checks the spending conditions. It can identify conflicting claims to an output before either is included in a block.
  • Independent transfers. Transactions using disjoint inputs do not need to serialize through a shared account nonce. A recipient can see the exact input dependencies and use that graph for confirmation policy.
  • A conventional payment path. A straightforward transfer uses the UTXO chain and its script rules. Applications that need richer state and composability can use NEVM contracts. A bridge between those representations must establish the asset, amount, destination, and authorized transition.
  • An early payment signal. Z-DAG was built for Syscoin’s asset transfers. It checks eligible transfers and their unconfirmed dependencies for conflicts and warnings, giving the recipient evidence to use before a block arrives. Z-DAG and SPT payments

SYS is the native currency. SYSX is the UTXO-side asset representation used by the SYS route between Core and NEVM. A native SYS payment and an SPT allocation transfer have different transaction formats and policies. SYS bridge route · UTXO integration reference

What Core 5.x supports​

Core 5.0 retired the 4.x RPCs for creating and managing assets on the UTXO side. The newer model delegates asset issuance and management to NEVM and uses supported bridge paths to bring eligible assets into the UTXO representation. Core still validates allocation transfers. External tooling can construct supported transactions. Check which asset and route your deployment actually supports. The public SYS bridge describes the native SYS route through SYSX. Core 5.0 changes · SDK reference