Technical notifications and up-to-date requests for action for TON validators, developers and integrators.
If you're a validator or developer of a popular TON service you should be subscribed.
Post #40
14K
Channel ✦ Verified Channel
TO TON Status
@tonstatus
- Subscribers
- 157K
- Photos
- 0
- Videos
- 0
- Links
- 156
Showing posts older than #41 · Back to latest
Older Posts 20 shown
Post #39
14.3K
t.me support in your applications:
— if you are using tonlib no action is required.
— if you are using tonweb - make sure that tonweb version is 0.0.58 or higher.
— if you use another solution - make sure you get root DNS smart contract from network config number 4.
— if you are using tonlib no action is required.
— if you are using tonweb - make sure that tonweb version is 0.0.58 or higher.
— if you use another solution - make sure you get root DNS smart contract from network config number 4.
Post #38
13.1K
TON Status Vote to change the root DNS smart contract The new root DNS smart contract which supports both .ton and .t.me domains has the following address Ef_lZ1T4NCb2mwkme9h2rJfESCE0W34ma9lWp7-_uY3zXDvq. You can check out its source code on GitHub. — Added support…
The voting was successfully completed, the root TON DNS smart contract was updated.
Post #37
13.2K
Vote to change the root DNS smart contract
The new root DNS smart contract which supports both .ton and .t.me domains has the following address Ef_lZ1T4NCb2mwkme9h2rJfESCE0W34ma9lWp7-_uY3zXDvq.
You can check out its source code on GitHub.
— Added support for t.me domain zone - Telegram usernames.
— Added short alias www.ton for the foundation.ton site.
— .ton domain zone support without changes.
Network validators, please vote for this proposal.
To vote via mytonctrl, you need to use the command: vo 110945915504048090704740762384722970647335048403405846922858187005120712761626
If you don't use mytonctrl, use this instruction.
The new root DNS smart contract which supports both .ton and .t.me domains has the following address Ef_lZ1T4NCb2mwkme9h2rJfESCE0W34ma9lWp7-_uY3zXDvq.
You can check out its source code on GitHub.
— Added support for t.me domain zone - Telegram usernames.
— Added short alias www.ton for the foundation.ton site.
— .ton domain zone support without changes.
Network validators, please vote for this proposal.
To vote via mytonctrl, you need to use the command: vo 110945915504048090704740762384722970647335048403405846922858187005120712761626
If you don't use mytonctrl, use this instruction.
Post #36
10.3K
The Open Network Telegram Usernames and TON DNS Given that Telegram usernames comply with TON DNS standard, we consider it a great idea to add the "t.me" domain zone to the TON DNS root smart contract. Almost all TON wallets and apps allow you to enter a ".ton" domain instead…
We remind you that tomorrow at 12:00 UTC all validators will need to send their vote for the DNS proposal.
Please stay in touch.
Please stay in touch.
Post #35
9.75K
Forwarded from The Open Network
Telegram Usernames and TON DNS
Given that Telegram usernames comply with TON DNS standard, we consider it a great idea to add the "t.me" domain zone to the TON DNS root smart contract.
Almost all TON wallets and apps allow you to enter a ".ton" domain instead of a wallet address.
After updating the root TON DNS, it will be possible to enter a Telegram username into TON apps in the same way as ".ton" domains. In other words, you will be able to send Toncoins to "any.t.me" address. The TON apps themselves will not require modifications.
Since the blockchain configuration can only be changed by validator voting, we’re scheduling a network vote for this proposal on Oct. 31 at 12:00 UTC. Validators, please be ready to send your vote at this time. Detailed instructions will be posted later.
Given that Telegram usernames comply with TON DNS standard, we consider it a great idea to add the "t.me" domain zone to the TON DNS root smart contract.
Almost all TON wallets and apps allow you to enter a ".ton" domain instead of a wallet address.
After updating the root TON DNS, it will be possible to enter a Telegram username into TON apps in the same way as ".ton" domains. In other words, you will be able to send Toncoins to "any.t.me" address. The TON apps themselves will not require modifications.
Since the blockchain configuration can only be changed by validator voting, we’re scheduling a network vote for this proposal on Oct. 31 at 12:00 UTC. Validators, please be ready to send your vote at this time. Detailed instructions will be posted later.
Post #34
10.1K
A recent update to FunC introduced a bug related to the optimization of some expressions involving the bitwise NOT
Please update your FunC compiler from master.
~.Please update your FunC compiler from master.
Post #33
25.6K
Mainnet validators:
Please start update of your node software from October 6 8:00 GMT to new version:
— in mytonctrl commandline run
— if you don't use mytonctrl please manually rebuild code from master branch of https://github.com/ton-blockchain/ton.
Update your validators one by one, don't update all at the same time.
Please avoid update one hour prior and two hours after start of new validation cycle; on October 6 new validation round will start around 16:00 GMT, thus avoid update in 15:00-18:00 GMT span.
Please start update of your node software from October 6 8:00 GMT to new version:
— in mytonctrl commandline run
update then upgrade.— if you don't use mytonctrl please manually rebuild code from master branch of https://github.com/ton-blockchain/ton.
Update your validators one by one, don't update all at the same time.
Please avoid update one hour prior and two hours after start of new validation cycle; on October 6 new validation round will start around 16:00 GMT, thus avoid update in 15:00-18:00 GMT span.
Post #31
22.4K
Network security update
Network update is scheduled on October 6 08:00 GMT.
We are asking mainnet validators to schedule time for upgrade your validator software.
Detailed instructions and information will be published on October 6.
Network update is scheduled on October 6 08:00 GMT.
We are asking mainnet validators to schedule time for upgrade your validator software.
Detailed instructions and information will be published on October 6.
Post #30
9.92K
TON-Ethereum bridge is running again!
All previous transfers have been processed.
Thanks for waiting.
All previous transfers have been processed.
Thanks for waiting.
Post #29
9.95K
TON-Ethereum bridge is under maintenance due to recent update of Ethereum network and will be resumed as soon as possible. We will notify you about that. All unprocessed swaps are safe and will be processed once operations resume.
TON-BSC bridge works as usual.
TON-BSC bridge works as usual.
Post #28
10.2K
Forwarded from The Open Network
Developers, please note that there have been additions to the standards:
- Added
- Added note about data encoded in TL-B schema in Token Data standard.
- Added
forward_payload format to NFT and Jettons standards.- Added note about data encoded in TL-B schema in Token Data standard.
Post #27
11.4K
At least 25 validators have not been updated to the previous update and therefore do not work:
To update:
— in mytonctrl commandline run
— if you don't use mytonctrl please manually rebuild code from master branch of https://github.com/ton-blockchain/ton.
ADNL Pubkey
9D5807...F0A93D FD362E...9AA3DD
75B0B7...33FB88 BD9194...1503B8
9E8CF3...C9322A 993C80...D8A0D2
1F4E39...497CC6 0D737A...9F24C2
B2DC94...1F4B0E 8299B1...052ABC
1300AB...DFD989 E2645E...5B52EF
DAE434...E55B25 399722...231BF9
7B92DC...EA4A7F A2E1C9...08CBCF
A33EBA...7AED9C B3C81D...204097
3090F8...049726 8987DB...19CAF1
DA00B4...C454EB 2C0874...0C3C52
B02E52...FE308D BC240A...160313
AF402E...85D80B 9B348D...071CE5
BC0BD7...F45107 7E318A...FEF81E
F3876C...E3B9C9 AB1001...1207E5
A8FA83...23E0FA 6B6654...DC32A3
B1E0E6...29F1B8 4AD0F8...0A3B77
E854AA...039227 0FB3E1...F1186D
EDB4ED...9EF8F9 B82717...A755B1
0C45E8...89B7DC 764390...A96FC6
B065B1...7C2749 47B818...F6EC52
AFCCEE...8C3607 7E9B91...9AA75C
B2C527...8AAFA4 08C5FF...9AE000
860F8D...6EB624 76CF73...A5BA4A
016AE2...77A65E 4BBC1B...966761
To update:
— in mytonctrl commandline run
update then upgrade.— if you don't use mytonctrl please manually rebuild code from master branch of https://github.com/ton-blockchain/ton.
Post #26
9.66K
Everything is ready to continue.
Validators please continue upgrade and follow instructions from recent post: upgrade and vote.
Validators who have already upgrade on August 8 (and not on
Validators please continue upgrade and follow instructions from recent post: upgrade and vote.
Validators who have already upgrade on August 8 (and not on
570da56 commit), please repeat all steps again. Post #25
9.75K
We found imperfections in recent TON node update. Please postpone upgrade till special notification.
Post #24
10.1K
Due to the temporary decrease in the efficiency of validators after the current elections, we urge you to postpone the update by 4 hours until 17:00 UTC.
If you have already updated - it's OK, nothing needs to be done.
If you have already updated - it's OK, nothing needs to be done.
Post #23
11.2K
Mainnet validators:
1. Please update your software to new version:
— in mytonctrl commandline run
— if you don't use mytonctrl please manually rebuild code from master branch of https://github.com/ton-blockchain/ton.
Update your validators one by one, don't update all at the same time.
2. Wait till synchronization restores.
3. Strongly after software update and sync, please vote for new network config param #29 (to inspect new config param you can use
— To vote via mytonctrl you need to use the command:
— If you don't use mytonctrl use this instruction.
1. Please update your software to new version:
— in mytonctrl commandline run
update then upgrade.— if you don't use mytonctrl please manually rebuild code from master branch of https://github.com/ton-blockchain/ton.
Update your validators one by one, don't update all at the same time.
2. Wait till synchronization restores.
3. Strongly after software update and sync, please vote for new network config param #29 (to inspect new config param you can use
od command in mytonctrl):— To vote via mytonctrl you need to use the command:
vo 29795181976365520175863428275263019662169778992074990458062119590680042465200— If you don't use mytonctrl use this instruction.
Post #22
17.2K
Security update of the network is scheduled on August 8. We are asking mainnet validators to schedule time for the maintenance.
Note, that update will not be activated immediately after node software upgrade. Instead, to preserve consensus all the time, update will be triggered by acceptance of new network config.
Therefore the whole process will require from you
1) Update your validator node
2) Wait till synchronization restores
3) Voting for new config
The order of actions is primary important.
Besides improving the security, this update contains node stability and memory consumption improvements, speed up of access to database and enhancing stats.
Note, that update will not be activated immediately after node software upgrade. Instead, to preserve consensus all the time, update will be triggered by acceptance of new network config.
Therefore the whole process will require from you
1) Update your validator node
2) Wait till synchronization restores
3) Voting for new config
The order of actions is primary important.
Besides improving the security, this update contains node stability and memory consumption improvements, speed up of access to database and enhancing stats.
Post #21
23.9K
Setting the root DNS in the network config
Validators please vote for setting
To vote via mytonctrl you need to use the command:
If you don't use mytonctrl use this instruction.
The DNS source code can be found on the GitHub.
Validators please vote for setting
Ef-OJd0IF0yc0xkhgaAirq12WawqnUoSuE9RYO3S7McG6lDh address in config 4 as root DNS.To vote via mytonctrl you need to use the command:
vo 28570401098048530419903479567404779787541823236808968536408335541289727996611If you don't use mytonctrl use this instruction.
The DNS source code can be found on the GitHub.
Post #20
11K
Network validators, on Aug. 2, it is planned to set the root DNS contract in the network config by voting — all validators need to participate.