Sub-Second for the TON Ecosystem

As part of the Sub-Second mainnet rollout, ecosystem participants should review the following guidance.

For Validators and Node owners

Follow @tonstatus.

For API developers

Please update your own nodes as described in the corresponding post.

APIs will continue functioning after the network upgrade. No additional compatibility changes are required.

If you were previously using low-end hardware, you may need to upgrade it due to the increased block rate

To deliver near-instant UX, we recommend adopting the latest API practices:

— Enable WebSockets support.
— Optimize general API latency.
— Support Pending and Confirmed operation statuses.

You can refer to the changes in the Toncenter API.

For exchanges and payment services

If you are running your own node, please update it as described in the corresponding post.
If you are using an API, whether external or self-hosted, no action is required.

No additional changes are needed. Transaction finality should continue to be determined based on masterchain finalization, as before.

For products and dApps

If you are running your own node, please update it as described in the corresponding post.
If you are using an API, whether external or self-hosted, no action is required.

Products and APIs will continue functioning after the network upgrade. No additional compatibility changes are required.

To deliver near-instant UX, we recommend adopting the latest UX practices:
— Use Toncenter Streaming API V2.
— Display an operation in the UI once it reaches Pending status.
— Mark an operation as completed once it reaches Confirmed status.

You can refer to the changes in mytonwallet.io and tonscan.org.