TAC
AI NativeTAC 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
Published May 15, 2026
Not a good fit for teams or projects that:
Source:
No explicit throughput ceilings were identified in the accessible sources beyond general statements about performance and latency trade-offs.
Observed signals include:
Sources:
Some heuristic website-trust services flag tac.build as higher risk, largely due to domain age and cryptocurrency category heuristics. These signals can affect perception among cautious buyers but are not definitive assessments of protocol security.
Sources:
Likely fits:
Source cues:
Good fit for teams that:
Get a comprehensive analysis of TAC including market position, competitive landscape, adoption trends, and peer benchmarks.
Download full report →Requirements include proven decentralization guarantees immediately.
The organization requires mature enterprise compliance documentation (SOC 2, ISO 27001) from the protocol/team.
The application will not derive benefits from Telegram/TON distribution.
The project requires minimal cross-chain complexity.
Source:
Source:
TAC's roadmap documents ongoing work including:
Note: Roadmaps are plans and not guarantees of delivery.
Source:
Sources:
Source:
A constraint for this analysis: TAC is a blockchain protocol and does not appear on traditional B2B review platforms (G2, TrustRadius, Gartner Peer Insights) in a manner comparable to SaaS vendors. Searches for "TAC build" on those platforms returned primarily other entities named "TAC" (for example, TAC Security) or unrelated contractor pages.
Consequently, formal review-platform quotations for tac.build specifically were not identified in the accessible sources.
To provide context, this report references:
Because formal user reviews are scarce, reasons to adopt TAC are inferred from product positioning and public statements:
Sources:
Potential churn drivers, informed by architecture disclosures and typical cross-chain dynamics:
Sources:
TAC's blog includes "dApps Spotlight Series" posts (for example, listings referencing Curve and Euler) suggesting these protocols are present in the TAC ecosystem. Available excerpts do not provide independently verifiable metrics sufficient to treat them as rigorous case studies.
TAC's mainnet announcement states that several well-known DeFi protocols are listed as live/partnered (Curve, Zerolend, Euler, Morpho) and that the Summoning liquidity campaign reached a large amount of liquidity.
Critical evaluation: These are vendor-published claims. Independent verification would require on-chain analytics (Dune dashboards, chain explorers) or third-party reporting to confirm activity and sustained liquidity.
Sources:
TAC's airdrop guide documents claim mechanics (e.g., an immediate partial claim versus a larger allocation obtainable through staking/vesting), published staking yield guidance (moderate APY), and a multi-week undelegation period.
Critical evaluation: These mechanics can encourage staking participation but may also incentivize short-term farming. Buyers should evaluate whether token incentives correlate with sustained product usage.
Source:
Decision-makers:
End users / implementers:
Developer artifact:
TAC is an EVM-compatible blockchain that enables Ethereum/Solidity dApps to reach users in the TON and Telegram ecosystems without requiring TON users to adopt EVM tooling or manage bridge workflows. TAC describes this as "Same code" deployment for EVM apps, with Telegram Mini App distribution.
On the developer side, TAC provides:
On the user side, TAC's stated objective is to enable TON/Telegram users to access EVM DeFi protocols via familiar TON wallets and Telegram interfaces, reducing the need for wallet switching.
Sources:
Primary market: Web3 application teams (DeFi and consumer dApps) with existing Solidity/EVM codebases that want access to Telegram distribution and TON liquidity/users.
Positioning: a chain designed for EVM-to-TON/Telegram integration, competing with:
Sources: