	Account Type	Key Features
Mint Accounts	Solana Account	Represents a unique mint and optionally can store token-metadata. Functionally equivalent to SPL mints. Rent-exemption cost covered by the Light Token Program
Token Accounts	Solana account	Stores token balances of mints (SPL, Token-2022, or Light) Rent-exemption cost covered by the Light Token Program

Rent Config by Light Token Program

A rent sponsor PDA by Light Protocol pays the rent-exemption cost for the account.
Transaction fee payers bump a virtual rent balance when writing to the account, which keeps the account “hot”.
“Cold” accounts virtual rent balance below threshold (eg 24h without write bump) get auto-compressed.
The cold account’s state is cryptographically preserved on the Solana ledger. Users can load a cold account into hot state in-flight when using the account again.

Mint Accounts

Light mints are on-chain accounts like SPL mints, but with rent-exemption paid for by the Token program, instead of the user.

Light-mints uniquely represent a token on Solana and store its global metadata, similar to SPL mint accounts with few core differences:

Tokens created from light-mints are light-tokens.
Token metadata (name, symbol, URI) is stored as an extension in the struct.

Creation Cost	Light Token	SPL-Token
Mint Account	0.000091 SOL	0.0015 SOL

Diagram
Source Code

Diagram showing light-mint account structure with three components: Address (identifier for light-mint in purple box), Account (struct containing BaseMint with SPL-compatible fields, MintMetadata for program state, and optional Extensions for Token Metadata), and BaseMint (containing Supply, Decimals, Mint Authority, and Freeze Authority fields) with Token Metadata extension

pub struct Mint {
    pub base: BaseMint,
    pub metadata: MintMetadata,
    /// Reserved bytes (16 bytes) for T22 layout compatibility.
    /// Positions account_type at offset 165: 82 (BaseMint) + 67 (metadata) + 16 (reserved) = 165.
    pub reserved: [u8; 16],
    /// Account type discriminator at byte 165 (1 = Mint, 2 = Account)
    pub account_type: u8,
    /// Compression info embedded directly in the mint
    pub compression: CompressionInfo,
    pub extensions: Option<Vec<ExtensionStruct>>,
}

Find the source code of light-mints here.

The metadata field is used by the Light Token Program to store the internal state of a light-mint. The BaseMint field replicates the field layout and serialization format of SPL Mint accounts. The struct is serialized with Borsh to match the on-chain format of SPL tokens and mints. Here is how light-mints and SPL mints compare:

Basemint vs SPL mint
BaseMint Struct

Field	Light-Mint	SPL Mint
mint_authority	✓	✓
supply	✓	✓
decimals	✓	✓
is_initialized	✓	✓
freeze_authority	✓	✓
Light-Mint Data	✓	-
Extensions	✓	via Token-2022

pub struct BaseMint {
    /// Optional authority used to mint new tokens. The mint authority may only
    /// be provided during mint creation. If no mint authority is present
    /// then the mint has a fixed supply and no further tokens may be
    /// minted.
    pub mint_authority: Option<Pubkey>,
    /// Total supply of tokens.
    pub supply: u64,
    /// Number of base 10 digits to the right of the decimal place.
    pub decimals: u8,
    /// Is initialized - for SPL compatibility
    pub is_initialized: bool,
    /// Optional authority to freeze token accounts.
    pub freeze_authority: Option<Pubkey>,
}

Token Account

Light token accounts are on-chain accounts like SPL token accounts, but with rent-exemption paid for by the Token program, instead of the user.

A light-token account holds token balances like SPL Token accounts:

A wallet needs a light-token account for each light-mint, SPL mint, or Token 2022 mint it wants to hold, with the wallet address set as the light-token account owner.
Each wallet can own multiple light-token accounts for the same light-mint.
A light-token account can only have one owner and hold units of one light-mint.

Creation Cost	Light Token	SPL-Token
Token Account	0.000017 SOL	0.0029 SOL

Additionally Light Token is more compute-efficient than SPL on hot paths:

CU Performance	Light Token	SPL-Token
ATA Creation	4,348	14,194
Transfer	312	4,645
Transfer (rent-free)	1,885	4,645

Diagram
Source Code

Diagram showing light-token Solana account structure with three components: Address (identifier for light-token account in purple box), Account (struct containing Data bytes, Executable flag, Lamports balance, and Owner set to Light Token Program), and AccountData (containing Mint, Owner, Amount, and Extensions fields)

/// Ctoken account structure (same as SPL Token Account but with extensions).
pub struct Token {
    pub mint: Pubkey,
    pub owner: Pubkey,
    pub amount: u64,
    pub delegate: Option<Pubkey>,
    pub state: AccountState,
    pub is_native: Option<u64>,
    pub delegated_amount: u64,
    pub close_authority: Option<Pubkey>,
    pub account_type: u8,
    pub extensions: Option<Vec<ExtensionStruct>>,
}

Find the source code of light-tokens here.

Light token accounts replicate the field layout and serialization format of SPL Token accounts. The struct is serialized with Borsh to match the on-chain format of SPL tokens. Here is how light-tokens and SPL tokens compare:

Field	Light Token	SPL Token Account
mint	✓	✓
owner	✓	✓
amount	✓	✓
delegate	✓	✓
state	✓	✓
is_native	✓	✓
delegated_amount	✓	✓
close_authority	✓	✓
extensions	✓	via Token-2022

Associated Light Token Account

Associated light-token accounts (light-ATAs) follow the same pattern as associated token accounts (ATA):

Each wallet needs its own light-token account to hold tokens from the same light-mint.
The address for light-ATAs is deterministically derived with the owner’s address, light token program ID, and mint address.

let seeds = [
    owner.as_ref(),          // Wallet address (32 bytes)
    program_id.as_ref(),     // Light Token Program ID (32 bytes)
    mint.as_ref(),           // light-mint address (32 bytes)
    bump.as_ref(),           // Bump seed (1 byte)
];

Find the source code to associated light-token accounts here.

Compressed Token Account

Under the hood, compressed token accounts store token balance, owner, and other information of inactive light-tokens.

Light token accounts are automatically compressed/decompressed when active/inactive.
Any light-token or SPL token can be compressed/decompressed at will.

You can still use compressed tokens for token distribution.

Diagram
Source Code

Diagram showing compressed token account structure with three components: Hash (identifier for compressed token account in purple box), Account (struct containing Data bytes, Executable flag, Lamports balance, and Address set to None), and AccountData (containing Mint, Owner, Amount, and Extensions fields)

pub struct TokenData {
    pub mint: Pubkey,
    pub owner: Pubkey,
    pub amount: u64,
    pub delegate: Option<Pubkey>,
    pub state: u8,
    /// Extensions for the compressed token account
    pub tlv: Option<Vec<ExtensionStruct>>,
}

Introduction

Light Token APIs

PDA Accounts

For Other Use Cases

Learn

Resources

Core concepts of the Light Token program

Rent Config by Light Token Program

Mint Accounts

Token Account

Associated Light Token Account

Compressed Token Account

Next Steps

Create Light Token Accounts

Introduction

Light Token APIs

PDA Accounts

For Other Use Cases

Learn

Resources

Documentation Index

​Rent Config by Light Token Program

​Mint Accounts

​Token Account

​Associated Light Token Account

​Compressed Token Account

​Next Steps

Create Light Token Accounts

Rent Config by Light Token Program

Mint Accounts

Token Account

Associated Light Token Account

Compressed Token Account

Next Steps