🎉 Misti 0.3 has just landed on NPM!

⚡️Tact 1.5 Support

🔍 Five New Tact Detectors: String Receivers Overlap, Asm Is Used, Preferred Stdlib API, Inherited State Mutation, Argument Copy Mutation.

🔧 Fixes & Enhancements: More configuration options, optimization and API improvements. Check out the full changelog.

♨️ @tact_kitchen

🎉 Tact 1.5.2 has just landed on NPM!

Remember, that we've introduced asm functions in version 1.5.0 for you to write TVM assembly right in your Tact code?

asm fun keccak256(s: Slice): Int {
    1 INT HASHEXT_KECCAK256
}

🐞 With this bugfix release, you now can use full* range of its syntax just like you could in similar asm functions of FunC. Just don't do anything too crazy, like trying to shadow (re-define) { or }, or using char } inside your newly defined instructions.

Other than that, have it your way. Note, that support of full Fift+TVM syntax is highly experimental, and will be reworked in future releases, in particular the following works now, but most likely won’t work at some point:

fun onchainSha256(data: String): Int {
    _onchainShaPush(data);
    while (_onchainShaShouldProceed()) {
        _onchainShaOperate();
    }
    return _onchainShaHashExt();
}

// Helper assembly functions,
// each manipulating the stack in their own ways
// in different parts of the `onchainSha256()` function
asm fun _onchainShaPush(data: String) { ONE }
asm fun _onchainShaShouldProceed(): Bool {
    OVER SREFS 0 NEQINT
}
asm fun _onchainShaOperate() {
    OVER LDREF s0 POP CTOS s0 s1 XCHG INC
}
asm fun _onchainShaHashExt(): Int {
    HASHEXT_SHA256
}

🐞 Additionally, all new installations of @tact-lang/compiler or @ton/blueprint via npm should work as expected. All other package managers continue to work fine, so create more awesome projects! We'll handle the rest ❤️

👀 And keep an eye on the docs, something big might happen very soon!

🍲 every contract is open source if you can read bytecode
♨️ @tact_kitchen

👏 Huge 👏 Revamp 👏 of Tact 👏 Docs 👏

There were a lot of things we just couldn't do nicely with the previous documentation library, Nextra. Granted, it's very good and has a lot going for it, but its rigidity in important places, as well as its overall pull towards Next.js and Vercel make some features like i18n almost impossible to implement while keeping the static build and not doing the server-side rendering.

It is finally time to move to a more flexible solution: Starlight, a documentation library powered by Astro that allows for great extensibility and bundles (among other things): advanced i18n support via i18next, site navigation, search, SEO, easy-to-read typography, code highlighting, dark mode and more. It's also very lightweight and snappy.

This move brought a lot of enhancements, here's a very short list (there's more!):

0️⃣ Translating the docs to another language (i18n) is super easy now. Just take the original English page, translate it, and put the file in the appropriate folder. That's it, the next deployments would feature your translated page as if it was always there ✨

1️⃣ The search via Ctrl + K (fuzzy full-site search) has been greatly improved. In addition, since all the pages are located in the sidebar, you now can use Ctrl + F (content search) to quickly find the page in any of the sections: Book, Cookbook, and Ecosystem!

2️⃣ Fixed issues with highlighting of code blocks in the light mode. The similar change for inline code highlighting will follow in the future too!

3️⃣ tact-docs repo has been merged into the Tact compiler one, which means that all new feature and standard library updates will arrive in docs much faster than before! Besides, you'll see badges like "Since version X.Y.Z" under each new feature, so that you'll know when to expect things and which Tact version to use for them :)

Things that didn't make the list include updates that are mostly relevant to the team and maintainers of the docs. For example:

1. It's much easier to influence the SEO of each page with good denoscriptions and image covers where needed
2. It's super easy to customize the docs with: CSS styles, JS noscripts, Markdown pre-processing plugins, HTML pre-processing and post-processing plugins, ...
3. ...and so on and so forth

🧑‍🍳 Contributor: Novus Nota
🐙 Implementation: #880
✈️ Delivered: docs.tact-lang.org

🍲 sparkle! sunshine!
♨️ @tact_kitchen

⚡️ Added destructuring statements

It's a concise way to unpack Structs and Messages into distinct variables, which mirrors the instantiation syntax:

// Definition of Example
struct Example { number: Int }

fun basic() {
    // Basic syntax of destructuring assignment
    // is shown on the left of "=":
    let Example { number } =
        Example { number: 42 };

    // The syntax above is roughly equivalent
    // to the following statements:
    let example = Example { number: 42 };
    let number = example.number;
}

One can also create bindings under different variable names or ignore some of the fields. Note, that the order doesn't matter:

