Warnet project implementation with one-tank network and attack scenario #2

b-l-u-e · 2025-07-04T01:34:03Z

Overview

A complete Warnet project implementing a one-tank network with a single attack scenario for hands-on Bitcoin network analysis learning.

Implementation Details

Based on feedback from this comment

��️ Project Structure

Created complete Warnet project structure (warnet-demo/)
Implemented one-tank network configuration (94.0.0-5k-inv.yaml)
Added single scenario (my_first_attack_5kinv.py)

📚 Documentation

Enhanced README with comprehensive setup instructions
Added extensive links to main Warnet documentation
Provided detailed monitoring and progress watching guidance
Included multiple monitoring options (dashboard, CLI, direct access)

🎯 Key Features

One-tank network: Single node for simplicity and learning
Single scenario: Focused on basic network interaction
Clear instructions: Step-by-step deployment and execution
Multiple monitoring methods: Web dashboard, command line, direct node access
Progress watching: Real-time observation of attack execution

What Users Can Do

Deploy the one-node network with warnet deploy warnet-demo
Run the attack scenario with warnet run warnet-demo/scenarios/my_first_attack_5kinv.py
Monitor the tiny network using dashboard or CLI tools
Watch the attack progress in real-time
Understand basic Bitcoin network behavior

Testing

✅ Successfully tested deployment and scenario execution
✅ Verified monitoring capabilities work as documented
✅ Confirmed one-node network operates correctly

Add a beginner-friendly guide that teaches users how to: - Set up Warnet using standard installation workflow - Deploy Bitcoin networks with warnet new command - Run existing scenarios (miner_std, tx_flood, reconnaissance) - Monitor and interact with networks via dashboard This provides a simple entry point for new users to learn Warnet without requiring custom scripts or source installation.

- Created one-tank network (single node) - Implemented single scenario (my_first_attack_5kinv.py) - Enhanced README with comprehensive Warnet docs links - Added detailed monitoring and progress watching instructions - Provided multiple ways to monitor the tiny network - Clear step-by-step execution and observation guidance

pinheadmz

Sorry I think this needs a lot more effort. I appreciate you taking the time to put together this demo for the BDP website, but it's disorganized and nothing works. If you still want to work on this, please proof read your work by pretending to be a beginner, and naievly following the steps you write out, to see if you get any results.

pinheadmz · 2025-07-14T17:57:16Z

README.md

+```sh
+# Create virtual environment
+python3 -m venv .venv
+source ./venv/bin/activate


Suggested change

source ./venv/bin/activate

source .venv/bin/activate

pinheadmz · 2025-07-14T18:01:22Z

README.md

+- **Minikube** - Local Kubernetes cluster (recommended for beginners)
+- **Docker Desktop** - If you have Docker Desktop with Kubernetes enabled


Personally I think Docker Desktop is better for beginners because it has a GUI. I would assume Docker Desktop for mac users and minikube for linux users

pinheadmz · 2025-07-14T18:10:04Z

README.md

+This project includes a pre-configured one-node network. Deploy it with:
+
+```sh
+warnet deploy warnet-demo


I expected this to be warnet deploy networks/warnet-demo or warnet deploy networks/94.0.0-5k-inv. I was surprised this command worked but I realized its because your directory structure is not standard for warnet. I think it should be something like this (I created this using warnet new and then following the inquirer prompts):

warnet-demo/ ├── networks │ └── 5k-inv-attack │ ├── network.yaml │ └── node-defaults.yaml ├── plugins │ ├── __init__.py │ ├── simln │ │ ├── README.md │ │ ├── charts │ │ └── plugin.py │ └── tor │ ├── charts │ └── plugin.py └── scenarios ├── __init__.py ├── commander.py ├── ln_framework │ ├── __init__.py │ └── ln.py ├── ln_init.py ├── miner_std.py ├── reconnaissance.py ├── signet_miner.py ├── test_framework │ ├── __init__.py │ ├── ... └── tx_flood.py

pinheadmz · 2025-07-14T18:14:10Z

README.md

