Skip to main content

Documentation

The contents of the Custom Proxy page block you are viewing are primarily for informational purposes. For complete details on Custom Proxy development, please refer to the official documentation linked below:

Custom Proxy

Developer documentation within @tonappchain/evm-ccl NPM-package
You can also reach out to our developer community in Telegram or Discord.

Installation

Setting up TAC Proxy development requires installing the TAC cross-chain libraries and configuring your Solidity development environment. TAC Proxy development currently requires Hardhat. Foundry support is planned in future.

Hardhat Environment Setup

Ensure your Hardhat project includes the necessary dependencies:
package.json
Configure your hardhat.config.js for TAC networks:
hardhat.config.js

Project Structure Setup

Create an organized project structure for proxy development:

Create Contract Directory

Organize your contracts with clear separation between proxy and application logic:

Setup Testing Environment

Create a test directory with proper organization:

Configure Environment Variables

Create a .env file for sensitive configuration:
.env
Never commit your .env file. Add it to your .gitignore immediately.

Verify Installation

Create a basic proxy contract to verify your setup:
contracts/TestProxy.sol
Compile to verify setup:
If compilation succeeds, your environment is properly configured for TAC Proxy development.

Common Setup Issues

Problem: Import resolution failures or compilation errorsSolutions:
  • Ensure @tonappchain/evm-ccl is properly installed
  • Verify Solidity version compatibility (0.8.28+)
  • Check import paths are correct
  • Reset and reinstall dependencies:
  • Clean and rebuild:
Problem: Unable to connect to TAC networkSolutions:
  • Verify RPC URLs are correct
  • Check network configuration in hardhat.config.js
  • Test connection manually: curl https://spb.rpc.tac.build
  • Ensure firewall allows outbound connections
Problem: Deployment fails with account/key errorsSolutions:
  • Verify private key is in .env file
  • Ensure private key starts with 0x if required by your configuration
  • Check that the account has sufficient TAC tokens for deployment. Get them here

What’s Next?

Environment ready? Let’s get to examples:

Basic Proxy Example