// "first" goes first, then goes "second"
struct Two { first: Int; second: String }

// a helper function
fun makeTwo(): Two {
    return Two {
        first: 42,
        second: "yee-haw",
    };
}

// 👀
fun totalDestruction() {
    // The "first" field is ignored,
    // while the value of "second"
    // is bound under the "cowboy"
    // variable from now on:

    let Two {
        second: cowboy,
        first: _,
    } = makeTwo();
}

🧑‍🍳 Contributors: Gusarich, Novus Nota (docs)
🐙 Implementation: #856
🍽 To be released in: v1.6.0

🍲 everyone within a 100 mile radius after you eat a taco
♨️ @tact_kitchen

⚡️ Added automatic links to Web IDE from code blocks in Cookbook section of the docs

Did you know, that just like the Remix for Ethereum, TON has an official Web IDE? If not, take a quick look at what it offers:

• Tact and FunC project creation
• Code highlighting and snippets for Tact and FunC
• Semi-automatic Build → Deploy pipeline on every save
• Convenient buttons to call getters and send messages to deployed contracts
• Deploy to Sandbox, testnet and mainnet
• Share button ↗️ on every file in a file tree
• ...plus a lot more!

And now any code samples from the Cookbook are right at your fingertips — just press the "Open in Web IDE" button, and the contents of the code block would automagically transfer to Web IDE!

🧑‍🍳 Contributor: Novus Nota
🐙 Implementation: #994
✈️ Delivered: docs.tact-lang.org/cookbook

🍲 «What's the TTP of Web IDE?»
♨️ @tact_kitchen

🎉 Misti 0.5 has just landed on NPM!

🔍 More Tact Detectors: Covered Tact-specific issues like CellOverflow, SuspiciousMessageMode, UnboundMap achieving totally 25 detectors.

⚠️ Warning Suppressions: Suppress specific warnings using // @misti:suppress DetectorName comments.

💡 Usability Enhancements: Install Misti with a single command and run it on the directory containing your contracts—no extra configuration required:

npm install -g @nowarp/misti
misti path/to/src/contracts

🔧 Fixes & Enhancements: More configuration options, optimization and improvements. Check out the full changelog.

♨️ @tact_kitchen

⚡️ Watch Tact & DevTools talk from 2nd day of TON Gateway
🌀 It's a whirlwind tour of progress made in Tact and ecosystem, plus the plans for the future!

🎞 If loading the video on Telegram is too much, start watching at the timestamp on YouTube
👀 For more, see the full recording of TON Gateway | Day 2

🍲 tactical advantage, strategic dominance
♨️ @tact_kitchen

❤️ A warm welcome to listeners of good podcasts @tonpizdev
♨️ @tact_kitchen

⚡️ Heads-up: there are more than 2100 Tact source files on GitHub, not counting forks and the tact-lang organization!

It would be nice to get Tact code highlighted there, don't you think? That's why we've made a PR to Linguist, a language detection and highlighting library from Github.

Here's how you can help:
1. Go to the PR
2. Leave your 👍 without writing any comments, to keep PR clean
3. Keep writing nice open source contracts in Tact 🙌
4. Wait for the best 🤞

This is not a drill. I repeat: this is not a drill.
This is the beginning of the story.

UPD: ❤

🍲 our story, actually
♨️ @tact_kitchen

❤️ Thanks, folks! We really appreciate that!

🍲 melting hearts
♨️ @tact_kitchen

⚡️ Added a page on security best practices to the documentation

There are several anti-patterns and potential attack vectors that Tact smart contract developers should be aware of. These can affect the security, efficiency, and correctness of the contracts.

With the help of community contributors, we've discussed the do's and don'ts specific to writing and maintaining secure Tact smart contracts, and written a cohesive page for you!

🧑‍🍳🎉 Community contributors: PixelPlex and Aliaksandr Bahdanau
🐙 Implementation: #1070
✈️ Delivered: docs.tact-lang.org/book/security-best-practices

🍲 where did the bad actor go? they ran somewhere
♨️ @tact_kitchen

⚡️ Added DeDust and STON.fi cookbooks to the documentation

Ever wondered how to build your own Decentralized EXchange? Neither have I!

However, documentation on how to interact with existing DEXes from Tact was highly requested — and, with the help of community contributors, we wrote it. Read how to swap Toncoins for Jettons, Jettons for Jettons, and provide liquidity to pools of DeDust and STON.fi, all with ⚡️ Tact.

🧑‍🍳🎉 Community contributors: PixelPlex and Aliaksandr Bahdanau
🐙 Implementations: #954, #956
✈️ Delivered: DeDust, STON.fi

🍲 decentralized surprise liquidity provision
♨️ @tact_kitchen

