Diagnosing Web3 errors is complex and time-consuming. This is why development teams have adopted War Rooms in response to high-stake errors and hacks. With Tenderly, you can now adopt a War Room procedure and be ready when a problem arises.
Detect issues faster
If the number of contracts in a transaction is greater than 30, then Call Trace will be automatically triggered.
You can switch it yourself if you’re only interested in seeing only external calls that are usually crucial for an attack. Use Evaluate Expression to better understand the whole context of the transaction and simplify the 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 to address an issue at a later point. You can also set a priority for traces that your team should inspect first.
War Rooms in Web3
How did they come about, why are they so important in Web3 and what are the elements that make them successful?READ MORE
Anatomy of a Good Emergency Procedure
We tapped into Yearn Finance’s best-in-class procedures to give you an overview of the best War Room practice.READ MORE
Tenderly in War Rooms
Get familiar with the features that can help you understand and debug you code faster and collaborate with your team.READ MORE