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.

Sign up for GitHub

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

Jump to bottom

Update testnet11.md #381

Merged
merged 1 commit into from
Jan 7, 2024
Merged

Update testnet11.md #381

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 0 additions & 4 deletions docs/testnet11.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,10 +4,6 @@

In the future testnet 11 will act as a staging zone for all sorts of crazy experiments, allowing us to stress test various approaches and ideas on a global scale with the participation of the community. The approaches we decide to adopt will then be stress tested for longer periods on testnet 10 before being incorporated into the mainnet.

## 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 [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:
Expand Down