🔨 Assets SDK Launch

We are excited to announce the release of the Assets SDK for interactions with Jettons and NFTs.

👥 @ton-community/assets-sdk v0.0.4
• Works on servers, browsers, and CLI.
• Deploy, mint, and transfer with ease.
• Fetch and upload data effortlessly.
• Compatible with custom contracts.
• Integrates with TON Connect and Blueprint.
• Serialization/deserialization of messages.
• Parses transactions for contract actions.

⬇️ To install, run npm install @ton\-community/assets\-sdk.

💡To learn more, visit the GitHub page at https://github.com/ton-community/assets-sdk.

💬 Encountered issues? Please report them on GitHub at https://github.com/ton-community/assets-sdk/issues.

🎁 Your feedback and usage examples are crucial. Share your experiences to help us evolve the SDK!

🔨Dev tools updates

blueprint v0.16.0
- Custom network may now be specified in the config (see the readme!)
- Improved verify command
- New convert command to convert legacy build scripts into blueprint compile files
- Added the ability to pass user data into compile hooks

TON is now in popular package managers

Developers can now install a TON binaries and libraries (func, fift, lite\-client, proxy and other) via apt install (Ubuntu, Debian, Linux Mint), homebrew (Mac), yum install (RedHat, Fedora, CentOS), pamac (Manjaro, RebornOS, Arch Linux) and chocolatey (Windows).

Available on x86-64 and aarch64 (arm64) platforms.

Installation commands and description »

We remind you that you can also download TON binaries for Linux, Mac and Windows from GitHub Autobuilds, or compile it yourself from sources (docs).

Thanks to Neodix for the continuous improvement of the TON build systems.

🔨 Dev Tools Updates

Throughout Q4 2023, working alongside Telegram, Wallet, Tonkeeper, Getgems, and TON Diamonds teams, we proudly announce the stable release of TON Connect UI 2.0.0.

This release greatly improves user interaction with Telegram Mini Apps and resolves numerous issues, offering the best TON Connect UI experience to date!

👥 @tonconnect/{ui-react,ui} v2.0.0
• Quick browser-to-Telegram transitions without extra tabs.
• Enhanced UX with TON Space on Telegram devices.
• Multiple Safari and Privacy Mode fixes.
• New no-bounceable address format.
• Optimized application loading speed.
• Back button handling for Android, discreetly hiding modal windows.
• Plus over 50 additional enhancements and fixes.

🙂 Experience it yourself using these links:
• https://ton-connect.github.io/demo-dapp-with-wallet for browsers.
• https://t.me/tc_twa_demo_bot/start for Telegram Mini Apps.

⬇️To learn more about TON Connect UI 2.0.0, visit GitHub page at https://github.com/ton-connect/sdk.

💬 Encounter issues? Please report them on GitHub at https://github.com/ton-connect/sdk/issues.

🎁 Special thanks to the collaborative teams for their invaluable assistance in making these enhancements possible.

🔨Dev tools updates

sandbox v0.15.0
- Changed the default and slim network configs to use the latest network config at the time of release, which enables new TVM opcodes by default

The TON Development plugin is back on JetBrains Marketplace

After temporary suspension and 1-month negotiations, the TON Development plugin returns to the marketplace. The JetBrains team changed the pluginID, so it's necessary to reinstall it from the marketplace.

Update instructions:
1. Remove the old version
2. Restart WebStorm (or IDE you use)
3. Install the new version

Click here to access the plugin.

🔨Dev tools updates

blueprint v0.15.0
This release improves custom API capabilities. Please consult blueprint help run to see detailed flag descriptions.
- Added flags \-\-custom\-version, \-\-custom\-key, \-\-custom\-type to run and verify commands to allow better control over custom API behavior
- \-\-custom now always adds jsonRPC to API URL for v2 APIs
- Fixed argument handling

TonTech NFT Royalty standard contest
Hey everyone! We're excited to reveal the results of the NFT Royalty Standard contest. We received four submissions, but unfortunately, none of them met our expectations in terms of proposal quality. Here's a detailed review of each project:

1. hitaspdotnet's solution:

- The solution lacks a guarantee on the size of royalties paid.
    - Its architecture opens up possibilities for scam use cases.
    - Involves too many transactions (4) for a single transfer.
    - Does not align with the current NFT standard and violates the transfer operation.
    - Allows the NFT to be put on sale to multiple contracts due to the ability for multiple users to transfer it.

1. Roman22022000's submission:

- Unfortunately, we were unable to comprehend the ideas presented by Roman.

1. Ton-Dynasty's solution:

- Considered overcomplicated and lacking practicality in terms of royalty enforcement.

1. coalus's implementation:

- Although the idea is interesting, the problem remains unsolved as normal transfers still exist in this implementation.

In our internal research at TonTech, we've explored potential solutions and believe that a public whitelist of code hashes could be effective in ensuring the safe transfer of NFTs. 

This whitelist, which can be stored on-chain as Merkle proofs in the global config for decentralized control, contains contracts which are proven to be safe to transfer NFT to, like wallets, NFT sale contracts, etc.

This could be achieved by adding the state initialization of the new_owner contract to the transfer message with a proof verifying that the contract code is indeed on the whitelist. This approach allows the NFT to:

- Check the code against a whitelist.
- Verify that the state initialization leads to the correct new_owner address.

However, it's crucial to acknowledge a major drawback: we cannot guarantee the security of the solution if the new_owner contract is an updatable contract. This is particularly problematic since the contract code could be updated to become something else. Given that the wallet w5 contract is likely to be updatable, this solution poses inherent challenges.

Despite not finding a satisfactory solution in the contest, we would like to express our gratitude to all participants for their time and effort. Recognizing their contributions, we have decided to reward each participant with 200 TON for their commitment and dedication. We understand that the contest may not have yielded the desired outcomes, but we value the creativity and tenacity shown by the participants.

Let's continue exploring innovative solutions to address these complexities and enhance the security and reliability of NFT royalty enforcement.

🔨Dev tools updates

We have finally updated our create-ton template to use @ton packages, so you get all the latest features when creating a new project from the get-go!

(Please note that some versions were skipped, and the changelogs were collected from all the versions since the last mention in this channel)
blueprint v0.14.2
- Fixed test templates (added missing imports)
- Set tact compiler dependency to version 1.1.5

test-utils v0.4.2
- Added missing findTransactionRequired export
- Fixed the deploy flag in flat transactions

sandbox v0.13.1 (Most of the changes were made by our wonderful community, thank you!)
- Step by step execution (blockchain.sendMessageIter)
- Better docs
- blockchain.now is now honored in smartContract.receiveMessage
- Exit code 1 is considered a success in get methods
- Transaction emulation errors now result in EmulationError instead of being dumped into console
- Fixed RemoteBlockchainStorage error caching

create-ton v0.10.0
- Updated/changed template dependencies (blueprint, sandbox, test-utils, @ton/ton, @ton/core, @ton/crypto)

Do you like TLB?