FunC updates

New versions of func-js-bin (0.4.3) and func-js (0.6.1) have been released.

Here is the official changelog for FunC version 0.4.3 - link

The only change of note in func-js is that it now contains this latest version of FunC.

To update func-js (if you use it as a CLI tool), run npm install @ton-community/func-js@latest -g

TON tooling roadmap 🔥

Hey guys!
We have launched a discussion about some features that could be implemented into the tools that we have developed.
Please come see them and participate here.

Blueprint dependency update

blueprint v0.9.0 has just been released, it includes dependency updates:
- func v0.4.3
- tact v1.1.1

Please note that this release is not yet included in create-ton, and so for now you will have to update blueprint manually when creating new projects.

New sandbox release!

sandbox v0.9.0 has been released. It contains two new features:
- A gas usage helper, printTransactionFees, that you can call on an array of transactions acquired from a sandbox execution, to help you calculate the fees of your operations
- Snapshots for Blockchain and SmartContract. Here's how to use them:

const snapshot = oldBlockchain.snapshot()
const newBlockchain = await Blockchain.create()
await newBlockchain.loadFrom(snapshot)

These features were discussed in our community prior to their release, so join us, if you want to discuss other stuff!

🔨Dev tools updates

sandbox v0.10.0
- New executor WASM binaries taken from the artifacts of this commit
- New treasury code which fixes some interactions between snapshots and treasuries

create-ton v0.4.0
- Updated template readme
- Changed template jest config to use TypeScript
- Updated blueprint and sandbox to latest versions

🔨Dev tools updates

sandbox v0.11.0
- Added the ability to emulate ticktock transactions
- Added new verbosity levels
- New emulator WASM binaries taken from the artifacts of this pipeline

Please see the changelog for more details

func-js update

A new version of func has been released (official release notes), so we've updated func-js-bin (v0.4.4) and func-js (v0.6.2). The only change is that they now ship func v0.4.4

Beta dev tools for the upcoming TVM update

The testnet branch of the official TON repo contains a lot of new opcodes, and we have released new tools to help you test them out before they reach mainnet. The new versions are as follows:
@ton-community/sandbox@0.12.0-tvmbeta.1 @ton-community/func-js@0.6.3-tvmbeta.1 @ton-community/func-js-bin@0.4.5-tvmbeta.1

Please note that the actual func version in the func-js-bin package is still 0.4.4

Also, the updated sandbox only includes the updated emulator binary, but lacks some interface updates - for example, there is currently no way to set the information required for the new opcodes PREVBLOCKSINFOTUPLE, PREVMCBLOCKS, PREVKEYBLOCK

The interface will likely be updated when the update reaches mainnet, or sooner if there is demand for that.

Also note that the default and slim configs packaged with sandbox are deliberately changed to enable the new TVM opcodes and will not match the ones that are actually contained in the blocks indicated by the seqno consts.

If you want to use the new opcodes in blueprint, you also need to override func-js versions. To do so, add the following to your package.json:

"overrides": {
    "@ton-community/func-js-bin": "0.4.5-tvmbeta.1",
    "@ton-community/func-js": "0.6.3-tvmbeta.1"
}

(change overrides to resolutions if you're using yarn)
Note that sandbox can be updated in the usual way by replacing the version in the devDependencies section directly.

New value_flow for burning fees in block.tlb

In testnet, the block.tlb scheme has changed and new blocks and config may not be decoded by the old libraries. Please update your libraries.
For example tongo should be updated to version v1.1.1

🔨Dev tools updates

blueprint v0.10.0
- Added two optional fields to the CompilerConfig: preCompileHook?: () => Promise<void> and postCompileHook?: (code: Cell) => Promise<void>. The former one gets called before any compilation of the respective contract happens, the latter one - after any compilation with the compiled code cell (they are called both during the build command and when calling the compile function for the respective contracts)
- Changed the run command to only show .ts noscripts

create-ton v0.5.0
- Updated template's blueprint to 0.10.0, sandbox to 0.11.0
- Changed template's jest config to ignore the dist directory

🚀 Join TonTech and shape the future of TON blockchain development!

We're hiring developers to build cutting-edge tools and SDKs. Work with the latest blockchain technology, collaborate in a dynamic environment, and access empowering resources.
Make an impact on the TON community.

Contact us: @Narek

Hey guys! A while ago, we started improving the previously unfinished TON Ledger App, and we are now close to the finish line! It's still not released and may require some further improvements, but you can check out its development branch here. One of the main new features is the support for the upcoming Ledger Stax device. Please also see the attached screenshot of the new UI.

Hey guys!

If we happen to have Rust developers with TON experience in subscribers: we have a small task for you, write about yourself in the comments.

🔨Dev tools updates

blueprint v0.11.0
- Added an options field to the tact variant of CompilerConfig, which is of the same type as the options of the TACT compiler, and includes fields such as debug, experimental, etc
- Updated TACT to 1.1.3

Hey everyone!

Last month, we dedicated our efforts to researching large collections on TON, and we have some exciting developments to share with you.

Let's start with some context: TON's asynchronous architecture naturally leads developers to use sharded architectures for their smart contracts. This also holds true for the current NFT standard in TON, where each NFT is represented as a separate smart contract. While this approach helps distribute the load on smart contracts, it presents some challenges for developers:

1. Deployment of an NFT collection with 1 million items results in the deployment of 1 million + 1 contracts.
2. Managing multi-NFT operations becomes a significant challenge.

However, we didn't let these challenges deter us. Our team has worked hard to find an innovative solution that allows for the deployment of extremely large collections of NFTs at a very affordable cost. While doing it entirely on-chain proved impractical, we found an excellent compromise by combining on-chain and off-chain storage of data.

Here's the basic idea: we introduce a new state for NFTs, which we call "virtual NFTs." The data for these virtual NFTs, including ownership and metadata, is stored off-chain, while on-chain, we keep a Merkle tree root containing all the NFTs in the collection. When the first transfer of a virtual NFT occurs, it gets minted on-chain, and from that point forward, it becomes indistinguishable from classical NFTs.

This approach offers numerous benefits:

1. Creation of truly massive collections, even up to 1 billion items.
2. Collection deployment comes at a fixed price, independent of its size.
3. Collection deployment costs are incredibly low, akin to deploying a normal empty collection (almost free).
4. The "claiming" of virtual NFTs is very affordable, comparable to a standard transfer.
5. Full compatibility with the existing NFT standard and mechanics.
6. The implementation on marketplace platforms is relatively straightforward.

We are thrilled to announce that today we have published this new approach as the Compressed NFT Standard. Alongside this, we have released reference contract implementations and an off-chain storage server. We eagerly await your feedback and comments on our standard draft.

Thank you for your continuous support, and let's work together to shape the future of NFTs on TON!