Core Terminology
TON Wallet Fundamentals
In the TON ecosystem:
- Each wallet is managed by a mnemonic phrase/private key
Every wallet functions as a smart contract requiring:
- Pre-deployment to the blockchain
- Small TONcoin payment for network fees
TON Accounts System
- Single mnemonic phrase can generate multiple accounts
- Account capabilities vary by contract type
- Unified management through original mnemonic
Contract Versions (2 Types)
TON offers specialized wallet contracts enabling:
Subwallet Functionality
- Create child wallets
- Transaction restrictions (specific accounts only)
- Stake node operations
Jetton Management
- Jetton: TON's non-native tokens
- Each Jetton type has dedicated wallet contracts
- Transactions execute via contract interactions
Key Differences Between TON and EVM Chains
| Feature | TON Chain | EVM Chains |
|---|---|---|
| Project Structure | Everything is a contract | Separate contracts |
| Wallet Creation | Requires contract deployment | Free creation |
| Contract Upgradability | Supports upgrades | Difficult to upgrade |
| Address Generation | Subwallet ID variations | Single address per key |
Distinctive TON Wallet Characteristics
Initial Deployment Cost
- First transaction requires TONcoin payment
- Covers contract deployment
Multiple Address Formats
- Different formats point to same wallet
- ⚠️ Cross-network transfers cause permanent loss
Address Formats and Security Features
EQ Addresses:
- Ideal for fund-receiving smart contracts
- Transfers bounce if contract undeployed
Wallet-Optimized Addresses:
- Accepts funds without deployment requirement
- Safer for balance storage
Transaction Fee Structure
TON fees include five components:
Storage Fees
- Time-based account storage
- Scales with contract size
Forward Fees
- Inbound/outbound message costs
Computation Fees
- Gas-based execution costs
- 400 nanotons per gas unit
👉 Learn how to optimize TON transaction costs
Critical Usage Guidelines
Fee Structure
- All fees paid to TON network
- TP wallet charges nothing
Deployment Requirements
- Initial one-time deployment cost
- Recurring storage fees per transaction
Balance Management
- Empty wallets deduct storage fees upon receipt
- May cause apparent amount discrepancies
Security Protocols
- Verify recipient network match
- Double-check connected DApp network
- Cross-network transfers irrecoverable
Account Safety
- Mnemonic phrases remain primary security
- Existing wallets don't update with new contract types
FAQ: TON Wallet Essentials
Q: Can I recover funds sent to wrong network?
A: No. TON's cross-network transfers permanently lose assets.
Q: Why does my first transaction cost more?
A: It includes both deployment and regular fees.
Q: How do Subwallet IDs work?
A: They let single mnemonic generate multiple accounts while maintaining security.
Q: Are Jetton transactions different from native transfers?
A: Yes. Jettons require additional contract interactions between specialized wallets.
Q: Can I modify transaction fees?
A: Currently no. TON sets fixed network fees.
👉 Explore advanced TON wallet strategies
Conclusion
Understanding TON's contract-based architecture and fee model helps optimize wallet usage. Always verify network compatibility and maintain sufficient balances for storage fees.
Last updated: [Current Year]