TAC

Name: TAC
Brand: TAC

AI Native

TAC is a Layer 1 blockchain introducing a novel TON-Adapter to enable Ethereum dApps to access Telegram’s 950M+ users.

Est 2024|Valuation $8M|Raised $11.8M

LinkedIn 767|Web traffic 2K|FTEs 88

01Competitive Landscape

Narrative analysis: where TAC may be advantageous

- Distribution alignment: If Telegram Mini Apps and TON wallets are the target distribution surface, TAC provides integration primitives purpose-built for that surface and may require less custom bridging work than generic EVM L2s. - Developer familiarity: For teams with existing Solidity contracts, TAC's model of deploying existing EVM code with supporting SDKs can reduce migration effort compared with rewriting in TON-native languages. Sources: - Official vendor documentation (TAC problem statement and overview)

Where alternatives can excel

If Telegram/TON-specific UX is not required, general-purpose L2s (Base, Arbitrum, Optimism) offer:

Larger established developer ecosystems
More mature infrastructure, tooling, and security assumptions If a custom chain is required, CDK/Orbit/OP Stack provide more configurable rollup-building frameworks at the cost of increased operational responsibility.

(Industry observation; not directly cited to the TAC sources above.)

	TAC (tac.build)	Arbitrum Orbit	Polygon Agglayer CDK
Starting price / cost model	No public subscription tiers; costs arise from gas fees and integration/operational effort	Costs depend on infrastructure and potential commercial terms; many teams use RaaS providers	Costs depend on infrastructure, provers, and partners; no standard public monthly fee for the core toolkit
Primary use case	EVM dApps targeting distribution via Telegram and TON integration	Teams implementing appchains or L2/L3 strategies within the Arbitrum ecosystem	Teams building custom chains with Polygon tooling and Agglayer connectivity
Key strength	Integration architecture for TON/Telegram via TON Adapter and SDK	Strong Ethereum alignment and an existing Orbit ecosystem	Toolkit approach with Polygon ecosystem integration and tooling
Key weakness	Sequencer not fully decentralized per documentation; cross-chain complexity	Operational complexity of rollups and potential governance/licensing complexity	Operational complexity and integration overhead for custom chain builds

01Competitive Landscape

Narrative analysis: where TAC may be advantageous

Distribution alignment: If Telegram Mini Apps and TON wallets are the target distribution surface, TAC provides integration primitives purpose-built for that surface and may require less custom bridging work than generic EVM L2s.
Developer familiarity: For teams with existing Solidity contracts, TAC's model of deploying existing EVM code with supporting SDKs can reduce migration effort compared with rewriting in TON-native languages.

Sources:

Official vendor documentation (TAC problem statement and overview)

Where alternatives can excel

If Telegram/TON-specific UX is not required, general-purpose L2s (Base, Arbitrum, Optimism) offer:

Larger established developer ecosystems
More mature infrastructure, tooling, and security assumptions If a custom chain is required, CDK/Orbit/OP Stack provide more configurable rollup-building frameworks at the cost of increased operational responsibility.

(Industry observation; not directly cited to the TAC sources above.)

	TAC (tac.build)	Arbitrum Orbit	Polygon Agglayer CDK
Starting price / cost model	No public subscription tiers; costs arise from gas fees and integration/operational effort	Costs depend on infrastructure and potential commercial terms; many teams use RaaS providers	Costs depend on infrastructure, provers, and partners; no standard public monthly fee for the core toolkit
Primary use case	EVM dApps targeting distribution via Telegram and TON integration	Teams implementing appchains or L2/L3 strategies within the Arbitrum ecosystem	Teams building custom chains with Polygon tooling and Agglayer connectivity
Key strength	Integration architecture for TON/Telegram via TON Adapter and SDK	Strong Ethereum alignment and an existing Orbit ecosystem	Toolkit approach with Polygon ecosystem integration and tooling
Key weakness	Sequencer not fully decentralized per documentation; cross-chain complexity	Operational complexity of rollups and potential governance/licensing complexity	Operational complexity and integration overhead for custom chain builds

TAC

01Competitive Landscape

Narrative analysis: where TAC may be advantageous

Where alternatives can excel

02Market Map

01Competitive Landscape

Narrative analysis: where TAC may be advantageous

Where alternatives can excel

02Market Map