Tips
Last updated
Last updated
Part of the involves installing . This is a great tool for keeping an eye on the tanks in your armada as well as investigating failed scenarios. If a scenario fails, you can use k9s to access the logs.
The warnet auth command from the page automatically sets up your kubernetes context so that you can access your armada through k9s.
To start k9s, all you have to do is open a new terminal tab and run:
Warnet has a bunch of commands you can use. Here's an example of getting the status of your armada:
A full list of Warnet commands can be found here:
If you aren't familiar with the Bitcoin Core functional test framework, this is a list of existing tests you can review to better understand how it can be used for p2p scenarios and to gather inspiration for your next attack:
There are a number of ways to access the logs for a commander running a scenario. The easiest thing to do is add the --debug option when executing a scenario. For example,
You can also use warnet logs or warnet logs -f which will provide a list of tanks (kubernetes pods), one of which is your scenario.
Lastly, you can also use k9s. Select your tank (kuberenetes pod), and press l to see the logs.
Some attacks may require you spend some BTC. Fortunately, the tanks in your armada have wallets that are automatically funded with BTC! For more information, see this section:
If you're interested, it's possible to set up a local Warnet battlefield so you can test out your scenarios in a more controlled environment. You can use it to debug questions like "is the victim getting the right message?" or check if memory use is increasing.
To set this up, see the "scrimmage" instructions in this README:
