ton-bug-triage

Reproduce TON blockchain bugs on a local tontester network.

15|6|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/ton-blockchain/ton-triage-skill --skill ton-bug-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ton-bug-triage
Source: https://github.com/ton-blockchain/ton-triage-skill/tree/main/ton-bug-triage
Command: npx skills add https://github.com/ton-blockchain/ton-triage-skill --skill ton-bug-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of reproducing bugs within the TON Blockchain on a local test network, significantly speeding up debugging and validation for developers.

Core Features & Use Cases

  • Local Bug Reproduction: Use tontester to reliably reproduce validator-level bugs.
  • Contract Deployment & Testing: Deploy contracts to a local network and test their behavior under specific conditions.
  • Build Comparison: Compare different validator builds to isolate issues.
  • Use Case: A developer suspects a bug in the TON validator's consensus mechanism. They can use this Skill to set up a local network with specific configurations, introduce conditions that might trigger the bug (e.g., malformed packets, mixed builds), and observe the outcome, collecting evidence for a fix.

Quick Start

Use the ton-bug-triage skill to reproduce a TON bug by deploying a contract and sending it a specific internal message.

Frequently Asked Questions about ton-bug-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reproduce a TON blockchain bug locally?

To reproduce a TON blockchain bug locally, use the tontester network to deploy contracts and execute specific transactions, modifying validator behavior to observe the outcome under controlled conditions.

Can I test validator behavior on a local TON network?

Yes, you can test validator behavior on a local TON network by launching validators with specific configurations and introducing conditions like malformed packets to trigger and observe consensus bugs.

What is the best way to compare patched TON validator builds?

The best way to compare patched TON validator builds is by running deterministic scripts that deploy contracts and launch validators, allowing you to isolate issues and collect evidence for fixes.

Do I need a local tontester network to debug TON contract transactions?

Yes, using a local tontester network is required for deterministic TON bug verification, as it allows you to reliably reproduce validator-level bugs and test contract behavior safely.

How does local TON bug verification work for consensus issues?

Local TON bug verification works by setting up a local network with specific configurations, introducing trigger conditions like mixed builds, and observing the validator's response to collect evidence.