⚡️ Completely overhauled exit codes page in the documentation

Sometimes pages in the Tact documentation are more detailed than you'll find elsewhere. The exit codes page is a case in point.

Not only do you get a comprehensive denoscription of what exit codes are, how they are defined, and which ones are reserved, but you also get a handy table of them with short denoscriptions and quick navigation to each exit code in the table of contents. Since each of the exit codes has its own headings, linking to a specific exit code is easier than ever!

In addition, all denoscriptions of compute phase exit codes show examples of how you might encounter them. And sometimes even help you to anticipate and avoid them.

By the way, for exit code 50 (not listed anywhere else), we've also described the current limits on config param 43 related to account state, max number of bits and cells in messages, and much more.

🧑‍🍳 Contributor: Novus Nota
🐙 Implementation: #978
✈️ Delivered: docs.tact-lang.org/book/exit-codes

🍲 code: dismissed
♨️ @tact_kitchen

⚡️ GitHub supports Tact!

Now that you've clicked, let me clarify — thanks to our efforts, your support and all of you writing lots of smart contracts, Tact now has syntax highlighting all across GitHub!

— Files with a .tact extension? Boom, colored.
— Blocks of code in markdown that specify tact as their language? Got you covered.

❤️ Thanks everyone for your support and love! Without you, there would be nothing. Literally.

✈️ We're continuing to ship awesome stuff for you — expect many shiny things this December.

🍲 growth is inevitable
♨️ @tact_kitchen

🎉 Misti 0.6 has just landed on NPM!

🔍 More Tact Detectors: CellBounds which covers both CellOverflow and CellUnderflow, ExitCodeUsage, EtaLikeSimplifications and ShortCircuitCondition.

⚙️ More Tools: Added Callgraph that tracks function effects and is useful for auditing contracts.

🌐 Better Integrability: Misti can run in browser environments.

🔧 Fixes & Enhancements: Check out the full changelog.

♨️ @tact_kitchen

⚡️ Added an assembly functions page to the documentation

👉 Covering all your needs and going beyond:
▪️ Eh, what are TVM instructions anyways?
▪️ Sure, they're used in asm functions of Tact, but what's the syntax and stuff?
▪️ Stack registers, what's that?
▪️ Fine, but what if I want to re-arrange parameters or return values?
▪️ Limitations? Caveats?
▪️ How would I debug all that?
▪️ Can I apply some attributes?
▪️ Got any examples?

🧑‍🍳 Contributor: Novus Nota
🐙 Implementation: #1061
✈️ Delivered: docs.tact-lang.org/book/assembly-functions

🍲 there are 11 types of programmers: ROT, -ROT and BRAINROT
♨️ @tact_kitchen

🎄 Merry Christmas, Folks!

As we wrap up 2024, it's time to celebrate all that we've accomplished together.

🚀 Adoption, Features and Tooling

Your biggest achievement this year was getting GitHub to support Tact on the entire website! We say you, because it wouldn't have been possible without you writing contracts, finding and reporting bugs & suggestions, and supporting Tact elsewhere ❤️

Regarding features and compiler updates, there were so many, that Tact has practically been reborn into a fresh, secure, easy and accessible language language for complex smart contracts, quick onboarding and fast prototyping.

In terms of tools, an awesome static analyzer Misti raised from 0 to hero: with over 25 issue detectors, CI/CD and Blueprint integrations. Additionally, the tree-sitter-tact and many editor packages and highlighting plugins were frequently updated to keep up with compiler updates.

📚 Documentation

Working on the clearest and most comprehensive documentation, we often had to dig deep into TON sources and discover what was really going on under the hood. And it was and is very worth it: the exit codes and assembly functions pages are the most vivid proofs.

We try to cater to both the experienced professionals and beginners on TON Blockchain, which is why you can expect more in-depth research of TVM, more production-ready examples of common contracts in Tact, and an even more streamlined onboarding experience ✈️

🐞 Bugfixes

The release 1.4.1 in particular squashed so many bugs, that the security audit of 1.5.0 went silky smooth — no critical vulnerabilities found, as announced on TON Gateway.

As for the next release, we're fixing the internal representation of Address type, reworking the type system to support more TVM types with the most safety and convenience, and making rapid strides to reduce the gas consumption 🛠

🎁 A Small Holiday Request

Finally, we have a small holiday wish: If you’ve enjoyed our progress this year, consider gifting us a GitHub star. It’s a simple gesture, but one that means the world to us. Your support helps Tact grow and reach even greater heights.

🎅 Happy holidays from the Tact team!
❤️ Take care, get some well-deserved rest and prepare for 2025 — we've got big plans for the next year

🍲 sparkling future ahead
♨️ @tact_kitchen