Skip to main content
Diagnosing Web3 errors is complex and hard, that’s why development teams have adopted War Rooms in response to high-stakes errors and hacks. With Tenderly you can now adopt a War Room procedure and be ready when the problem arises. Detect issues faster If the number of contracts in the transaction is greater than 30 then Call Trace will be automatically triggered. You can switch it yourself if you’re only interested in seeing external calls that are usually crucial for the attack. Use Expression Evaluation to better understand the whole context of the transaction and simplify debugging process. Collaborate and prioritize With the new annotation system, you can leave comments on the exact line of code you think caused the issue. Annotations can be used to make team collaboration more efficient or to leave a note for yourself so you don’t forget it later. You can also set a priority for traces you want inspected first.

​
Tenderly in War Rooms

Get familiar with the features that can help you understand and debug your code faster and collaborate with your team:

Tenderly War Rooms: The Aid Kit You Need in Time-Sensitive Scenarios

​
Anatomy of a Good Emergency Procedure

We tapped into Yearn Finance’s best-in-class procedures to give you an overview of the War Room best practice:

The Anatomy of a Good Emergency Procedure [Yearn Finance Case Study]