Debug TON Vesting Contract Error

@trm66614

Hi there, Good evening I am Talha. I have read you project details i saw you need help with Smart Contracts, Blockchain and Git I am excited to submit my proposal for your project, which focuses on a comprehensive project plan. To begin, we will thoroughly understand your project's objectives and requirements, ensuring alignment on scope and goals. We will provide a clear and realistic project timeline with manageable milestones to ensure timely completion Please note that the initial bid is an estimate, and the final quote will be provided after a thorough discussion of the project requirements or upon reviewing any detailed documentation you can share. Could you please share any available detailed documentation? I'm also open to further discussions to explore specific aspects of the project. Thanks Regards. Talha Ramzan

@steveng96

Hello, and thank you for the detailed description of the TON vesting issue. I understand the contract runs correctly until the wallet notification, where Exit code 130 appears. I will share my wonderful previous project when we start a chat. I’ve worked extensively with TON, Tact, and low-level TVM behavior, including debugging gas forwarding and address serialization issues. Exit code 130 often points to bounce, invalid message mode, or insufficient gas during internal send. I’ll carefully trace the notification routine using toncli, TVM debugger, and transaction logs to pinpoint the exact trigger. After isolating the root cause, I’ll patch the Tact logic, validate gas allocation, and test the full vesting cycle on devnet before confirming on mainnet. You’ll receive the updated .tact/.fc file, a concise fix summary, and clear deployment steps. I’m confident we’ll eliminate the exit code and ensure reliable wallet notifications every time.

@danielboggs

Hi Client, I read your description closely and I’m confident I can find why Exit code 130 appears during the “Notifying wallet” step. I have hands-on experience with TON/Tact development, testing with toncli and the TVM debugger, and a solid background in Solidity, contract testing, dApp integration and security best practices. I’ll review the notification routine, trace the wallet-call path and gas/account handling, reproduce the failure from your repo and txs on devnet, and implement a minimal, well-tested patch in Tact. I will deliver the updated .tact/.fc file, test logs showing a full vesting cycle with zero exit codes, and concise deployment notes. Can you provide the repository link, a representative transaction hash, and the devnet/mainnet deployed addresses so I can reproduce the failing notification locally? Sincerely, Daniel

@mukhtara55

Hello, For over 3 years, I have worked to develop web applications based on React, Node.js, Python, and Laravel, and have had the opportunity to integrate blockchain solutions for various projects. I have worked extensively with blockchain platforms, and my experience with smart contracts and their execution on various chains aligns with the needs of your project. If you want, I can show my portfolio with similar projects involving smart contracts and blockchain solutions. Hope to contribute for your project. Mukhtar

@exequiel12ifran

Hello, I am a full-stack developer with 8 years of rich experience in software development, with file processing pipelines, image transformation workflows, automated asset conversion systems and scalable cloud based tools for gaming utilities. I would approach this by structuring a robust upload to conversion pipeline that detects pack structure automatically, processes textures and metadata through modular steps, and generates a fully validated mcpack output ready for download. The system would handle resizing, format normalization, animation mapping and compatibility checks in a clean and scalable backend architecture designed for speed and reliability. This project is a perfect fit for my skills and I am sure I can delivery this with high quality. Thanks for considering my proposal, — Lautaro