UTXO Teleport

What Is a UTXO Teleport?

A UTXO teleport is a transfer of Bitcoin UTXO ownership that occurs entirely off-chain through the statechain protocol. Rather than broadcasting a transaction that moves coins from one address to another, a UTXO teleport reassigns who holds the signing keys that control an existing on-chain output. The coins never move on the blockchain: instead, the authority to spend them passes from one party to the next through a cryptographic key rotation ceremony.

The "teleport" metaphor captures this distinction precisely. In a standard Bitcoin transaction, coins move visibly from input to output, consuming one UTXO and creating another. In a UTXO teleport, ownership changes hands as if the UTXO were lifted from one person's wallet and placed into another's, with no trace on the blockchain that anything occurred. The on-chain UTXO remains at the same address, with the same value, in the same position in the UTXO set.

This mechanism was first described as part of the statechain concept proposed by Ruben Somsen at Scaling Bitcoin 2018 in Tokyo. The idea was to transfer full UTXOs off-chain using a semi-trusted facilitator, enabling Bitcoin to scale beyond its on-chain throughput without altering the consensus rules. Mercury Layer, developed by CommerceBlock, is the primary implementation of this transfer model, while protocols like Spark extend it with partial-amount transfers and distributed operator sets.

How It Works

A UTXO teleport relies on three participants: the current owner (sender), the new owner (receiver), and the statechain entity (SE). The SE holds one share of a 2-of-2 key arrangement with the current owner. Neither party alone can spend the UTXO: a valid signature requires both shares.

Step-by-Step Transfer

1. Alice currently owns a statechain UTXO. She holds one private key share (the "transitory key"), and the SE holds the other. Together, their shares correspond to the aggregate public key that controls the on-chain UTXO.
2. Alice signals to the SE that she wants to transfer ownership to Bob. She sends her transitory key to Bob through a secure channel.
3. The SE and Bob perform a key resharing operation. The SE generates a new key share for Bob and mathematically adjusts its own share so that the combined public key remains identical. The on-chain address does not change.
4. Bob creates a new backup transaction with a shorter nLockTime than Alice's backup, and the SE co-signs it. This ensures Bob can claim funds on-chain before any previous owner.
5. The SE deletes its old key share that corresponded to Alice. Alice's transitory key is now orphaned: it cannot produce a valid signature without the SE's matching (now destroyed) share.

# UTXO teleport: ownership changes, UTXO stays put

Before transfer:
  On-chain UTXO → controlled by (Alice_key + SE_share_v1)

Key resharing:
  SE generates new share for Bob
  SE adjusts its own share to preserve aggregate pubkey
  SE deletes old share (SE_share_v1)

After transfer:
  On-chain UTXO → controlled by (Bob_key + SE_share_v2)
  Same address. Same UTXO. Different owner.

Why the UTXO Appears Untouched

The key insight is that the aggregate public key never changes. When the SE reshares its key with a new owner, the mathematics of the key-splitting scheme ensure that both the old pair (Alice + SE_v1) and the new pair (Bob + SE_v2) correspond to the same public key. A blockchain explorer shows no new transactions, no new outputs, and no changes to the UTXO set. The transfer is invisible to anyone observing the blockchain.

This is fundamentally different from how Lightning channels or CoinJoin transactions work. Lightning requires an on-chain funding transaction to open a channel and a closing transaction to settle. CoinJoin creates a visible on-chain transaction with multiple inputs and outputs. A UTXO teleport leaves zero on-chain footprint between deposit and final withdrawal.

Decrementing Timelocks

Each teleport creates a new backup transaction with a shorter timelock than the previous one. This ensures that the current owner can always claim funds on-chain before any previous owner:

# Backup transaction timelocks across teleports
Owner 1 (Alice):  nLockTime = block 900,000
Owner 2 (Bob):    nLockTime = block 899,000
Owner 3 (Carol):  nLockTime = block 898,000

# Carol's backup becomes valid first, so she can
# broadcast before Alice or Bob if the SE disappears

This decrementing scheme limits the number of teleports a single UTXO can undergo before it must be settled on-chain and re-deposited into a fresh statechain.

UTXO Teleport vs. On-Chain Transaction

