TON Rust Node | Chat

google drive line for logs

Thanks! I will analyze and return soon

We've analyzed your log file. Unfortunately, it doesn't contain enough information for a full analysis. We have some ideas, but more metrics are needed for confirmation. Please follow these steps: - Enable telemetry in logs.config.yml at the debug level (I recommend leaving this value permanently) telemetry: level: debug - Wait 30 minutes - Send me the last log tail -n 200000 output.log > 200K.log

I modified the configuration file, restarted the node, and checked the log. The synchronization speed is faster than the output speed.

Nodectl v0.5.0 & Node v0.7.0: Validator Continuity & Security Hardening Keys locked tight, pools tuned right, node running light. Static ADNL becomes the default across elections, nominator pools get deploy modes for cleaner setup, and automation covers wallet and pool deploys and top-ups. On the node side, secrets move into vault-based storage, while external message processing, archival memory usage, CellDb efficiency, and the handling of compressed BOCs, external messages, and TVM transactions all improve. Full changelogs: ▪️ https://github.com/RSquad/ton-rust-node/releases/tag/nodectl%2Fv0.5.0 ▪️ https://github.com/RSquad/ton-rust-node/releases/tag/node%2Fv0.7.0 ▪️ https://github.com/RSquad/ton-rust-node/releases/tag/helm%2Fnodectl%2Fv0.3.0

hello , i up to version v0.7.0 ,and No configuration files were modified， However, the ADNL connection to port 50063 failed

liteserver port 50063

Nodectl v0.5.1 & Node v0.8.0: RPC Resilience & Data Freshness Lag protection on the fly, strict endpoint routing, and precise stake validation. Nodectl protects your election decisions by automatically skipping lagging JSON-RPC endpoints before every request. Instead of unpredictable round-robin, it now enforces a strict priority-based fallback where the primary node carries all traffic and backups trigger only on failure, while periodic TTL cache refreshes eliminate frozen-stake accounting distortions. On the node side, a new HTTP SSE endpoint enables real-time tracking of confirmed blocks. The latest update also delivers a major Cell DB performance boost via the RocksDB merge operator, along with further stability fixes. ⚠️Important: this release is non-revertible. Once upgraded, nodes cannot roll back to earlier versions, so plan your deployment accordingly. Full changelogs: ▪️ https://github.com/RSquad/ton-rust-node/releases/tag/nodectl%2Fv0.5.1 ▪️ https://github.com/RSquad/ton-rust-node/releases/tag/node%2Fv0.8.0 ▪️ https://github.com/RSquad/ton-rust-node/releases/tag/helm%2Fnodectl%2Fv0.3.1

TON Rust Node v0.8.2: Network & Performance Optimization Enhanced QUIC transport and memory efficiency. Introduces a block sync overlay for observer-mode validators and adapts custom overlays to the QUIC transport layer, now featuring SNI support. This release also delivers key memory optimizations, streamlines Simplex version propagation to the validator manager, and resolves state resolver cache issues in the collator for improved node stability. Read the Changelog: https://github.com/RSquad/ton-rust-node/releases/tag/node%2Fv0.8.2

TON Rust Node v0.8.3: Block v14 Support Preparing for the block version upgrade. This release adds full support for the block version 14. It updates the TVM and the transaction executor to ensure node stability and seamless compatibility with the new block version. Read the Changelog: https://github.com/RSquad/ton-rust-node/releases/tag/node%2Fv0.8.3

Nodectl v0.6.0 & Node v0.9.0: Audited Events. Sharper Consensus. Two releases, one direction. Stricter accountability on the tooling side, tighter execution on the node side. Nodectl now introduces an append-only audit log that captures domain events like elections, config changes, authentication, and service lifecycle, with automatic file rotation. Plus a Nominator Pool gas fix for large withdraw-request batches. On the node side, a new Simplex consensus emulator for testing arrives alongside extensive consensus refactoring. Collator stability hardened across empty-candidate repairs, stale request throttling, and candidate observation recovery. Full changelogs: ▪️ https://github.com/RSquad/ton-rust-node/releases/tag/nodectl%2Fv0.6.0 ▪️ https://github.com/RSquad/ton-rust-node/releases/tag/node%2Fv0.9.0

Hello, is it expected to receive such log during the initial node sync? What am I missing? WARN node::engine - download_block_proof_worker (attempt 1): id: (-1:8000000000000000, 46894135, rh 3048e69a12cf946ebc99b4cf9ca61c3ff4b3fcc88c4015763ac01204ecc1bf9f, fh bbdac0b4543e9141449ceb37c3c63ba6e9cc4e2c904d77f56d17e44acf1d1bed), Neighbour is not found (0 in list) for query (TLObject tl_id:#77364c38 PrepareKeyBlockProof { block: BlockIdExt { shard_id: -1, 8000000000000000, seq_no: 46894135, root_hash: 3048e69a12cf946ebc99b4cf9ca61c3ff4b3fcc88c4015763ac01204ecc1bf9f, file_hash: bbdac0b4543e9141449ceb37c3c63ba6e9cc4e2c904d77f56d17e44acf1d1bed }, allow_partial: BoolFalse }

I just ran ton-rust-node's TVM through my tool (metamorphic + differential fuzzing) — it looks solid overall. I only found a few divergences in very edge cases; reported one: https://github.com/RSquad/ton-rust-node/issues/226. The fun part is that you've actually fixed a real C++ TVM miscompile in an arithmetic corner case, so sometimes it's even more correct. Are you planning any security contests or a bug bounty program in the future?

hello

I use mycontrl run liteServer， but the MyTonCtrl> status [debug] 30.09.2026, 07:13:53.292 (UTC) <MainThread> start GetValidatorStatus function [debug] 30.09.2026, 07:13:53.299 (UTC) <MainThread> start GetValidatorWallet function [debug] 30.09.2026, 07:13:53.299 (UTC) <MainThread> start GetLocalWallet function [debug] 30.09.2026, 07:13:53.299 (UTC) <MainThread> start GetWalletFromFile function [debug] 30.09.2026, 07:13:53.299 (UTC) <MainThread> start WalletVersion2Wallet function [debug] 30.09.2026, 07:13:53.299 (UTC) <MainThread> start GetDbSize function ===[ Node status ]=== Node mode: LITESERVER Node ports: 30001 ADNL address of local validator: 9E34BDACD676033A4B9B6A757685D50436A1C53CF5039288EADD0128E4296A10 Public ADNL address of node: 987AA8F4CE08E4979140D785D991A4FDA35D0D93E2A56E9AECB02110064702C0 Load average[32]: 2.6, 2.68, 2.7 Network load average (Mbit/s): 53.7, 55.04, 63.97 Memory load: ram:[13.68 Gb, 11.3%], swap:[0.14 Gb, 6.6%] Disks load average (MB/s): sr0:[0.0, 0.0%], vda:[0.08, 0.33%], vdb:[17.18, 23.25%] Mytoncore status: working, 144 days Local validator status: working, 144 days Local validator out of sync: 55 Masterchain out of sync: 6 sec Shardchain out of sync: 55 blocks Local validator last state serialization: 0 blocks ago Liteserver queries for the past 60 sec (success/error): 75765/2316 Local validator database size: 1096.84 Gb, 82.6% Version mytonctrl: () Version validator: 3d478cb (master) Shardchain out of sync: 55 blocks Still > 10

some one help me ?

hello

ok thinks

Hi, how can I get in touch with the MyTonControl team? Could you provide me with a Telegram link or any other contact method?