Weekly Development Progress
We have not published progress updates for a while. Time to fix that.
Even though we are not moving as fast as we would like, we can still share some of what has been done.
If you are not a developer, you can skip the first 2 points.
1. Multiple Cryptography Types
We had a problem: post-quantum cryptographic algorithms are not fast enough in the browser environment.
Since the first public release is planned for browser and desktop, it was important for us to support JavaScript, which is relatively weak for heavy cryptography.
We decided to allow both users and developers to choose between different options in the protocol:
- ECDH for browser / weaker devices, or post-quantum ML-KEM
- Ed25519 or post-quantum ML-DSA
This will apply both to the connection itself and to the messages.
2. JavaScript SDK
Right now we are working on the SDK for the web application.
This will include modules such as:
The modules will provide:
- Auto-generation of types and code from schemas, so client code updates instantly when the API version changes
- 3 transport layers: HTTP, WebSocket, TONMP
- All required cryptographic functions
- TONMP requests serialization and deserialization
- Handle events with automatic decryption and message signature verification
We care about DX, so the SDKs will feel familiar. If you have worked with libraries like grammy or openai you already understand the experience we aim for.
3. Backend
Right now we are working on the protocol, including schema serialization and deserialization, sharing and versioning.
Previously we designed a custom architecture for our needs and the utilities required to support it.
We also worked on optimizing certain parts of the pipeline to reach maximum throughput. Our current estimate is that even the first version will be able to handle millions of RPS (requests per second). This is only a projection and will require benchmarking once we have the final version.
4. Documentation
We evaluated many options and narrowed it down to two: VitePress and Mintlify.
We currently prefer VitePress because it is fully open source.
In the future we may mirror the documentation in Mintlify.
The primary language of the documentation will be English. We also plan to use an LLM for automatic translation into other widely used languages to improve developer accessibility.
5. Fundraising and NFTs
Most of the points above are technical and not very transparent to non-technical users. So for everyone else we decided to just show a concept of the fundraising flow and NFT previews.
6. What’s next?
After we complete the JavaScript SDK and backend parts, we plan to start building the application interface and SDKs for Rust/Go or Python.
We're also planning to work on optimizing the processes needed to counter restrictions on free speech.
Even though the federation system is set for late 2026, we can already use ADNL as a decentralized network.
Right now, the issue to fix is latency.
🤍 Stay with us!
We have not published progress updates for a while. Time to fix that.
Even though we are not moving as fast as we would like, we can still share some of what has been done.
If you are not a developer, you can skip the first 2 points.
1. Multiple Cryptography Types
We had a problem: post-quantum cryptographic algorithms are not fast enough in the browser environment.
Since the first public release is planned for browser and desktop, it was important for us to support JavaScript, which is relatively weak for heavy cryptography.
We decided to allow both users and developers to choose between different options in the protocol:
- ECDH for browser / weaker devices, or post-quantum ML-KEM
- Ed25519 or post-quantum ML-DSA
This will apply both to the connection itself and to the messages.
2. JavaScript SDK
Right now we are working on the SDK for the web application.
This will include modules such as:
@tonm/core – shared core utilities@tonm/client – for convenient client development@tonm/bot – for the future Bot API, structured similarly to @tonm/clientThe modules will provide:
- Auto-generation of types and code from schemas, so client code updates instantly when the API version changes
- 3 transport layers: HTTP, WebSocket, TONMP
- All required cryptographic functions
- TONMP requests serialization and deserialization
- Handle events with automatic decryption and message signature verification
We care about DX, so the SDKs will feel familiar. If you have worked with libraries like grammy or openai you already understand the experience we aim for.
3. Backend
Right now we are working on the protocol, including schema serialization and deserialization, sharing and versioning.
Previously we designed a custom architecture for our needs and the utilities required to support it.
We also worked on optimizing certain parts of the pipeline to reach maximum throughput. Our current estimate is that even the first version will be able to handle millions of RPS (requests per second). This is only a projection and will require benchmarking once we have the final version.
4. Documentation
We evaluated many options and narrowed it down to two: VitePress and Mintlify.
We currently prefer VitePress because it is fully open source.
In the future we may mirror the documentation in Mintlify.
The primary language of the documentation will be English. We also plan to use an LLM for automatic translation into other widely used languages to improve developer accessibility.
5. Fundraising and NFTs
Most of the points above are technical and not very transparent to non-technical users. So for everyone else we decided to just show a concept of the fundraising flow and NFT previews.
6. What’s next?
After we complete the JavaScript SDK and backend parts, we plan to start building the application interface and SDKs for Rust/Go or Python.
We're also planning to work on optimizing the processes needed to counter restrictions on free speech.
Even though the federation system is set for late 2026, we can already use ADNL as a decentralized network.
Right now, the issue to fix is latency.
🤍 Stay with us!
❤1👍1
"No" to data collection! "No" to bots on the TON Blockchain!
We recently announced our user verification system via World ID.
That service had two major drawbacks:
- you exposed your data to World Chain
- limited country support (15 countries as of now)
Despite the Orb's cutting-edge tech, the platform falls short on global coverage. We planned to use the Secure Passport verification level, but even it has a limited country list. We can't geofence users - that would violate our principle of freedom.
We decided to revisit this. After five cups of coffee we found a solution!
From now on, passport verification is fully private. How? The passport check happens right on your phone. Your private data never leaves the device.
At first, we considered building this algorithm from scratch on the TON Blockchain. But we chose not to reinvent the wheel and looked for ready-made solutions that meet our requirements. To our surprise, such a project already exists.
We're glad to introduce our integration with Self Protocol.
ZK on-device passport verification, validation on Self Chain, and support for ~129 countries. You can review the country list in the docs or on the interactive map.
The project was built specifically to fight bots on blockchains, so it fits perfectly with our idea of a #NoBots messenger.
From now on, we can confidently say our messenger fully follows the privacy principle - no phone numbers for registration, no personal data.
Privacy on the Internet in 2025 is a safety guarantee. It's not just a desire, it's a necessary extra layer of protection against attackers. It's a guarantee of a calm night's sleep.
We hope this rollout will increase trust in our app and attract more users to complete private verification.
We're launching an initiative to clean the TON Blockchain from spam.
We want REAL votes in polls, REAL comments, and REAL subscribers.
Saving the TON Blockchain from the bot wave is in our hands only.
React if you're with us.
We recently announced our user verification system via World ID.
That service had two major drawbacks:
- you exposed your data to World Chain
- limited country support (15 countries as of now)
Despite the Orb's cutting-edge tech, the platform falls short on global coverage. We planned to use the Secure Passport verification level, but even it has a limited country list. We can't geofence users - that would violate our principle of freedom.
We decided to revisit this. After five cups of coffee we found a solution!
From now on, passport verification is fully private. How? The passport check happens right on your phone. Your private data never leaves the device.
At first, we considered building this algorithm from scratch on the TON Blockchain. But we chose not to reinvent the wheel and looked for ready-made solutions that meet our requirements. To our surprise, such a project already exists.
We're glad to introduce our integration with Self Protocol.
ZK on-device passport verification, validation on Self Chain, and support for ~129 countries. You can review the country list in the docs or on the interactive map.
The project was built specifically to fight bots on blockchains, so it fits perfectly with our idea of a #NoBots messenger.
From now on, we can confidently say our messenger fully follows the privacy principle - no phone numbers for registration, no personal data.
Privacy on the Internet in 2025 is a safety guarantee. It's not just a desire, it's a necessary extra layer of protection against attackers. It's a guarantee of a calm night's sleep.
We hope this rollout will increase trust in our app and attract more users to complete private verification.
We're launching an initiative to clean the TON Blockchain from spam.
We want REAL votes in polls, REAL comments, and REAL subscribers.
Saving the TON Blockchain from the bot wave is in our hands only.
React if you're with us.
❤4👍1🔥1🎉1
— Our Position on EU Laws —
— 1. Chat Control —
The regulation is ineffective with respect to messengers that use end-to-end encryption.
Beyond intruding into users’ privacy and crossing the boundaries of private life, the regulation is completely ineffective in combating crime.
For end‑to‑end encrypted chats, a proposal was made to perform client‑side content scanning. This approach does not work in practice because the client application can be modified, which is common. The moderation code can be removed or replaced. No level of code obfuscation prevents disassembly.
With all due respect to Parliament, we cannot accept this regulation.
Moreover, in our view we will have a more effective system for combating fraud and crime. We share the same goal, but we also uphold people’s rights. It is possible that our method of decentralized moderation will prove more effective and become a standard.
Thanks to our integration with the Self Protocol, offenders will receive effective, lasting penalties. This stands in contrast to other messengers, where one can simply recreate an account and continue unlawful activity.
— 2. Fact‑checking of content —
This is a good initiative if implemented correctly. But that raises a core question: what is the source of truth? Who will determine what is true and what is false? Does a correct implementation even exist? Does truth exist?
How can we claim to know the truth in order to prohibit what we do not deem to be true?
This recalls the story of the "banning" of Copernicus’s "On the Revolutions of the Heavenly Spheres" in 1616. The Inquisition acted as "centralized moderation" and as the "sole source of truth"
Over time it turned out they were wrong. More than 200 years later the book was removed from the Index. For over two centuries society was forbidden to state the truth. Consider the impact: the progress of science and related fields was slowed for two centuries. Galileo Galilei was forced to recant the truth to save his life after condemnation by the Inquisition. People were subjected to fear of the authorities, who had the power to punish. Such influence still exists in many countries today.
One cannot deny that centralized moderation is always susceptible to subjectivity. It was true 400 years ago, and it is true today.
Historical sources:
Maurice A. Finocchiaro, "The Galileo Affair: A Documentary History"
Arthur Koestler, "The Sleepwalkers"
How, then, should we combat disinformation?
In the crypto industry there is a basic rule: DYOR (Do Your Own Research).
No matter how much the world strives toward truth, truth will always recede. What we consider truth at any given moment is only the version accepted by the majority. In that sense, the source of truth is a democratic process of adopting what is regarded as true. And decentralization is democracy at its best.
You should always conduct your own investigation and question even the accepted truth. This is how new discoveries are made.
— 1. Chat Control —
The regulation is ineffective with respect to messengers that use end-to-end encryption.
Beyond intruding into users’ privacy and crossing the boundaries of private life, the regulation is completely ineffective in combating crime.
For end‑to‑end encrypted chats, a proposal was made to perform client‑side content scanning. This approach does not work in practice because the client application can be modified, which is common. The moderation code can be removed or replaced. No level of code obfuscation prevents disassembly.
With all due respect to Parliament, we cannot accept this regulation.
Moreover, in our view we will have a more effective system for combating fraud and crime. We share the same goal, but we also uphold people’s rights. It is possible that our method of decentralized moderation will prove more effective and become a standard.
Thanks to our integration with the Self Protocol, offenders will receive effective, lasting penalties. This stands in contrast to other messengers, where one can simply recreate an account and continue unlawful activity.
— 2. Fact‑checking of content —
This is a good initiative if implemented correctly. But that raises a core question: what is the source of truth? Who will determine what is true and what is false? Does a correct implementation even exist? Does truth exist?
How can we claim to know the truth in order to prohibit what we do not deem to be true?
This recalls the story of the "banning" of Copernicus’s "On the Revolutions of the Heavenly Spheres" in 1616. The Inquisition acted as "centralized moderation" and as the "sole source of truth"
Over time it turned out they were wrong. More than 200 years later the book was removed from the Index. For over two centuries society was forbidden to state the truth. Consider the impact: the progress of science and related fields was slowed for two centuries. Galileo Galilei was forced to recant the truth to save his life after condemnation by the Inquisition. People were subjected to fear of the authorities, who had the power to punish. Such influence still exists in many countries today.
One cannot deny that centralized moderation is always susceptible to subjectivity. It was true 400 years ago, and it is true today.
Historical sources:
Maurice A. Finocchiaro, "The Galileo Affair: A Documentary History"
Arthur Koestler, "The Sleepwalkers"
How, then, should we combat disinformation?
In the crypto industry there is a basic rule: DYOR (Do Your Own Research).
"The more a person learns, the more he realizes how little he knows"
Metaphysics, Aristotle
No matter how much the world strives toward truth, truth will always recede. What we consider truth at any given moment is only the version accepted by the majority. In that sense, the source of truth is a democratic process of adopting what is regarded as true. And decentralization is democracy at its best.
You should always conduct your own investigation and question even the accepted truth. This is how new discoveries are made.
👍1
We plan to integrate LLMs (AI) to make fact‑finding more convenient. AI can be biased and make mistakes, so it must be treated as a tool for vector search and text generation, not as a super‑intelligence. Vector search is based on information from a dataset or the internet. Models are typically trained on real scientific publications. By design, a model is not biased toward any particular source of information. We will also attach a link to the source on which the model’s output is based.
In this way, each of you will be able to check with one click whether the text corresponds to reality. A topic may have several sources of truth. What to regard as truth is your choice and yours alone.
Thus, if EU fact‑checking carries weight for you, you will be able to examine it alongside other sources. Such a system does not violate EU law while preserving users’ rights to know and to consider other viewpoints.
It will likely be fair to give users a choice among LLMs. A request may go to a centralized provider or potentially to a decentralized provider such as @Cocoon. We do not limit your choice. We provide a tool that you can use at your discretion.
— 3. Interoperability between messengers —
Although we are not among the designated "gatekeepers", we would like to offer our view. The initiative is interesting, but it requires agreement on a single E2EE protocol for all messengers as well as the ability to verify its implementation through open‑source code.
Consider this scenario: our users send messages to WhatsApp users. We implement E2EE and open our source code, thereby proving that we truly implemented it. In that case, we also expect WhatsApp to follow the same rules. Otherwise, a leak on WhatsApp’s side would affect our messenger’s reputation. We would be blameless, yet we do not want to be associated with negative headlines. We oppose this initiative if our partners will not open their source code.
It is worth remembering that laws, like coins, have two sides. It is incorrect to claim that all laws bring only harm. One should carefully weigh pros and cons, rights and duties. The core principle of law is to protect people from harming one another. What is harm? It is not for us to judge, since we do not possess the truth. You determine truth yourselves. You have the right to speak, and you have the right to be heard. If you spread disinformation, be ready for criticism. If you speak the truth, be ready for criticism as well. This is the power of the internet. Only bots are standing in the way - and we'll challenge them. ⚔️
Fun fact: under the GPL public license, all third‑party Telegram clients based on its source code must publish their code openly.
We would also be glad to present future integration with Telegram’s Secret Chats, as they fully comply with our policy.
Unfortunately, integration with regular Telegram chats is impossible due to the lack of end‑to‑end encryption on Telegram’s side. We look forward to a protocol update from Telegram. To achieve this, we must demonstrate the value of encryption across all chat types. We cannot do this without your support. The louder the community’s voice, the greater the chance we will be heard. The more serious the competition we pose to Telegram, the more often it will listen to its users.
Keep your private data safe
Seek the truth and find your own understanding of it
Communicate freely with your friends
We continue our work thanks to your support ⚙️
We continue to stand for peace, safety, and freedom. 🕊
Thank you to everyone who is with us. 🤍
In this way, each of you will be able to check with one click whether the text corresponds to reality. A topic may have several sources of truth. What to regard as truth is your choice and yours alone.
Thus, if EU fact‑checking carries weight for you, you will be able to examine it alongside other sources. Such a system does not violate EU law while preserving users’ rights to know and to consider other viewpoints.
It will likely be fair to give users a choice among LLMs. A request may go to a centralized provider or potentially to a decentralized provider such as @Cocoon. We do not limit your choice. We provide a tool that you can use at your discretion.
— 3. Interoperability between messengers —
Although we are not among the designated "gatekeepers", we would like to offer our view. The initiative is interesting, but it requires agreement on a single E2EE protocol for all messengers as well as the ability to verify its implementation through open‑source code.
Consider this scenario: our users send messages to WhatsApp users. We implement E2EE and open our source code, thereby proving that we truly implemented it. In that case, we also expect WhatsApp to follow the same rules. Otherwise, a leak on WhatsApp’s side would affect our messenger’s reputation. We would be blameless, yet we do not want to be associated with negative headlines. We oppose this initiative if our partners will not open their source code.
It is worth remembering that laws, like coins, have two sides. It is incorrect to claim that all laws bring only harm. One should carefully weigh pros and cons, rights and duties. The core principle of law is to protect people from harming one another. What is harm? It is not for us to judge, since we do not possess the truth. You determine truth yourselves. You have the right to speak, and you have the right to be heard. If you spread disinformation, be ready for criticism. If you speak the truth, be ready for criticism as well. This is the power of the internet. Only bots are standing in the way - and we'll challenge them. ⚔️
Fun fact: under the GPL public license, all third‑party Telegram clients based on its source code must publish their code openly.
We would also be glad to present future integration with Telegram’s Secret Chats, as they fully comply with our policy.
Unfortunately, integration with regular Telegram chats is impossible due to the lack of end‑to‑end encryption on Telegram’s side. We look forward to a protocol update from Telegram. To achieve this, we must demonstrate the value of encryption across all chat types. We cannot do this without your support. The louder the community’s voice, the greater the chance we will be heard. The more serious the competition we pose to Telegram, the more often it will listen to its users.
Keep your private data safe
Seek the truth and find your own understanding of it
Communicate freely with your friends
We continue our work thanks to your support ⚙️
We continue to stand for peace, safety, and freedom. 🕊
Thank you to everyone who is with us. 🤍
🎉2
TON Messenger
The passport check happens right on your phone. Your private data never leaves the device.
UPD: Correction to clarify up-to-date information. The data is transmitted into Secure Enclaves. More details at Self Protocol Architecture Docs
What are Secure Enclaves?
Simply put, your data is still completely safe with cryptographic verification. You remain the sole owner of your data.
What are Secure Enclaves?
Simply put, your data is still completely safe with cryptographic verification. You remain the sole owner of your data.
👍3
Bots have started unsubscribing from the channel. Can we say we're on the right way? Can we say that we have taken the first step?
❤2🎉2👍1
#NoAdSpam
We originally spoke out against integrated ads in the messenger.
But what about ad spam from channel authors?
Most channels publish hundreds of promotional posts per month. That's more than the channel's actual themed content.
From now on, users will be able to see how many promotional posts the channel publishes per month.
Every promotional post must be labeled with a small "ad" badge.
It's barely noticeable to users, but if a post contains advertising and doesn't include the label, the channel can be reported.
If there are many violations, the channel will receive an "ad spam" badge (like "scam" or "spam" badges)
We do not restrict creators who want to monetize their channels through advertising
We do not limit project growth - you are free to buy ads from channel owners
We give users the ability to know what kind of channel they are subscribing to
This post is a test of the new short-post format. But maybe after the shorter context you still have a lot of questions. Let us know which format you prefer.
If you have any remaining questions, contact us
We originally spoke out against integrated ads in the messenger.
But what about ad spam from channel authors?
Most channels publish hundreds of promotional posts per month. That's more than the channel's actual themed content.
From now on, users will be able to see how many promotional posts the channel publishes per month.
Every promotional post must be labeled with a small "ad" badge.
It's barely noticeable to users, but if a post contains advertising and doesn't include the label, the channel can be reported.
If there are many violations, the channel will receive an "ad spam" badge (like "scam" or "spam" badges)
We do not restrict creators who want to monetize their channels through advertising
We do not limit project growth - you are free to buy ads from channel owners
We give users the ability to know what kind of channel they are subscribing to
This post is a test of the new short-post format. But maybe after the shorter context you still have a lot of questions. Let us know which format you prefer.
If you have any remaining questions, contact us
👍1
When AWS was down - tonm.app was working
When Cloudflare was down - tonm.org was working
ton-messenger.ton was working all the time
When Cloudflare was down - tonm.org was working
ton-messenger.ton was working all the time
👍5
This media is not supported in your browser
VIEW IN TELEGRAM
We were looking for a browser with TON support but couldn't find one anywhere...
So we decided to create TON Browser!
Here's the list of changes:
- Integrated TON Proxy directly into the browser
- The .ton domain is now recognized as a domain, not a search query
- Removed the insecure connection warning that could confuse regular users (ADNL has encryption by default)
- Replaced Firefox branding with TON Browser
- DuckDuckGo is set as the default search engine for privacy
Planned future updates:
- Integrate wallet extensions
- Searching for a wallet address will redirect to tonscan/tonviewer
- Add support for the adnl:// URL scheme
- Expand default bookmarks to make navigation easier for newcomers
These updates should simplify how users interact with TON Web3 services.
Just download the browser and you can start using sites right away, without having to configure a Proxy.
So we decided to create TON Browser!
Here's the list of changes:
- Integrated TON Proxy directly into the browser
- The .ton domain is now recognized as a domain, not a search query
- Removed the insecure connection warning that could confuse regular users (ADNL has encryption by default)
- Replaced Firefox branding with TON Browser
- DuckDuckGo is set as the default search engine for privacy
Planned future updates:
- Integrate wallet extensions
- Searching for a wallet address will redirect to tonscan/tonviewer
- Add support for the adnl:// URL scheme
- Expand default bookmarks to make navigation easier for newcomers
These updates should simplify how users interact with TON Web3 services.
Just download the browser and you can start using sites right away, without having to configure a Proxy.
👍9❤3🔥1
You can check out all the changes on our GitHub.
At the moment, you can run builds for Windows and Linux.
Let us know if you're interested - we'll prepare builds for Windows, Android, and possibly iOS and macOS in the future.
Thanks to Mozilla Firefox and TON Utils Proxy for making this possible.
And we’re continuing the development of TON Messenger!
At the moment, you can run builds for Windows and Linux.
Let us know if you're interested - we'll prepare builds for Windows, Android, and possibly iOS and macOS in the future.
Thanks to Mozilla Firefox and TON Utils Proxy for making this possible.
And we’re continuing the development of TON Messenger!
❤3👍2🔥2
Hi, community!
We've noticed that the idea of the TON Browser has received a good response, but our main focus remains the TON Messenger.
The browser build process is quite complex, so to allocate resources properly, we want to run a poll and understand which platform you actually need first.
Platforms that gather 250 votes will get support earlier than the others.
But even if a platform doesn't reach the required number of votes, its release will still happen - just later.
We have a small request: please help gather the opinion of the TON community. Share the poll with your friends.
The community's interest is the only thing we need. None of this would exist without you.
In an era when most projects chase personal gain, it's very hard to earn users' trust and attention.
We sincerely thank everyone who shows interest. Your trust is priceless!
We've noticed that the idea of the TON Browser has received a good response, but our main focus remains the TON Messenger.
The browser build process is quite complex, so to allocate resources properly, we want to run a poll and understand which platform you actually need first.
Platforms that gather 250 votes will get support earlier than the others.
But even if a platform doesn't reach the required number of votes, its release will still happen - just later.
We have a small request: please help gather the opinion of the TON community. Share the poll with your friends.
The community's interest is the only thing we need. None of this would exist without you.
In an era when most projects chase personal gain, it's very hard to earn users' trust and attention.
We sincerely thank everyone who shows interest. Your trust is priceless!
What platforms would you like to see the TON Browser for?
Anonymous Poll
54%
Android
32%
iOS
51%
Windows (x86-64)
9%
Windows (ARM)
9%
macOS (x86-64)
14%
macOS (ARM)
18%
Linux (.deb .snap .flatpak. .AppImage etc)
How to lose your client
Recently, X integrated displaying the account's country. One day, your private information was leaked into public access.
What are the downsides of public geolocation?
There are no borders or countries on the internet
Web3 proves it
Recently X restored privacy. But it will never restore trust.
Recently, X integrated displaying the account's country. One day, your private information was leaked into public access.
What are the downsides of public geolocation?
1. Enables region-specific fraud schemes
2. Improves attack targeting using language and popular local services
3. Narrows OSINT search area, increasing chances of deanonymization
4. Allows localized social engineering scenarios
5. Turns the internet into a playground that continues real-world problems
There are no borders or countries on the internet
Web3 proves it
Recently X restored privacy. But it will never restore trust.
🔥2
Web3-world Statistics
According to our data, around 144,000 .ton domains have been minted in total
Shortest ones: 2,600 pieces (4 characters long)
Most popular: 11-character domains (32,000 pieces)
Total spent: about 1 million $TON (based on current domain prices)
But these are just domains. What about websites?
We counted around 500 active websites, including interesting developer profiles and promising projects.
You might ask: Telegram has the largest crypto-related developer community, so why are there so few websites?
We asked ourselves the same question and tried to find the reason.
Imagine you're an regular user. How do you use the internet?
1. Open a browser (pre-installed on the device)
2. Enter a search query or URL
What do you need to use Web3?
1. Find a proxy and verify its trust level
2. Install the proxy
3. Enable the proxy
4. Open a browser
5. Enter the URL, or
6. Search for a .ton website list in Google
7. Find the needed website
8. Close the unsafe connection warning
Every day Google processes 10 billion search queries. Brave Web3 browser has already been installed over 100 million times.
These statistics show a real demand for such tools. The lack of these tools in TON Web3 pushes users away. If there are no users, there will also be no developers building websites.
Once developers know that users will be able to discover their websites, they will start creating them.
If we want TON's vision of a free internet to grow, we need those essential tools.
While Web2 websites get blocked, the hundreds .ton websites keep working 24/7.
According to our data, around 144,000 .ton domains have been minted in total
Shortest ones: 2,600 pieces (4 characters long)
Most popular: 11-character domains (32,000 pieces)
Total spent: about 1 million $TON (based on current domain prices)
But these are just domains. What about websites?
We counted around 500 active websites, including interesting developer profiles and promising projects.
You might ask: Telegram has the largest crypto-related developer community, so why are there so few websites?
We asked ourselves the same question and tried to find the reason.
Imagine you're an regular user. How do you use the internet?
1. Open a browser (pre-installed on the device)
2. Enter a search query or URL
What do you need to use Web3?
1. Find a proxy and verify its trust level
2. Install the proxy
3. Enable the proxy
4. Open a browser
5. Enter the URL, or
6. Search for a .ton website list in Google
7. Find the needed website
8. Close the unsafe connection warning
Every day Google processes 10 billion search queries. Brave Web3 browser has already been installed over 100 million times.
These statistics show a real demand for such tools. The lack of these tools in TON Web3 pushes users away. If there are no users, there will also be no developers building websites.
Once developers know that users will be able to discover their websites, they will start creating them.
If we want TON's vision of a free internet to grow, we need those essential tools.
While Web2 websites get blocked, the hundreds .ton websites keep working 24/7.
❤5🔥4👍2
I'll just leave this here for those who want automatic translation
https://news.1rj.ru/str/boost/tonm_app
P.s.We'll pin a couple of important messages now, sorry for the spam.
It was difficult to choose, but we did it.
We have created some "anchors" next to which there are also important messages.
https://news.1rj.ru/str/boost/tonm_app
P.s.
It was difficult to choose, but we did it.
We have created some "anchors" next to which there are also important messages.
Telegram
TON Messenger
Boost this channel to help it unlock additional features.
What is TON Messenger?
We talked a lot about separate parts of the messenger, but never summarized all key advantages in one post. Let's fix that.
1. Integration with TON
- Built-in wallet
- Voting through smart contracts
- Fundraising (convenient decentralized crowdfunding)
- Wallets for users, channels, and groups
- And much more
In short: the native messenger currency is $TON, not centralized "stars".
Its functions have decentralized alternatives implemented through smart contracts. For example, decentralized voting or giveaways.
You no longer need to trust the results. Now you can verify them. Cryptography is a mathematical guarantee of truth.
Useful posts:
- Fundraising concept
2. Fighting scammers and spam
This is our main priority. We are implementing a special algorithm for this.
Spam bots are the main weapon of fraud actors. We aim to remove this attack surface entirely.
No need to rely on paid access to messages to limit spam - we solve the root problem, not invent ways to live with it.
Useful posts:
- How we fight scammers
- Updated approach to improve user privacy
- Fighting advertising spam
3. No personal data
Registration works through a seed phrase. No emails, no phone numbers, no "anonymous numbers" that actually require KYC.
Only 24 words - this is your key to your account. From any device, from any type of internet connection.
Useful posts:
- Integration of projects that share our privacy values
4. Post-quantum cryptography and end-to-end encryption
Popular decentralized private messengers like Session and Matrix inspired our direction, but we go further:
TON Messenger adopts post-quantum cryptography to future-proof message integrity. Why it matters for everyday users?
Today's encryption can become breakable once large-scale quantum computers arrive - not just future messages, but even your archived chats could be decrypted years later.
Whether that happens in 10, or 20 years is unknown - but we already know this: your messages remain protected for 30+ years ahead, beyond today's computing limits.
Useful posts:
- About post-quantum cryptography
- Why Telegram is not a private messenger
5. Community-oriented and open-source
We listen to the community. We believe this is our strong side.
We don't build corporate walls. We are part of the TON ecosystem.
You are as much a part of TON Messenger as we are.
We will also have open-source code - everyone will be able to participate in development and audit it.
Useful posts:
- Our history
- Our weaknesses
- Our strengths
- Our stance on laws
- Our decentralization vision
- TON Browser announcement
- Our Web3 vision
You can always contact us if you have questions.
Your TON Messenger Team
We talked a lot about separate parts of the messenger, but never summarized all key advantages in one post. Let's fix that.
1. Integration with TON
- Built-in wallet
- Voting through smart contracts
- Fundraising (convenient decentralized crowdfunding)
- Wallets for users, channels, and groups
- And much more
In short: the native messenger currency is $TON, not centralized "stars".
Its functions have decentralized alternatives implemented through smart contracts. For example, decentralized voting or giveaways.
You no longer need to trust the results. Now you can verify them. Cryptography is a mathematical guarantee of truth.
Useful posts:
- Fundraising concept
2. Fighting scammers and spam
This is our main priority. We are implementing a special algorithm for this.
Spam bots are the main weapon of fraud actors. We aim to remove this attack surface entirely.
No need to rely on paid access to messages to limit spam - we solve the root problem, not invent ways to live with it.
Useful posts:
- How we fight scammers
- Updated approach to improve user privacy
- Fighting advertising spam
3. No personal data
Registration works through a seed phrase. No emails, no phone numbers, no "anonymous numbers" that actually require KYC.
Only 24 words - this is your key to your account. From any device, from any type of internet connection.
Useful posts:
- Integration of projects that share our privacy values
4. Post-quantum cryptography and end-to-end encryption
Popular decentralized private messengers like Session and Matrix inspired our direction, but we go further:
TON Messenger adopts post-quantum cryptography to future-proof message integrity. Why it matters for everyday users?
Today's encryption can become breakable once large-scale quantum computers arrive - not just future messages, but even your archived chats could be decrypted years later.
Whether that happens in 10, or 20 years is unknown - but we already know this: your messages remain protected for 30+ years ahead, beyond today's computing limits.
Useful posts:
- About post-quantum cryptography
- Why Telegram is not a private messenger
5. Community-oriented and open-source
We listen to the community. We believe this is our strong side.
We don't build corporate walls. We are part of the TON ecosystem.
You are as much a part of TON Messenger as we are.
We will also have open-source code - everyone will be able to participate in development and audit it.
Useful posts:
- Our history
- Our weaknesses
- Our strengths
- Our stance on laws
- Our decentralization vision
- TON Browser announcement
- Our Web3 vision
You can always contact us if you have questions.
Your TON Messenger Team
We've been reported serious translation errors when using the Telegram translator feature.
Please also read the original version.
Please also read the original version.
👍2👎1