+Execute the included scenario to see the network in action:
+
+```sh
+warnet run warnet-demo/scenarios/my_first_attack_5kinv.py


Suggested change

warnet run warnet-demo/scenarios/my_first_attack_5kinv.py

warnet run warnet-demo/scenarios/my_first_attack_5kinv.py --debug

This might be more fun to show some running-time output of the scenario, but of course it will consume the shell foreground so for other commands like warnet dashboard we might not want to add --debug what do you think?

pinheadmz · 2025-07-14T18:54:04Z

README.md

+- Monitor transaction propagation across the network
+- Show you how nodes communicate and synchronize


So, I thought we were going to test an attack, literally https://github.com/bitcoin-dev-project/battle-of-galen-erso/blob/main/scenarios/my_first_attack_5kinv.py

What you have here is actually very cool and totally fine - but then we mine as well add 1-2 more nodes so we can actually see actual network propogation. Then go ahead and just rename the scenario something like propogation-check and instruct the user to do warnet dashboard etc

and THEN....
we can still run the attack from Galen Erso and watch a node die. (if you like?)

pinheadmz · 2025-07-14T18:59:48Z

README.md

+- **[Warnet Scenarios](https://github.com/bitcoin-dev-project/warnet?tab=readme-ov-file#scenarios)** - Learn how to create custom attack scenarios
+- **[Warnet Networks](https://github.com/bitcoin-dev-project/warnet?tab=readme-ov-file#networks)** - Understanding network configuration
+- **[Bitcoin Core Test Framework](https://github.com/bitcoin/bitcoin/tree/master/test/functional)** - Framework used by Warnet scenarios
+- **[Bitcoin Development Guide](https://bitcoin.org/en/development)** - General Bitcoin development resources


i think we can just drop this

pinheadmz · 2025-07-14T19:00:35Z

README.md

+
+- **[Warnet Documentation](https://github.com/bitcoin-dev-project/warnet)** - Complete guide to Warnet features and usage
+- **[Warnet Quick Start](https://github.com/bitcoin-dev-project/warnet?tab=readme-ov-file#quick-start)** - Step-by-step installation guide
+- **[Warnet Scenarios](https://github.com/bitcoin-dev-project/warnet?tab=readme-ov-file#scenarios)** - Learn how to create custom attack scenarios


Did you try these links? They don't work.

use

https://github.com/bitcoin-dev-project/warnet/blob/main/docs/scenarios.md

...etc.

pinheadmz · 2025-07-14T19:01:34Z

warnet-demo/plugins/simln/README.md

@@ -0,0 +1,123 @@
+# SimLN Plugin


let's remove the entire plugins/ directory, it's more advanced usage and not worth the confusion of including in an introductory guide.

pinheadmz · 2025-07-14T19:02:23Z

warnet-demo/warnet.yaml

@@ -0,0 +1,35 @@
+name: "warnet-demo"


What is this file for?

pinheadmz · 2025-07-14T19:03:27Z

warnet-demo/README.md

@@ -0,0 +1,132 @@
+# Warnet Demo Project


What's this extra README for? It describes a 5-node network which we don't have.

b-l-u-e · 2025-07-15T12:33:06Z

Thank you for your feedback..
I will resolve on changes suggested...
And proofread the setup and run it on new venv...
I had ran the demo on my existing venv...

b-l-u-e added 2 commits June 27, 2025 01:12

pinheadmz requested changes Jul 14, 2025

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Warnet project implementation with one-tank network and attack scenario #2

Warnet project implementation with one-tank network and attack scenario #2

Uh oh!

b-l-u-e commented Jul 4, 2025 •

edited

Loading

Uh oh!

pinheadmz left a comment

Uh oh!

pinheadmz Jul 14, 2025

Uh oh!

pinheadmz Jul 14, 2025

Uh oh!

pinheadmz Jul 14, 2025

Uh oh!

pinheadmz Jul 14, 2025

Uh oh!

pinheadmz Jul 14, 2025

Uh oh!

pinheadmz Jul 14, 2025

Uh oh!

pinheadmz Jul 14, 2025

Uh oh!

pinheadmz Jul 14, 2025

Uh oh!

pinheadmz Jul 14, 2025

Uh oh!

pinheadmz Jul 14, 2025

Uh oh!

b-l-u-e commented Jul 15, 2025

Uh oh!

Uh oh!

		- Minikube - Local Kubernetes cluster (recommended for beginners)
		- Docker Desktop - If you have Docker Desktop with Kubernetes enabled

	warnet run warnet-demo/scenarios/my_first_attack_5kinv.py
	warnet run warnet-demo/scenarios/my_first_attack_5kinv.py --debug

		- Monitor transaction propagation across the network
		- Show you how nodes communicate and synchronize

Warnet project implementation with one-tank network and attack scenario #2

Are you sure you want to change the base?

Warnet project implementation with one-tank network and attack scenario #2

Uh oh!

Conversation

b-l-u-e commented Jul 4, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Overview

Implementation Details

��️ Project Structure

📚 Documentation

🎯 Key Features

What Users Can Do

Testing

Uh oh!

pinheadmz left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

b-l-u-e commented Jul 15, 2025

Uh oh!

Uh oh!

b-l-u-e commented Jul 4, 2025 •

edited

Loading