3. Technological Advantages and Clear Path Forward

Currently, Tact compiles to FunC (the language from which Tolk was forked), rather than directly into assembly. Despite this intermediate compilation step, we've already made significant strides in optimizing gas efficiency. Specifically, for common use cases and typical developer-written contracts (without extreme, manual, low-level optimizations), contracts written in Tact now consume slightly less gas compared to the same logic written directly in FunC.

We achieved this through sophisticated, built-in low-level optimizations embedded into our compiler and standard library. Essentially, Tact automatically applies many optimizations that would otherwise require specialized, manual effort—allowing developers to focus purely on the logic, readability, and architecture of their smart contracts, rather than the complexities of gas optimization.

Our future plans are even more ambitious: once we eliminate the dependency on FunC and transition to direct compilation into assembly, we'll unlock even deeper and more powerful optimization possibilities. This will further widen the performance and efficiency gap between Tact and alternatives like Tolk.

When it comes to features, Tact is already well ahead of Tolk. From day one, Tact was purposefully designed to provide developers with a smooth and intuitive experience, rich tooling, and the ability to effortlessly create maintainable, secure, and scalable smart contracts. Our upcoming release—Tact 2.0—scheduled for later this year, will further enhance this foundation, introducing even more innovative features, optimizations, and architectural improvements.

While Tolk is also moving towards better usability and feature enhancements, Tact's inherent design principles and dedicated roadmap position it uniquely to remain the leading choice for TON smart contract development.