New

Integrate expert-curated crypto & blockchain knowledge into your app with the upcoming IQ.wiki API.

0% read

TAC Network

TAC Network

TON Architectural Chain (TAC) is a infrastructure project that connects -compatible applications to the and Telegram ecosystems via an -compatible network and a cross-chain communication framework. The project enables Solidity-based applications to interact with wallets, assets, and Telegram Mini Apps without requiring developers to rebuild applications for . [1]

Overview

TAC is an -compatible designed to connect -based with the and Telegram ecosystems. Built on and Ethermint, it enables developers to deploy Solidity and provides interoperability with via a dedicated cross-chain messaging layer. Its architecture includes the TAC Layer, the Adapter, and the TAC SDK, which together allow applications to interact with wallets, -native assets, and Telegram-based interfaces.

A core feature of TAC is its Hybrid dApp framework, which enables -compatible applications to be accessed by users without requiring separate wallets, wrapped assets, or direct interaction with bridging infrastructure. Through development tools and support for Telegram Mini Apps, TAC provides a way for developers to integrate -based functionality, including services such as asset swaps, lending, and yield-generating applications, into the and Telegram ecosystems. [6] [8]

Features

Hybrid dApps

Hybrid dApps are that combine -compatible functionality with user interfaces and distribution channels built within the and Telegram ecosystems. Using TAC’s infrastructure, developers can deploy existing Solidity-based applications, enabling users to access them through wallets and Telegram Mini Apps. The underlying smart contract logic executes on TAC’s -compatible , while cross-chain communication is handled through the Adapter.

The Hybrid dApp model is designed to connect Ethereum-based decentralized finance and application infrastructure with Telegram-native user experiences. Through the TAC SDK, Telegram Mini Apps can interact with without requiring users to manage multiple wallets, switch networks, or use bridging mechanisms. This architecture enables applications such as token swaps, lending protocols, liquidity provision platforms, and other services to be accessed through familiar Telegram interfaces while leveraging TAC's security and execution environment. Examples of applications integrated through this framework include protocols such as , , and . Hybrid dApps also provide a pathway for interoperability between the ecosystem and -based applications, allowing users to access functionality while enabling Solidity developers to deploy applications without rebuilding them for ’s native virtual machine. [2] [4]

Architecture

TAC is a architecture designed to enable interoperability between the ecosystem and -compatible . The protocol combines an -compatible execution layer with a cross-chain communication framework that facilitates deterministic message passing and asset transfers between and TAC. Its architecture relies on standardized cross-chain messaging, decentralized sequencing, and on-chain verification to coordinate interactions across both networks while maintaining native user experiences on the side.

The architecture consists of several core components. The TAC Layer, built with and Ethermint, provides a fully -compatible execution environment that supports Solidity , standard development tools, EIP-1559 mechanics, and consensus. Cross-chain communication is managed through the Adapter, a set of deployed on both networks that validate transactions, lock and manage assets, format messages, verify proofs, and prevent duplicate or invalid executions. A decentralized Sequencer Network monitors events across and TAC, aggregates them into Merkle trees, and submits transaction roots for consensus, while an Execution Layer assigns executors to process validated cross-chain messages and complete operations in a permissionless manner.

Applications integrated with TAC use a combination of the TAC SDK and standardized proxy contracts. The SDK handles message construction and interaction with cross-chain infrastructure on , while proxy contracts on the TAC side receive validated messages and execute the corresponding calls. Together, these components provide a framework for deploying Hybrid dApps that allow users to interact with -based applications through cross-chain messaging and asset management mechanisms. [8]

Tokenonmics

TAC is the native of the TAC Network and serves as the primary asset for transaction processing, network security, and governance. Issued as an token on the TAC Layer, it is integrated into the protocol’s execution and and is used across the network’s core infrastructure. Within the protocol, TAC functions as the token for transactions executed on the TAC Layer. It is also used in the network’s system, where stake tokens to help secure the and may face penalties for malicious behavior. In addition, staked TAC provides governance rights, allowing participants to vote on protocol upgrades, network parameters, and other ecosystem decisions. For users interacting through , the network can automatically convert into TAC, allowing cross-chain operations to be processed without direct management of the token. [5] [7]

Partnerships

See something wrong?

References (8 sources)

HomeCategoriesWiki MCEventsGlossary