现已上线！2025 年 Telegram 研究 — 年度关键洞察 
TON Builders
前往频道在 Telegram
TON Builders' Hub for developers, creators, and founders to connect, collaborate, and grow.
显示更多未指定国家技术与应用13 586
8 642
订阅者
-224 小时
-497 天
-20330 天
数据加载中...
吸引订阅者
六月 '26
六月 '26
+37
在0个频道中
五月 '26
+90
在1个频道中
Get PRO
四月 '26
+194
在21个频道中
Get PRO
三月 '26
+837
在58个频道中
Get PRO
二月 '26
+1 111
在42个频道中
Get PRO
一月 '26
+973
在81个频道中
Get PRO
十二月 '25
+1 294
在39个频道中
Get PRO
十一月 '25
+150
在4个频道中
Get PRO
十月 '25
+1 399
在31个频道中
Get PRO
九月 '25
+333
在8个频道中
Get PRO
八月 '25
+461
在8个频道中
Get PRO
七月 '25
+300
在11个频道中
Get PRO
六月 '25
+1 529
在72个频道中
Get PRO
五月 '25
+46
在1个频道中
Get PRO
四月 '25
+2 319
在5个频道中
| 日期 | 订阅者增长 | 提及 | 频道 | |
| 24 六月 | +1 | |||
| 23 六月 | +3 | |||
| 22 六月 | +4 | |||
| 21 六月 | +2 | |||
| 20 六月 | +1 | |||
| 19 六月 | 0 | |||
| 18 六月 | 0 | |||
| 17 六月 | +2 | |||
| 16 六月 | +4 | |||
| 15 六月 | +2 | |||
| 14 六月 | 0 | |||
| 13 六月 | +1 | |||
| 12 六月 | 0 | |||
| 11 六月 | +4 | |||
| 10 六月 | +2 | |||
| 09 六月 | 0 | |||
| 08 六月 | +1 | |||
| 07 六月 | 0 | |||
| 06 六月 | +3 | |||
| 05 六月 | +1 | |||
| 04 六月 | +1 | |||
| 03 六月 | +1 | |||
| 02 六月 | +3 | |||
| 01 六月 | +1 |
频道帖子
📣 Community Update
As the TON ecosystem evolves, so does the way we come together! We're consolidating channels to keep conversations more active and connected. As a result, this channel will be closing and joining the main TON community.
Getting the latest updates, connecting with the wider community, and getting support just got easier.
Stay Connected:
🔊 News & Updates
TG: TON Dev News, Toncoin, TON Community
X: TON 💎, TON Community
LI: TON Foundation | LinkedIn
GH: TON Blockchain
💬 Community Groups
TG: TON Dev Eng, Toncoin Chat, TON Community Chat
Thanks for being part of this space. See you on the other side! 🤝
YouTube | TON.org
| 2 |  🚀 The AI Hackathon review period has been extended until April 3.
The results exceeded all expectations: over 160 submissions, 4x the previous contest.
The volume and variety of projects submitted have genuinely impressed us. A strong mix of thoughtful, creative, and technically impressive work from across the ecosystem.
We definitely didn’t expect that. So, we are extending the review period to April 3 to ensure we have enough time to review every submission thoroughly.
While you wait, two new features just dropped on the Identity platform:
🔹Makers. Add your teammates to submission. Everyone gets the participation badge.
🔹Comments. Talk about projects. Feedback, questions, discussion, all on submission pages.
Thank you for the energy, creativity, and effort you brought to this hackathon.
Keep building! ✨😎
TON Community | TON Builders | TON Dev News | TON Hubs | X | YouTube | LinkedIn | TON.org | 0 |
| 3 | 🫧 Tolk v1.3: moving toward a general-purpose language
After the previous post, this release may feel less surprising — but still a bit unusual.
The reason is simple: Tolk is no longer evolving only as a contract language. It is becoming a foundation for the toolchain I described earlier.
This release focuses on features beyond contracts — introducing general-purpose capabilities needed for libraries and frameworks.
✅ Notable changes in Tolk v1.3:
1. Type array<T> — dynamically sized arrays backed by TVM tuples.
2. Type unknown — a TVM primitive with unknown contents.
3. Type lisp_list<T> — nested two-element tuples (FunC-style).
4. Type string — text chunks backed by snaked cells, with StringBuilder for concatenation.
5. Compile-time string methods: "str".crc32(), "str".sha256(), etc.
6. Null coalescing operator — ?? like in TypeScript.
7. Import path mappings — import "@third_party/utils".
8. Compile-time reflection via @stdlib/reflection.
9. Custom serializers now support structures and generics.
10. The compiler now reports multiple errors at once.
11. Focused on stability — fixed dozens of minor issues found by LLM fuzzing.
12. Extensive internal refactoring towards being stateless and multi-threaded.
PR on GitHub with detailed info.
✔ Arrays: redesigned tuples
Working with TVM tuples has been fully redesigned. There is now array<T> — a dynamically sized container:
// array<int>
var numbers = [1, 2, 3];
// array<Point?>
var optPoints = [
Point { x: 10, y: 20 },
Point { x: 30, y: 40 },
null,
];
- methods push, get(idx), etc.
- any T, including sub-arrays like array<array<int>>
- automatically serialized into snake cells
- max size: 255 (TVM limitation)
✔ The `unknown` type
Raw TVM tuple exists, but it's no longer built-in. It's just an array... of something unknown:
type tuple = array<unknown>
The unknown gives access to the untyped TVM stack, fully integrated into the type system.
✔ The `string` type
TVM has no strings — only binary slices. Strings were always just a convention over binary data.
Now Tolk has strings built-in.
// string
val str = "hello";
- strings are cells (not slices)
- long strings are snake cells under the hood
- methods calculateLength, equalTo, etc.
- on-chain/off-chain encoding for jettons and NFTs to comply with TEPs
StringBuilder encapsulates cell manipulation:
StringBuilder.create()
.append(content.commonContent)
.append(individualNftContent)
.build()
By the way, compile-time functions now look cleaner: "str".crc32() and so on.
✔ Import path mappings
The import statement now accepts @aliases:
import "@common/jettons"
import "@third_party/math-lib"
This is similar to widely used path mappings in TypeScript.
✔ Compile-time reflection
Many additions in v1.3 make sense not for contracts, but for frameworks. For example, take a look at one of reflect features:
fun log(msg: string, loc: SourceLocation = reflect.sourceLocation()) {
debug.print(loc.lineNo);
}
fun demo() {
log("a"); // prints K — current line no
log("b"); // prints K+1
}
Why is this useful? It allows errors to point to the original call site — for example, expect(...) in tests — by carrying source location at compile time.
⚙️ A huge portion of internal refactoring
A lot of work has been done inside the compiler core, peephole optimizations, and memory management.
Final result: tolk compiler is now thread-safe and re-invokable within a single process. It will be embedded into an external toolchain written in Rust, communicating via FFI.
... And more
Dozens of independent improvements. Combined, they cover the requirements not only for contracts, but for abstract libraries and the upcoming toolchain.
Feel free to check the description on GitHub.
🌳 And one more thing! Wallet-v5, compiled with Tolk v1.3, reduces gas usage by 30% compared to FunC. As of Tolk v1.0, the savings were "only" 20%. Take a look at new benchmarks. | 0 |
| 4 | 💎 Tolk v1.3 is live — expanding scope beyond smart contracts
Tolk is evolving into a general-purpose language, enabling the next layer of TON tooling:
• Library development
• Framework support
• Developer tooling infrastructure
This release lays groundwork for a more complete development stack on TON.
TON Core team is improving developer experience with focus on onboarding, usability, and tooling consistency.
More technical updates will follow.
👉 Start building on TON
TON Community | TON Hubs |X | YouTube | LinkedIn | TON.org | 0 |
