Asset Bridging

Asset bridging in TAC enables tokens to move seamlessly between TON and TAC EVM while maintaining supply integrity and user ownership. Unlike traditional bridges that create wrapped tokens, TAC’s bridging system is designed specifically for application-level interactions where assets flow naturally based on user intent rather than explicit bridging operations.

​

Core Bridging Principles

TAC’s asset bridging system operates on fundamental principles that ensure security, maintain token economics, and provide seamless user experience.

​

Supply Conservation

• Total Supply Integrity: The combined supply of a token across both TON and TAC EVM always equals the original supply. When tokens are locked on one chain, equivalent amounts are minted on the other chain, maintaining perfect balance.

• Provable Reserves: All locked tokens are held in verifiable smart contracts where their existence can be independently confirmed by anyone.

• Atomic Operations: Asset locking, minting, burning, and releasing operations occur atomically within the same cross-chain transaction, preventing inconsistent states.

​

Bidirectional Flow

Assets can move in both directions depending on user operations and application requirements:

​

Token Types and Handling

Different types of assets require specialized handling to ensure proper representation and functionality across both chains.

​

TON Native Assets

// Bridging a TON jetton
const assets = [{
  address: "EQTokenAddress...", // TON jetton address
  amount: 100.5,                // User-friendly amount
  decimals: 9                   // TON standard decimals
}];

// Bridging a TON jetton
const assets = [{
  address: "EQTokenAddress...", // TON jetton address
  amount: 100.5,                // User-friendly amount
  decimals: 9                   // TON standard decimals
}];

// Bridging native TON
const nativeTONBridge = [{
  // No address needed for native TON
  amount: 5.0
}];

​

TAC EVM Native Assets

• EVM-Origin Tokens: Tokens originally created on TAC EVM can also be bridged to TON, creating jetton representations on the TON side.

• Liquidity Pool Tokens: LP tokens from DEXes and other DeFi protocols on TAC EVM can be bridged to TON for use in TON-native applications.

• Governance Tokens: TAC-native governance tokens can be bridged to enable participation in governance from TON wallets.

​

Bridging Mechanisms

​

Lock-and-Mint Process

When assets move from TON to TAC EVM, they undergo a structured locking and minting process:

​

Burn-and-Release Process

The reverse process handles assets moving from TAC EVM back to TON:

​

Address Calculation and Mapping

TAC maintains deterministic relationships between token addresses across chains, enabling predictable bridging behavior.

​

Deterministic Address Generation

• TON to EVM Mapping: When a TON jetton first crosses to TAC EVM, its corresponding ERC-20 address is calculated based on the jetton’s metadata and TON address.

• EVM to TON Mapping: Similarly, EVM tokens bridging to TON receive deterministic jetton addresses based on their EVM metadata.

• Pre-Calculation: Applications can calculate paired addresses before tokens actually bridge, enabling advanced features like showing expected addresses in user interfaces.

​

Address Registry

​

Decimal and Precision Handling

Different blockchain ecosystems use different decimal standards, requiring careful handling to maintain precision and user experience.

​

Decimal Standards

​

Precision Management

• Preservation: When TON tokens (9 decimals) bridge to TAC EVM, they maintain their 9 decimal precision rather than being artificially inflated to 18 decimals.

• Compatibility: TAC EVM supports tokens with various decimal counts, ensuring that bridged tokens work correctly with existing DeFi protocols.

• User Interface: Applications display amounts using the appropriate decimal precision for user familiarity while handling the technical differences behind the scenes.

​

Automatic Token Deployment

The bridging system includes automatic token deployment capabilities that reduce friction for first-time token bridging.

​

Deployment Process

• Metadata Extraction: When a token first crosses chains, the system extracts all necessary metadata including name, symbol, decimals, and description.

• Contract Generation: A standard ERC-20 or jetton contract is automatically deployed with the extracted metadata.

• Registry Update: The new token deployment is registered in the cross-chain address registry for future reference.

​

Deployment Triggers

• First Bridge Operation: Token contracts are deployed automatically when a user first bridges a particular token type.

• Batch Deployment: Multiple token types can be deployed in a single operation when complex transactions involve multiple new tokens.

• Permissionless Process: Anyone can trigger token deployment by bridging assets, making the system fully permissionless.

​

Liquidity Management

Asset bridging enables sophisticated liquidity management strategies that benefit both ecosystems.

​

Unified Liquidity Pools

• Cross-Chain Liquidity: Tokens can flow between chains based on where liquidity is most needed, optimizing capital efficiency.

• Arbitrage Opportunities: Price differences between chains create natural arbitrage opportunities that help maintain price consistency.

• Protocol Integration: DeFi protocols can access liquidity from both ecosystems, increasing available capital and reducing slippage.

​

Example: DEX Liquidity

When users provide liquidity to a DEX on TAC EVM using TON-origin tokens:

​

Security Considerations

Asset bridging implements multiple security layers to protect user funds and maintain system integrity.

​

Economic Security

• Collateral Requirements: Sequencers stake significant collateral to participate in bridging validation, creating financial incentives for honest behavior.

• Multi-Party Validation: Multiple independent sequencer groups must agree on bridging operations before execution.

• Slashing Mechanisms: Provably incorrect bridging operations result in automatic collateral slashing.

​

Technical Security

​

Integration Patterns

Developers can integrate asset bridging into their applications using several common patterns.

​

Automatic Bridging

• Transparent Operations: Users specify what they want to do (swap, provide liquidity, etc.) and the system automatically bridges required assets.

• Single Transaction: From the user’s perspective, asset bridging and the target operation happen in a single transaction.

• Status Updates: Applications can provide real-time updates on both bridging progress and target operation execution.

​

Manual Bridging

• Explicit Control: Some applications allow users to explicitly bridge assets before performing operations.

• Batch Operations: Users can bridge multiple assets in preparation for complex operations.

• Advanced Features: Manual bridging enables advanced features like pre-positioning assets for better execution.

​

What’s Next?

Understanding asset bridging provides the foundation for exploring how complete transactions flow through TAC’s cross-chain system.