tlb схема из стандарта для перфекционистов

https://github.com/the-ton-tech/TEPs/blob/tokenized-vaults/text/0000-tokenized-vaults.md
https://github.com/ipromise2324/TEPs/blob/tep-vault-standard/text/0524-vault-standard.md
а какой стандарт вам нравится больше? Не с точки зрения качества проработки документации, а с точки зрения структур и методов.

Если переживаете — это нормально, но помните: мы уже проходили через такое, и не раз. Рынки цикличны, и после каждого падения они восстанавливались.

Мы строим долгосрочный продукт, и наша работа не зависит от дневных колебаний рынка. То что мы делаем — остаётся ценным и в +30%, и в -30%.

В выходные отдохните, перезагрузитесь. В понедельник продолжим строить. Всё будет хорошо 💪

еще вопрос к уважаемой публике.
вот есть жетон у которого в трансфере написано "трансферни 100 едениц васе", а в нотифае васе написано "петя прислал вам 90 едениц".
что делать с таким жетоном?

Сделал форк библиотеки go-tree-sitter (не мейтейнилась год), обновив все грамматики и добавил поддержку fift, func, tlb и tolk:

https://github.com/tonkite/go-tree-sitter

А расскажите в чем срач и причём тут интел sgx. Только с упором на техническую часть а не личности

никто так и не рассказал

где правда? кому верить?

я так понимаю речь про https://t.me/inetovsky/54

норм идея, мне нравится

ломай стандарты! все рамки у тебя в голове! сильная аура это сделать фис в жетон трансфере, слабая аура это бояться нарушить стандарт

🫧 Tolk v1.2: rich bounced messages, cheap deployment, and a breaking change that you'll love

Tolk v1.2 is here, aligned with TVM 12 — bringing new assembler instructions that make contracts cheaper and cleaner.

This update introduces one breaking change, several powerful new capabilities, and a few quality-of-life improvements across the compiler.

✅ Notable changes in Tolk v1.2:

1. Breaking change: address is now "internal only"
2. Rich bounces: not 256 bits, but the full body on bounce
3. Cheap builder-to-slice, StateInit, and address composition
4. Improved compilation errors
5. Anonymous functions (lambdas)
6. Borrow checker to catch undefined behavior

PR on GitHub with detailed info.

✔ `address` is now "internal only"

Before:
* address meant internal/external/none

Now:
* address — internal only
* address? (nullable) — internal/none, exactly like "maybe address" in @ton/core
* any_address — internal/external/none

In 99% of contracts only internal addresses are used. External ones are rare, and "none" can be expressed as nullable.

struct Storage {
    // internal, checked automatically
    owner: address
}

With new TVM 12 instructions, addresses are validated automatically during (de)serialization without extra gas — no more manual isInternal() checks.

So yes, it's technically a breaking change, but it removes a ton of noise.

A short migration guide, as well as technical details, available here.

✔ Rich bounced messages

Historically, a bounced message only returned the first 256 bits of the original body.

Now TVM 12 supports rich bounces — which lets you obtain the entire body instead.

createMessage({
    bounce: BounceMode.RichBounce,
    ...
})

In onBouncedMessage, you get access to the original body, exit code, gas used, and more.

Old true/false bounce flags still work for backward compatibility.

Rich bounces simplify complex message flows and inter-contract communication — one of the most painful aspects of TON until now.

✔ Cheap builder-to-slice and address composition

Previously, converting a builder to a slice (endCell + beginParse) consumed a lot of gas because cells are expensive. Now there's a new instruction — BTOS (builder-to-slice) — without intermediate cell creation.

- b.endCell().beginParse() is now cheap: auto-optimized to BTOS
- "builder-to-address" is the same BTOS; hacks around "return a builder with a valid address" can be removed
- cheaper StateInit hashing and address calculations

Just update to Tolk v1.2 + TVM 12, and you'll immediately save gas.

✔ Anonymous functions (lambdas)

Can be used in general-purpose frameworks, perfectly integrated with the type system:

fun customRead(reader: (slice) -> int) { ... }

customRead(fun(s) {
    return s.loadUint(32)
})

✔ Low-level compiler enhancements

Also included: better diagnostics with precise ranges, new peephole optimizations, tuple ↔ object conversions, and multiple small fixes. A lightweight borrow checker prevents undefined behavior on concurrent mutations.

As always, all additions are carefully described in a PR.

🌳 We've also started improving TVM itself — new assembler instructions are designed specifically to fit the Tolk type system and optimizer. I have always said: the language is just the beginning. Perfect developer experience requires improving every layer of TON's stack. The road may be sharp and curvy — but we're definitely heading in the right direction.

📚 New TON Documentation is Live

We rebuilt the entire documentation from scratch based on community feedback.

What's new:

▪️ AI Assistant - Ask questions in plain language and get instant answers from the entire documentation

▪️ Easier Navigation - Flat structure rewritten by blockchain engineers

▪️ Comprehensive Guides - New content for blockchain foundations, TON Connect, mytonctrl, Sandbox, Blueprint, smart contracts, and more

▪️ Dr. Durov's Whitepapers - Now in web format with AI summaries and cross-links

Built with feedback from Zengo, RSquad, TonTech, TON API team, TON Core, and shaped and delivered by TON Studio.

Try it: docs.ton.org 

👉 Read more

А что вы об этом обо всем думаете?

База???

Ну допустим сделали мы что если сумма отличается то мы пишем не JettonTransfer, а JettonUebanTransfer FlawedJettonTransfer. Но теперь вопрос: а что делать если сумма одинаковая, но жетон меняет форвард пейлоад?
Надо ли написать что это трансфер не соответствующий стандарту?
За примером ходить далеко не надо.🙄

покушение на мемпад бидаска

Отсылки на токены с налогами?)

New for TON devs: Deep Smart Contract Audit Skill

A new audit skill for TON smart contracts is now live — powered by TON Symbolic Analyzer (TSA) and combining LLMs with formal methods.

What is TSA?
A symbolic execution engine that simulates contract behavior across many possible states to uncover non‑obvious bugs.

What the skill does:

• Explores real execution paths
• Analyzes smart contract code at the bytecode level
• Detects critical issues:
– Unauthorized fund withdrawal scenarios
– Incorrect handling of bounced messages
– Replay attack vulnerabilities

• Generates test cases
• TSA enable deep analysis for higher security coverage.
• Produces a structured audit report

⚙️ It is free and powerful smart contract audit skill for all TON developers!

More details:
🔗 https://tonsec.dev/smart-contract-audit-agent
Includes a case study showing how it reproduced a real DEX vulnerability.