Ton Console

And again :(

DDoS again. We are fixing

🌥 Service fully resumed During yesterday's denial-of-service attack we have updated the TonAPI infrastructure and it is now fully operational. We are still working on further improvements to be able to withstand a similar attack should it repeat. Thank you for using TonAPI!

⏸ Testnet indexer is temporarily on pause Tonviewer and TonAPI services on testnet are off for maintenance. We plan to turn testnet back on within 24 hours.

⛈ Targeted denial-of-service attack against TON infrastructure Some of the most popular infrastructure providers are experiencing a deliberate flood attack that leads to slower or interrupted service. This attack is aimed at our TonAPI servers, public liteservers, Ton Center, Getblock and Tonhub. Check out the availability of the infrastructure in real time: 👉 tonstat.us About the attack 1. Decentralized network of TON nodes is working normally. Transactions get validated at a stable pace of 50 tx/sec. 2. Your funds in Tonkeeper are safe: even if your Tonkeeper has trouble connecting to TonAPI, try again later. 3. This is a deliberate and planned attack. We see a mixture of low-level flood attack by UDP packets that clog the bandwidth and crafted requests aimed at exhausting resources of the indexing services (e.g. triggering expensive TVM evaluation). 4. We do not currently have an estimate when the attack will be mitigated. Every infra provider is trying to reconfigure or relocate their servers to hide them from the attackers' reach. This process may take hours or days. 5. Attackers are adapting quickly. We tried different quick options to divert the flood and noticed how attackers change tactics, discover new IP addresses and resume their activity. We are proud that our services are important and valuable in the TON community, so that it attracts such unwanted attention. Our team is working overnight to protect our services and come out stronger out of this. I thank all our users for your patience. Hold on tight! ❤️

Our servers are under DDoS attack again. Our specialists are working on solving the problem, but this time the issues are more serious. There are no estimates for restoration of functionality yet. We will keep you informed.

We regret to inform you that our service experienced an outage from 15:47 to 16:59 Dubai time due to a DDoS (Distributed Denial of Service) attack from 3400 IP addresses from multiple data centers. Our team is diligently working on strengthening our infrastructure to enhance service resilience against such attacks. We apologize for any inconvenience caused and thank you for your patience as we fortify our systems to serve you better.

We experienced a brief service interruption today from 13:36 to 13:48 Dubai time, due to technical issues. We apologize for any inconvenience this may have caused and appreciate your understanding. Rest assured, our team is actively working to enhance system stability to prevent future occurrences. Thank you for your patience.

https://tonapi.io/v1/ will be disabled on 2023.12.27. Please migrate to /v2/.

We are experiencing a DDoS attack. Tonapi is unavailable at the moment. UPD: It's not DDOS but something unusuall in blockchain. we are investigating the problem UPD: TON API is back online.

We have problem with indexing new transactions Upd: Fixed

Mainnet API is temporary unavailable. We are investigating the problem. UPD: fixed. downtime 23:20-23:55 UTC.

🚨 Testnet API is temporary unavailable. We are investigating the problem.

🚨 We are currently experiencing issues with the blockchain indexing through TonAPI. Consequently, the TonAPI responses are reflecting the status from approximately 10 minutes ago and failing to receive any updates. Our technical team is actively looking into this matter. We appreciate your understanding and patience. ⚠️ Update: We've managed to resolve the primary issue, but you might still encounter occasional 500 errors. Rest assured, we are actively working on a solution and expect to deploy a fix shortly. Thanks for your patience and understanding. 🙏 ✅ Update: This issue is fully resolved.

If you are using tonconnect package from tongo library please update your version to v1.3.1 ASAP! 🔥🔥🔥🔥🔥🔥🔥🔥🔥

Hi! We made some changes to the decoded message body. You can now test it on https://beta.tonapi.io. This is a complete operating API for the mainnet with all the authorization, limits, tokens, access levels, and other stuff, but on running on a new index version. This API endpoint (beta.tonapi.io) will become available from September 19 through September 30 guaranteed. We’re switching current API endpoint (tonapi.io) to the new index at 12:00 AM on Friday UTC+3. Endpoint Changes: - /v2/blockchain/blocks/{block_id}/transactions - /v2/blockchain/transactions/{hash} - /v2/blockchain/messages/{hash}/transaction - /v2/blockchain/accounts/{account}/transactions - /v2/wallet/emulate - /v2/traces/{hash} Field Changes: - decoded_body in the Message type. General Changes: - Removed extra wrappers: {value: {something}} > {something}. - Token and NFT transfers got a new forward_paylod callback: now it’s not a hex line but a structure with a type and value.

UPD: we will deploy changes first on dev platform and you will have time for make changes in your code.

We're working on some substantial upgrades to improve the functionality of decoded message bodies. Those enhancements may disrupt backward compatibility so we kindly invite you to assist us in making informed decisions by participating in the vote below. Your input is highly valued and will greatly contribute to our decision-making process. 1. Update on Ref types structure from:

"some_type_stored_in_cell_ref": {"value": somevalue}

to:

"some_type_stored_in_cell_ref": somevalue

2. Update forward_payload for NFTs and jettons. Old:

forward_payload: "hex_encoded_boc"

New:

forward_payload: {Type: "DedustSwap", Value: {MinAmountOut: "100500"}}

or forward_payload: {Type: "Cell", Value: "hex_encoded_boc"}

We don't check signature right now in our "emulations" methods of Tonapi. But we are going to enable it for all methods except /v2/wallet/emulate. Please be careful. /v2/events/emulate /v2/traces/emulate /v2/accounts/{account_id}/events/emulate