For a detailed analysis of how statechain transfers compare to other scaling approaches, see the statechains scaling deep dive.

Why It Matters

UTXO teleports address two of Bitcoin's most fundamental constraints: limited on-chain throughput and high transaction fees during periods of congestion. By moving ownership changes off-chain, a single on-chain UTXO can change hands dozens of times without consuming any block space.

This has practical implications for how Bitcoin can scale. During fee spikes, on-chain transactions can cost tens of dollars. A UTXO teleport costs nothing. The tradeoff is the semi-trusted relationship with the statechain entity, but for many use cases (transferring fixed-denomination amounts, privacy-preserving transfers, rapid settlement) this tradeoff is acceptable.

Protocols like Spark build on the UTXO teleport concept to overcome its primary limitation: the fixed-denomination constraint. Where a traditional statechain can only teleport entire UTXOs, Spark uses a leaves architecture that enables arbitrary-amount transfers while retaining the core key-rotation mechanism. Spark also distributes the SE role across multiple operators using FROST threshold signatures, reducing the trust assumption from "trust one server" to "trust that at least one operator is honest."

Use Cases

Zero-Fee Bitcoin Transfers

The most straightforward use case: transferring Bitcoin without paying any on-chain fees. During periods of high network congestion, UTXO teleports provide an alternative transfer path that is completely unaffected by the fee market. A 0.1 BTC transfer costs the same as a 10 BTC transfer: nothing.

Privacy-Enhanced Transfers

Because teleports leave no blockchain footprint, chain analysis firms cannot track ownership changes that occur via statechain transfers. Mercury Layer takes this further with blind signing: the SE co-signs transfers without learning the transaction IDs, public keys, or amounts involved. Even the facilitator cannot reconstruct the transfer history.

Lightning Channel Transfers

Entire Lightning channel funding UTXOs can be teleported to new owners without closing and reopening the channel on-chain. This avoids the two on-chain transactions (close + open) that would normally be required, saving fees and keeping channel liquidity intact. For more on Lightning channel mechanics, see the Lightning channel glossary entry.

Rapid Settlement for Fixed Denominations

For use cases where standardized denominations are acceptable (such as trading fixed-value "statecoins"), UTXO teleports provide instant settlement. A 0.01 BTC statecoin can change hands repeatedly throughout the day with each transfer completing in seconds, matching the speed of centralized exchanges without surrendering custody.

Risks and Considerations

Statechain Entity Trust

The SE must honestly delete its old key share after each teleport. If it retains the old share and colludes with a previous owner, the two can jointly produce a valid signature to steal the current owner's funds. This key deletion cannot be cryptographically proven: users must trust the SE's infrastructure and operational practices. Distributing the SE across multiple operators using FROST threshold signatures mitigates this risk but does not eliminate it entirely.

Fixed Denomination Constraint

Traditional UTXO teleports transfer entire UTXOs. If you deposit 0.5 BTC into a statechain, you can only teleport exactly 0.5 BTC. You cannot split it into smaller amounts or combine multiple statechain UTXOs into one. This limits practical use for everyday payments where arbitrary amounts are needed. Protocols like Spark and Ark address this with more flexible off-chain structures including VTXOs.

Transfer Count Limits

Each teleport decrements the backup transaction's timelock, reducing the remaining window before the UTXO must be settled on-chain. After enough transfers, the timelock approaches the current block height and the statechain expires. The original statechain design proposed using eltoo (LN-Symmetry) to remove this limitation, but eltoo requires the SIGHASH_ANYPREVOUT soft fork, which has not been activated on Bitcoin.

Entity Availability

If the SE goes offline, no teleports can occur. Users can still withdraw on-chain using their pre-signed backup transaction, but they must wait for the timelock to expire. During this waiting period, funds are effectively frozen: they cannot be transferred off-chain or spent on-chain until the timelock matures.

No Partial Recovery

Unlike payment channels where each party holds a commitment to their share of the balance, a UTXO teleport is all-or-nothing. The current owner either controls the entire UTXO or does not. There is no mechanism for splitting ownership if a dispute arises.

This glossary entry is for informational purposes only and does not constitute financial or investment advice. Always do your own research before using any protocol or technology.