Key Terminology
TON Wallet Basics
TON Wallet Structure:
- Each wallet operates as a smart contract on the TON blockchain.
- Requires deployment to the public chain before use, funded by a small amount of Toncoin for network fees.
- Managed via mnemonic phrases/private keys.
TON Accounts:
- Single mnemonic phrase can generate multiple accounts using different contract types provided by TON.
- Accounts vary in functionality based on their contract type but remain under unified mnemonic management.
Contract Versions (Contract Types)
TON offers diverse wallet contract types enabling unique functionalities:
Subwallet ID:
- Numeric identifier (default:
698983191) allowing creation of sub-wallets. - Enables hierarchical wallet management under a single public key.
- Numeric identifier (default:
Jetton System:
- Jetton: TON's non-native tokens.
- Jetton Wallet: Each Jetton type within a wallet is managed by a dedicated Jetton Wallet contract. Transactions occur through interactions between wallet and Jetton Wallet contracts.
TON vs. EVM Chains: Core Differences
Contract-Centric Design:
- Every entity (including wallets) is a smart contract. Wallet addresses = contract addresses.
Usage Costs:
- Users pay for contract deployment (first transaction) and ongoing storage fees.
Upgradability:
- TON contracts support upgrades, unlike EVM's typically immutable contracts.
Address Flexibility:
- Single public key can generate multiple accounts via Subwallet IDs.
Key Features of TON Wallets
Initial Deployment Cost:
- First transaction requires Toncoin to deploy the wallet contract.
Multi-Format Addresses:
- Single wallet can have multiple address formats, all pointing to the same contract.
- ⚠️ Cross-network transfers lead to permanent asset loss!
TON Address Formats and Characteristics
| Address Type | Use Case | Risk Considerations |
|---|---|---|
| EQ Addresses | Smart contract deposits | Funds rebound if contract undeployed. |
| User-Friendly | Wallet storage | Safer for fund retention. |
👉 Explore TON wallet security tips
Transaction Fee Breakdown
TON fees comprise:
Storage Fees:
- Paid per transaction based on contract size and time since last tx.
Forwarding Fees:
- In/Out Fwd Fees: Contract call costs for sending internal/external messages.
Computation Fees:
- Gas-priced at 400 nanotons per unit. Fixed rates apply (no user adjustments).
Total Fee Formula: Storage Fees + Forwarding Fees + Computation Fees + (Deployment Cost if first tx)
Critical Usage Notes
Fee Structure:
- Fees are blockchain-collected; third parties (e.g., TP Wallet) charge nothing.
Deployment & Storage:
- Initial deployment is one-time; storage fees recur per transaction.
Balance Alerts:
- Empty wallets deduct storage fees from incoming Toncoin (may cause receipt discrepancies).
Network Compatibility:
- Always verify recipient wallet network matches yours. Cross-network transfers = irreversible loss.
Security:
- Mnemonics/private keys are irreplaceable—store them securely.
DApp Interactions:
- Switched wallets may not trigger alerts. Confirm active wallet before transacting.
- Some DApps won’t flag network mismatches—double-check before proceeding.
FAQ Section
1. Why does my TON wallet need an initial deployment?
TON wallets are smart contracts requiring on-chain deployment (funded by Toncoin) to activate functionality.
2. Can I change my TON wallet address later?
No. Once created, wallet addresses remain fixed regardless of contract type updates.
3. How do Subwallet IDs work?
They allow generating multiple accounts under one public key by assigning different numeric IDs.
4. What happens if I send Toncoin to a non-deployed EQ address?
Funds will rebound, preventing loss—a safety feature for smart contracts.
5. Are TON transaction fees adjustable?
No. Fees are fixed per TON’s protocol; users cannot prioritize or modify payments.
6. How can I avoid cross-network transfer mistakes?
Always verify the recipient’s network matches yours in both direct transfers and DApp interactions.