There are multiple choices for the Proxy App in this case: Option 1: using the single TAC ProxyApp on TON to rely users’ transactions on TAC EVM extension network. In this case, you can use the TAC SDK to easily implement the frontend with TON Connect. Option 2: you can build your own TAC Proxy App on TON and build a frontend that will prepare and execute transacitons for your proxy app. Note: TAC SDK (Option 1) is reccomended if you don’t know how to write secure code in funC (TON Native language). Opt for a custom Proxy App only if you need specific business logic to be executed on TON side before triggering Solidity code deployed on TAC EVM.

Option 1: using the single TAC ProxyApp on TON to rely users’ transactions on TAC EVM extension network. In this case, you can use the TAC SDK to easily implement the frontend with TON Connect.

eploying Solidity Code

Turin (Testnet): RPC endpoint: https://turin.rpc.tac.build Blockexplorer: https://turin.explorer.tac.build Faucet (for gas fees): https://turin.faucet.tac.build ChainId: 2390 FeeSchema: EIP-1559 BlockGasLimit: 20M Blocktime: 4 sec

tokens.

In future updates

Using these inputs, the SDK builds a TON transaction payload and enables further signature processing through TON-Connect or directly via mnemonic.

with.

ProxyDapp

cross-chain transactions

Install tacchaindCopy

sValidators

Proxy Apps: set of smart contracts (TON and TAC EVM) that enable direct application interaction

TON proxy

TON with

locking in the bridge

TAC proxy

purchase NFTs

Use the TAC testnet proxy generation

to an EVM testnet

Auto-Generation Process Proxy apps are automatically generated when you integrate your EVM application with TAC. You don’t need to write proxy contract code yourself - TAC handles this automatically.

adaptor wallet

TAC Adaptor

TAC Adaptor

TON proxy contract

the TAC Adaptor

t for the TAC Adaptor.

receives your transaction

Please note that, that when you use the TAC SDK, the proxy path is completely abstracted from you. And we recommend you to use the SDK instead of interacting with the proxy directly.

On EVM, it manages interactions between the execution layer and the target application.

On TON, it handles communication between your wallet and the execution layer.

handling all cross-chain complexities while providing a native experience for users.

Proxy apps can be both auto-generated (using TAC’s SDK) or manually deployed. This page covers the auto-generated proxy apps.

TON wallet

API Access On the frontend side, developers can access the TON network through two public endpoints: Mainnet: https://toncenter.com/api/v2/jsonRPC Testnet: https://testnet.toncenter.com/api/v2/jsonRPC To deploy Solidity code and directly access the TAC EVM Layer, developers can rely on public RPC endpoints that implements the standard EVM JSON-RPC interface: Mainnet: to-be-defined Testnet (Turin): [Coming Soon - later this week] Third party providers like Anrk, offers private RPC endpoints and agumented APIs.

Network Parameters Here are the key parameters of the TAC EVM network: ​Testnet (Turin) ChainId: [Coming Soon - later this week] Blocktime: 4 seconds Explorer: [Coming Soon - later this week] ​Mainnet to-be-defined

user’s wallet

making EVM apps feel native to TON users

must stake collateral

Uniswap v2

The EVM-based TAC environment naturally accommodates these tokens alongside standard 18-decimal tokens. However, bridging back to TON presents challenges, particularly for 18-decimal tokens originating in TAC (such as LP tokens). To address this, strict limits are implemented on unbridging to TON to prevent potential numerical overflow issues.

These bridged tokens then provide liquidity in the Uniswap pair.

necessary tokens

with tokens

An important consideration regarding metadata is its upgradeability. While all metadata fields except l1Address can be modified from the TON side, these changes are not currently reflected on the TAC side. The metadata remains static from the moment it first appears in the TAC Adaptor environment.

. When

All tokens within the system must implement the IERC20 interface standard.

These bridged tokens typically maintain 9 decimals rather than the standard 18.

nder CCL control

Learn about TAC token operations.

TAC accommodates two distinct categories of tokens in its ecosystem. The first category consists of Native TAC-originated tokens, which includes liquidity provider tokens and tokens emitted by dApps. While these tokens are expected to follow the ERC20 standard, this isn’t directly enforced at the protocol level. The second category comprises tokens bridged from TON, which operate under CCL control on the TAC side and are guaranteed to be ERC20-compliant. These bridged tokens typically maintain 9 decimals rather than the standard 18.

Finalization/Rollback

Successful transactions update state

parameters

processed

are sent

TON wallet

transfer

set of sequencers