Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update testnet11.md #380

Merged
merged 5 commits into from
Jan 7, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 5 additions & 7 deletions docs/testnet11.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,13 +6,13 @@ In the future testnet 11 will act as a staging zone for all sorts of crazy exper

## The first experiment

The goal of the first experiment is to stress load the network in terms of block rates and transaction rates, in varying network conditions. In particular, we are curious to see how the network responds to *mildly* varying hash rates, so we encourage users to freely join and leave the network, or set up several nodes. **However**, we kindly ask users not to abuse the hashrate and **only use the included CPU miner**. Turning on a GPU rig (or, god forbid, a KS02) to increase the global hashrate by 10000% at once might be amusing, but not very productive.
The goal of the first experiment is to stress load the network in terms of block rates and transaction rates, in varying network conditions. In particular, we are curious to see how the network responds to *mildly* varying hash rates, so we encourage users to freely join and leave the network, or set up several nodes. **However**, we kindly ask users not to abuse the hashrate and **only use the [CPU kaspa miner](https:/elichai/kaspa-miner)** (which is currently the only miner that supports testnet-11). Turning on a GPU rig (or, god forbid, a KS02) to increase the global hashrate by 10000% at once might be amusing, but not very productive.

## Overview

On the software side, participating requires three components:
1. *kaspad* - the Kaspa client
2. *kaspaminer* - the Kaspa miner
2. *kaspa-miner* - the Kaspa CPU miner
3. *Rothschild* - a transaction generator

The Rothschild tool is used to create a wallet, and once the wallet has some funds within, Rothschild will continuously create transactions from that wallet back to itself at the prescribed rate.
Expand All @@ -27,7 +27,7 @@ Since we want the test condition to be as close as possible to organic, we encou

The venue for discussing and monitoring the experiment will be the \#testnet channel on Discord. We encourage participants to describe the experience in general, and also tell us what hardware they are using and how well it handles the load.

The minimal hardware requirements are 16GB of RAM, preferably a CPU with at least 8 cores, and an SSD drive with at least 50GB of free space (the 100GB for a safety margin is preferable).
The recommended hardware requirements are 16GB of RAM, preferably a CPU with at least 8 cores, and an SSD drive with at least 100GB of free space (the 150GB for a safety margin is preferable). It might also be possible to operate with 8GB of RAM, by passing the `--ram-scale=0.6` parameter to `kaspad`.

## Setup Instructions

Expand Down Expand Up @@ -66,13 +66,11 @@ If you want to transmit transactions, first create a Rothschild wallet

Like kaspad, the Rothschild window should remain open and undisturbed.

For mining, grab the `kaspaminer` from within the latest [Go release](https:/kaspanet/kaspad/releases) and run it with the following flags:
For mining, grab `kaspa-miner` from within the latest [Release](https:/elichai/kaspa-miner/releases) and run it with the following flags (**this is currently the only miner that supports testnet-11**):
```
kaspaminer --testnet --miningaddr <address> --target-blocks-per-second=0
kaspa-miner --testnet --mining-address <address> -p 16210 -t 1
```

If you intend to run Rothschild, replace ``<address>`` with the address of the wallet generated by ``rothschild``, you should then wait for a while before your wallet accumulates enough funds. Assuming several dozen participants, 20 minutes should be more than enough. If you just mine for the sake of mining, you could use any address, such as the one provided in the example above.

The ``--target-blocks-per-second=0`` is important, without it the miner will limit itself to creating one block per second.

Like the Kaspad and Rothschild windows, the miner window should also be left undisturbed, and closing it will stop the mining.