Congested Testnet design

High level concept

The congested testnet will simulate high loads by sampling spam transactions with characteristics similar to the historical congestion distribution, as detailed in the statistics
The testnet will be open to public access.
A publicly available tADA faucet will be provided on the testnet for developers.
The testnet will offer a mechanism to submit custom transactions.

Architechture

In our Cardano testnet, some nodes will be integrated with the following APIs:

Faucet API. This api will be connected with few testnet nodes annd will be used to send 1000 tADA to a specified address.
```
curl -X POST ".../faucet" \
    -H "Content-Type: application/json" \
    -d '{"address": $USER_ADDRESS}'
```
User. The user can interact with the testnet using ogmios/kupo to submit transactions and access the faucet to receive test ADA
Prometheus.This database stores logs from each node in the testnet, allowing us to estimate the current mempool usage percentage for each node and calculate the average mempool usage across the entire testnet.
Spammer.
- Spammer continually submits random transactions in round robin manner to each node on the testnet in order to simulate congestion as in historical peak
- The size of the transaction and its CPU/memory usage will be regulated by alwaysTrue validators performing varying computational tasks.
- Transaction parameters such as transaction size, cpu/mem usage will be sampled from congestion distribution
- It will be built on top of Cardano transaction library(CTL) which connects with testnet nodes via ogmios and kupo.
- All necessary data for spam transactions, such as random addresses, scripts, and policies, along with parameters from the congestion distribution, will be stored in database (SpammerDB).
- Spammer will query Prometheus to check whether to continue generating spam or to stop.