FREEBLOCK / SMART CONTRACTS
TON smart contract
development
Turn your product rules into TON contracts with explicit states, messages and access controls. We connect the contract to your backend, wallet flow and application interface.
Start with an idea, a specification or existing code.
01 / YOUR PRODUCT
A contract for specific product rules
TON smart contract development starts by defining what must be verified on-chain and which data the application needs.
Jettons and distribution
Minting permissions, transfers, distribution and associated restrictions. Agree on the standard and additional token rules.
Application mechanics
Rewards, access, game or payment actions where verifiable on-chain logic is needed.
Existing contracts
Review the code, storage, messages and administrator permissions to assess changes or migration.
02 / DELIVERY SCOPE
What comes with the contract
Working code needs tests and an integration path. We scope application integration separately from contract implementation.
-
Behaviour specification
States, permitted actions, messages, roles and configuration rules.
-
Contract and tests
Business logic, input validation, access checks, failures and contract interactions.
-
Integration layer
Data reads, request construction, result tracking and agreed API formats.
-
Testnet validation
Deployment scripts and complete journeys with the wallet and application.
-
Launch preparation
Mainnet configuration, access handover, documentation and agreed monitoring.
03 / DESIGN DECISIONS
Designed around TON’s architecture
- Messages and intermediate states
- Contract interactions may involve multiple messages. Plan failures, bounced messages and the final outcome, beyond successful signing.
- Languages and tools
- For new contracts we consider the current TON stack, including Tolk. Existing FunC or Tact projects begin with a code and tooling compatibility review.
- Permissions and upgrades
- Specify administrator actions, pauses, upgradeability and limits so users and operators understand the same rules.
Technical references: TON smart contracts · TON Connect
04 / FREEBLOCK PORTFOLIO
Experience in real projects
Pinot is a Telegram Mini App in the TON ecosystem. Its case study covers prototyping, interfaces and TON wallet integration. It illustrates our application integration experience; the contract development scope is agreed separately.
FREEBLOCK / CASE STUDY
piNot
Telegram Mini App on the TON blockchain
ChallengepiNot is a financial gaming application in the format of a Telegram WebApp, built on the principle of a “matrix” crypto game. Users purchase pyramids with NOTcoin tokens, receive income in several stages, participate in a referral program, and manage their game field where rotating pyramids are displayed.
What we builtpiNot is a financial gaming application in the format of a Telegram WebApp, built on the principle of a “matrix” crypto game. Users purchase pyramids with NOTcoin tokens, receive income in several stages, participate in a referral program, and manage their game field where rotating pyramids are displayed.
View case study: piNot05 / QUALITY AND OPERATIONS
Test behaviour, beyond compilation
Internal testing and an independent audit are separate stages. For contracts handling user assets, we agree on external review requirements before launch.
- Sender verification, parameters and administrator privileges.
- Repeated requests and malformed messages.
- Failures across message flows and final operation states.
- Data reads and accurate results in the application interface.
06 / COST AND TIMING
An estimate for your scope
First we define the initial release, integrations and acceptance criteria. Then we estimate delivery phases and identify external service costs separately.
Business logic
States, roles, tokens and contract interactions.
Application integration
Backend, TON Connect, indexing and interface work.
Testing and launch
Test scenarios, audit scope, deployment and operations.
07 / TECHNOLOGY
Tools for your product architecture
We select tools and networks after agreeing on the workflows. These catalogues show our available capabilities; your project gets a specific agreed stack.
Technologies
Blockchains
08 / FAQ
Before we start
Can you port a Solidity contract to TON?
Product logic can be redesigned for TON, but it is not a simple network change. The data model, messages, tools and tests need adaptation.
Which language will you use?
For new projects we select current TON tools for the task, including Tolk. If you already have FunC or Tact code, we review it and its maintenance requirements first.
What does TON Connect provide?
TON Connect connects an application to a compatible wallet for user interaction. It does not replace the contract, server-side verification or operation result tracking.
Can the scope be just a Jetton?
Yes. We specify token parameters, minting permissions and additional restrictions. A website, distribution, staking and other mechanisms are estimated separately.
Can you review existing code?
Yes. We need the repository or source code, expected behaviour and deployed addresses where available. The review scope is agreed separately.
How are cost and timing determined?
We estimate the logic, number of contracts, messages, integrations and testing depth. After reviewing the task, we propose phases and clear deliverables.
FREEBLOCK / LET’S TALK
Let’s define your contract logic.
What should the contract do? Do you have source code, a specification or an application?