Skip to main content
Using the Wallet SDK? VTXO renewal is handled automatically. See VTXO Management for details.
VTXOs are not permanent. Each one is created inside a batch output that has a defined expiration window. Before that window closes, the VTXO must be renewed or settled. This lifecycle is a deliberate design choice: expiration allows the operator to recycle capital efficiently and keeps the system’s onchain footprint compact.

Batch Expiry

Every batch output has a built-in expiration. When a batch expires, the operator gains the ability to sweep the underlying Bitcoin through the batch output’s sweep path. If a user’s VTXO is still active when the batch expires and they have not renewed it, the operator can claim those funds. In practice, the operator typically issues redeemable Arkade Notes as a recovery mechanism, but the user loses the ability to enforce their claim unilaterally onchain. The solution is straightforward: participate in a batch swap before expiry. This creates a fresh VTXO in a new batch with a reset expiry timer, while inheriting full Bitcoin finality.

Liveness Requirements

The expiry mechanism creates liveness requirements for both operators and users.

Operator Liveness

Arkade uses a client-server architecture where operator uptime directly affects functionality. When the operator goes offline, users cannot initiate new transactions until the operator returns. However, existing funds remain completely safe through presigned exit transactions. Users retain the ability to exit unilaterally at any time, regardless of operator status. Operators face strong economic incentives to maintain availability: downtime means lost fee revenue and user attrition.

User Liveness

Users must take action during the expiry window to maintain unilateral exit rights. They do this by participating in a batch swap, which renews their VTXOs with fresh expiry timestamps. Expired VTXOs get swept by the operator. While users may recover their funds through Arkade Notes, they lose the ability to enforce ownership claims onchain. This creates a natural incentive to remain active and settle periodically.
In practice, the SDK and wallet software handle renewal automatically in the background. Users of well-built applications rarely need to think about expiry directly.

Delegation

Not every user can be online at the right moment. Arkade’s intent system enables users to delegate VTXO renewal to a third party without giving up custody.

How Delegation Works

Delegation is implemented at the VTXO level by embedding an additional spending path into the output script:
  • User + Operator (collaborative path). Standard cooperative spending.
  • User + timelock (exit path). Unilateral fallback.
  • User + Delegate + Operator (delegation path). Requires all three parties to sign.
The user creates a presigned intent specifying exactly which VTXOs to renew and what outputs to produce. The delegate can submit this intent during a batch swap on the user’s behalf, but cannot alter the terms or access funds beyond what was presigned.

Delegation Options

Wallet Providers

Integrate automatic renewal into the application experience transparently.

Third-party Services

Professional entities offering renewal with reliability guarantees.

Self-hosted

Run your own delegate/watchtower on a laptop, home node, or server.

Guarantees

Delegation preserves self-custody throughout:
  • User retains control. All delegation uses presigned intents. Funds remain self-custodial with unilateral exit always possible.
  • Pre-committed inputs and outputs. Intents define exact inputs and outputs. Delegates cannot alter them or access funds beyond what was signed.
  • Strict timing constraints. Intents include time windows that prevent delegates from submitting early to collect fees prematurely.
Find the full intent delegation workflow in the Server & API section.

Previous: Settlement & Finality

Batch swaps, commitment transactions, and intents.

Next: Security & Trust Model

Unilateral exits, the Arkade Signer, and risk analysis.