Anton Trunov

Nice stuff! Btw, does it also specify TVM instructions' side-effects/exceptions and such? (I mean to provide the full semantics of an instruction, in addition to its stack types)

Awesome! Thanks for sharing

@delovoyhomie The Tact team has checked the spec and it all looks good to us. I think the bounty should be paid and any issues that will arise we can...

> Therefore, I don't think it's feasible to expect Tact there. So we should just continue to improve the docs. Perhaps, the "primer" ("tour" or "overview", to be determined) page...

Closing this, since we have the corresponding issue in tact-docs

Great! Looking forward to it.

Some issues observed in FunC, many could be applied to Tact as well: https://github.com/slowmist/Toncoin-Smart-Contract-Security-Best-Practices/blob/main/README.md

A post by CertiK: https://blog.ton.org/secure-smart-contract-programming-in-func

The Tact Telegram chat interactions show people still have some issues with using the `dump` function, for instance they expect adding `dump` to their contracts and running tests would automatically...

One more issue our users experience with `dump`: how to use it with Blueprint. > When creating a new blueprint project I don't have a default tact.config.json file. I created...