Initializing TAC SDK...
;
-
- const handleTransaction = async () => {
- // Use tacSdk for cross-chain operations
- const result = await tacSdk.sendCrossChainTransaction(/* ... */);
- };
-
- return (
-
- );
-};
-```
-
-### Next.js Integration
-
-For Next.js applications, handle client-side initialization:
-
-```jsx
-// hooks/useTacSdk.js
-import { useEffect, useState } from "react";
-import { TacSdk, Network } from "@tonappchain/sdk";
-
-export const useTacSdk = () => {
- const [tacSdk, setTacSdk] = useState(null);
- const [loading, setLoading] = useState(true);
-
- useEffect(() => {
- // Only initialize on client side
- if (typeof window !== "undefined") {
- const initializeSdk = async () => {
- try {
- const sdk = await TacSdk.create({
- network: Network.TESTNET,
- });
- setTacSdk(sdk);
- } catch (error) {
- console.error("SDK initialization failed:", error);
- } finally {
- setLoading(false);
- }
- };
-
- initializeSdk();
- }
- }, []);
-
- return { tacSdk, loading };
-};
-```
-
-### Vue.js Integration
-
-For Vue applications, create a composable:
-
-```javascript
-// composables/useTacSdk.js
-import { ref, onMounted, onUnmounted } from "vue";
-import { TacSdk, Network } from "@tonappchain/sdk";
-
-export function useTacSdk() {
- const tacSdk = ref(null);
- const loading = ref(true);
-
- onMounted(async () => {
- try {
- tacSdk.value = await TacSdk.create({
- network: Network.TESTNET,
- });
- } catch (error) {
- console.error("TAC SDK initialization failed:", error);
- } finally {
- loading.value = false;
- }
- });
-
- onUnmounted(() => {
- if (tacSdk.value) {
- tacSdk.value.closeConnections();
- }
- });
-
- return { tacSdk, loading };
-}
-```
-
-## TON Connect Integration
-
-For browser applications, integrate with TON Connect for wallet connectivity:
-
-### Install TON Connect
-
-```bash
-npm install @tonconnect/ui
-```
-
-### Configure TON Connect
-
-```javascript
-import { TonConnectUI } from "@tonconnect/ui";
-
-// Initialize TON Connect
-const tonConnectUI = new TonConnectUI({
- manifestUrl: "https://yourapp.com/tonconnect-manifest.json",
- buttonRootId: "ton-connect-button",
-});
-
-// Create sender from TON Connect
-import { SenderFactory } from "@tonappchain/sdk";
-
-const sender = await SenderFactory.getSender({
- tonConnect: tonConnectUI,
-});
-```
-
-### TON Connect Manifest
-
-Create a manifest file for your application:
-
-```json
-{
- "url": "https://yourapp.com",
- "name": "Your dApp Name",
- "iconUrl": "https://yourapp.com/icon.png",
- "termsOfUseUrl": "https://yourapp.com/terms",
- "privacyPolicyUrl": "https://yourapp.com/privacy"
-}
-```
-
-## TypeScript Configuration
-
-If using TypeScript, ensure your `tsconfig.json` includes proper module resolution:
-
-```json
-{
- "compilerOptions": {
- "target": "ES2020",
- "module": "ESNext",
- "moduleResolution": "node",
- "esModuleInterop": true,
- "allowSyntheticDefaultImports": true,
- "strict": true,
- "skipLibCheck": true,
- "forceConsistentCasingInFileNames": true
- }
-}
-```
-
-## SDK Configuration Options
-
-The SDK accepts several configuration options during initialization:
-
-```javascript
-const tacSdk = await TacSdk.create({
- network: Network.TESTNET, // Network selection
- delay: 1000, // Delay between operations (milliseconds)
- TONParams: {
- // TON-specific configuration
- contractOpener: tonClient, // Custom TonClient instance
- },
- TACParams: {
- // TAC-specific configuration
- provider: customProvider, // Custom provider
- },
-});
-```
-
-Loading wallet...
;
- }
-
- return (
-
- {isConnected ? (
-
- );
-};
-```
-
-## Private Key Integration
-
-For backend services, automated systems, or development environments, you can create senders directly from mnemonic phrases or private keys.
-
-### Standard TON Wallets
-
-The SDK supports all standard TON wallet versions:
-
-```javascript
-import { SenderFactory, Network, AssetType } from "@tonappchain/sdk";
-
-// Wallet V4 (most common)
-const senderV4 = await SenderFactory.getSender({
- network: Network.TESTNET,
- version: "V4",
- mnemonic: "word1 word2 word3 ... word24",
-});
-
-// Wallet V5R1 (latest)
-const senderV5 = await SenderFactory.getSender({
- network: Network.TESTNET,
- version: "V5R1",
- mnemonic: "word1 word2 word3 ... word24",
- options: {
- v5r1: {
- subwalletNumber: 0, // Optional subwallet number
- },
- },
-});
-
-// Legacy wallets
-const senderV3 = await SenderFactory.getSender({
- network: Network.TESTNET,
- version: "V3R2",
- mnemonic: "word1 word2 word3 ... word24",
-});
-```
-
-### Highload Wallet V3
-
-For applications requiring high transaction throughput:
-
-```javascript
-const highloadSender = await SenderFactory.getSender({
- network: Network.TESTNET,
- version: "HIGHLOAD_V3",
- mnemonic: "word1 word2 word3 ... word24",
- options: {
- highloadV3: {
- subwalletId: 0, // Subwallet identifier
- timeout: 60, // Transaction timeout in seconds
- },
- },
-});
-```
-
-
-
- ) : (
-
- )}
- Connected: {wallet.device.appName}
-Address: {wallet.account.address}
- - -
-
-
-### TON Side: SDK-Managed Proxies
-
-On the TON side, proxy functionality is handled automatically by the TAC SDK rather than requiring developers to write custom smart contracts.
-
-- **User Transaction Handling**: When a TON user initiates a transaction with a hybrid dApp, the SDK formats the request appropriately for cross-chain delivery. This includes encoding method parameters and preparing asset transfer instructions.
-
-- **Asset Locking**: The SDK manages the locking of user assets in the TON Adapter contracts. Users simply approve transactions in their familiar TON wallets, while the SDK handles the technical details of cross-chain asset preparation.
-
-- **Status Monitoring**: The SDK continuously monitors transaction status and provides real-time updates to the user interface. This allows hybrid dApps to show progress indicators and handle errors gracefully.
-
-- **Message Formatting**: All the complex message structuring required by the TON Adapter is handled automatically, including proper encoding of target addresses, method signatures, and parameters.
-
-
-
-
-### Group Formation and Management
-
-- **Approval Process**: Sequencer groups are not permissionless - they require approval through DAO voting or multisig processes. This ensures that only trusted entities with proper infrastructure and incentives can participate in securing cross-chain messages.
-
-- **Group Composition**: Each group contains multiple sequencer nodes owned by a specific entity. This could be a trusted dApp, infrastructure provider, or other stakeholder with strong incentives to maintain network security.
-
-- **Internal Operations**: Within each group, sequencers operate independently but must coordinate to reach consensus. This internal redundancy protects against individual node failures while maintaining group-level reliability.
-
-### Economic Requirements
-
-
-
-
-### Core Technology Stack
-
-
-
-
-The SDK acts as a bridge between your frontend application and TAC's cross-chain infrastructure:
-
-
-
-
-## Message Structure
-
-Every cross-chain operation begins with a structured message that contains all necessary information for secure execution:
-
-```javascript
-{
- timestamp: 1640995200, // TON blockchain timestamp
- target: "0x742d35Cc6473...", // Target smart contract address
- methodName: "swapTokens(bytes,bytes)", // Method signature
- arguments: "0x1234...", // Encoded method parameters
- caller: "EQAbc123...", // Original TON caller address
- mintTokens: [...], // Tokens to mint on TAC EVM
- unlockTokens: [...] // Tokens to unlock from previous locks
-}
-```
-
-This message structure ensures that sequencers have all the information needed to validate the operation and execute it correctly on the target chain.
-
-## Sequencer Network
-
-The security and reliability of the TON Adapter depends on a distributed network of sequencers that validate and process cross-chain messages.
-
-### Individual Sequencer Operations
-
-Each sequencer in the network operates independently while following the same validation protocols:
-
-- **Event Monitoring**: Sequencers continuously monitor both TON and TAC EVM for relevant events. When a user initiates a cross-chain transaction, multiple sequencers detect the event simultaneously.
-
-- **Local Validation**: Before participating in consensus, each sequencer validates the transaction locally. This includes verifying asset transfers match message parameters and ensuring the requesting user has sufficient balances.
-
-- **Database Storage**: Validated events are stored in each sequencer's local database, creating a distributed record of all cross-chain activity.
-
-- **Merkle Tree Formation**: At regular intervals determined by network parameters, sequencers compile their validated transactions into Merkle trees, creating cryptographic proofs of transaction inclusion.
-
-### Sequencer Groups
-
-The network organizes sequencers into groups to enhance security through redundancy and consensus requirements.
-
-
-
-
-### 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:
-
-
- **TON Standard**: TON jettons typically use 9 decimals, following the
- platform's conventions for token precision.
-
-
-
- **EVM Standard**: Ethereum and EVM chains commonly use 18 decimals,
- providing higher precision for complex DeFi operations.
-
-
-
-
-## Validation Layers
-
-Message validation occurs at multiple layers, each providing different security guarantees and catching different types of potential issues.
-
-### Client-Side Pre-Validation
-
-Before messages even enter the cross-chain system, the TAC SDK performs initial validation to catch obvious errors early.
-
-
-
-
-The lifecycle involves three main phases: **Initiation** (user action), **Processing** (validation and consensus), and **Execution** (target chain operations). Each phase includes multiple stages that ensure security and reliability.
-
-## Stage Progression
-
-Cross-chain transactions progress through specific stages that can be monitored and tracked for status updates.
-
-### TON-Side Stages
-
-
-
-
-## Architecture Overview
-
-
-
-
-## The Problem TAC Solves
-
-- **Challenge**: Reaching TON's billion users requires rebuilding entire - applications in FunC, TON's native language.
- - **TAC Solution**: Deploy - existing Solidity contracts as-is and make them accessible to TON users -
- **Challenge**: Limited access to DeFi, gaming, and other EVM applications - that dominate the blockchain space.
- **TAC Solution**: Use any EVM application directly from TON wallets without bridges or multiple wallets -
-
-
-### TON-Origin Tokens
-
-- **TON Jettons**: Standard fungible tokens native to the TON blockchain that follow TON's jetton standard with typical 9-decimal precision.
-
-- **Native TON**: The native currency of the TON blockchain, which receives special handling when bridging to maintain its fundamental properties.
-
-- **TON-Native Assets**: Specialized tokens created specifically for the TON ecosystem, including governance tokens, utility tokens, and application-specific assets.
-
-### TAC EVM-Origin Tokens
-
-- **Native TAC Tokens**: Tokens originally created on the TAC EVM Layer, including the native TAC token used for gas fees and protocol operations.
-
-- **EVM dApp Tokens**: Tokens created by applications deployed on TAC EVM, such as liquidity provider tokens, governance tokens, and application-specific assets.
-
-- **Wrapped Assets**: Representations of external assets that have been brought into the TAC EVM ecosystem through various bridging mechanisms.
-
-## Token Deployment Process
-
-When tokens first cross between chains, TAC automatically handles the deployment of corresponding token contracts with proper metadata preservation.
-
-### Automatic Deployment Triggers
-
-
+ **TON Standard**: TON jettons typically use 9 decimals, following the
+ platform's conventions for token precision.
+
+
+
+ **EVM Standard**: Ethereum and EVM chains commonly use 18 decimals,
+ providing higher precision for complex DeFi operations.
+
+
-
-
+
+
+## Main Layers
+
++ **Challenge**: Reaching TON's billion users requires rebuilding entire + applications in FunC, TON's native language.
+ + **TAC Solution**: Deploy + existing Solidity contracts as-is and make them accessible to TON users +
+ **Challenge**: Limited access to DeFi, gaming, and other EVM applications + that dominate the blockchain space.
+ **TAC Solution**: Use any EVM application directly from TON wallets without bridges or multiple wallets +