Tokenization Overview

Complete Setup and Installation first.

This section is the conceptual home for AMP and tokenization. It explains what the feature set is for, how the pieces fit together, and where each SDK workflow belongs.

What tokenization means here

In this system, tokenization means issuing and governing native Liquid assets that represent something operational or financial, such as:

• securities
• stablecoins
• loyalty units
• internal settlement assets

These are native Liquid assets, not smart contracts deployed to a separate VM.

Why AMP exists

AMP wallets are the Liquid wallet type designed for tokenization workflows. They add:

• 2-of-2 user and server co-signing
• confidential Liquid settlement
• transfer restrictions
• operational controls around who can hold or move issued assets

AMP workflow map

The tokenization workflow usually follows this order:

1. create an AMP wallet
2. issue the asset
3. configure restrictions and burn permissions
4. transfer the asset between wallets or external Liquid addresses
5. optionally reissue or burn supply later

What lives in this section

• Asset Issuance: create the first supply and understand reissuance
• Asset Management: restrictions, whitelists, and burns
• Asset Transfers: move assets between AMP wallets and external destinations

Shared concepts vs AMP-specific work

Some ideas are shared across the whole platform, such as:

• Transaction Lifecycle
• Policy Engine

This section focuses only on the AMP- and tokenization-specific parts of the workflow, then links back to those shared concepts where needed.