TAC

The TAC token is the native utility asset that powers the entire network’s operation and incentive systems.

Gas: TAC is used to pay transaction fees on the TAC EVM, enabling deterministic execution and contract interaction. Staking and security: Validators stake TAC to secure the blockchain. Misbehaviour results in slashing or loss of staked funds, maintaining validator accountability. Governance: Token holders participate in voting on network upgrades, economic parameters, and ecosystem decisions. Cross chain operations: Sequencers and executors earn TAC rewards for validating and processing messages between TAC and TON. Incentive alignment: Developers and service operators can integrate TAC to access priority network features and earn a share of protocol-level incentives. This structure ensures that economic alignment across developers, users, validators, and cross chain operators maintains the network’s decentralisation and stability.

TAC functions as a bridge between Ethereum’s development environment and Telegram’s native infrastructure. The network consists of several key components that coordinate cross chain activity.

TAC EVM layer: Runs Solidity-based applications through the Ethermint engine, achieving near 2-second block times and full EVM compatibility. TON adapter: A protocol layer that packages, verifies, and relays transactions between TAC and TON. It maintains message integrity and prevents duplication or replay. Sequencer network: Collects transactions from both TAC and TON, aggregates them into Merkle trees, and reaches consensus on message batches before forwarding them for execution. Executors: Permissionless agents that process validated cross chain calls, ensuring atomicity and providing automatic rollback if execution fails. Proxy contracts: Stateless EVM contracts that allow hybrid applications to handle cross chain messages natively from TON wallets or Telegram interfaces. This coordinated design enables applications deployed on TAC to interact with TON users and assets as if both systems were part of the same environment. As a result, developers can build multi chain products without duplicating codebases or maintaining separate deployments.