# Testnet Guide

## Introduction

This guide provides information on what you can expect during this testnet phase.\
Our key objectives for this permissioned testnet are.

## Objectives

During Venn's testnet phase we will work to reach the following KPIs:

1. [False Negative](#user-content-fn-1)[^1] Ratio of **10% or less**
2. [False Positive](#user-content-fn-2)[^2] Ratio of **1% or less**
3. Response Time of **500ms or less**

## What To Expect?

As we go through the testnet phases, we will be onboarding select node operators onto Venn. Once your node is up and running *(see* [*Installation*](https://docs.venn.build/venn-network/getting-started/node-operators/installation)*)* it will actively participate in each of these phases, strengthening Venn's security and performance.

* For phase one, Venn will replay 70 hacking transactions for inspection twice a day
* For phase two, Venn will replay [all transactions for hacked protocols](#user-content-fn-3)[^3] from January 1st 2023 to the present day
* After setup, our engineering team may get in touch with software updates as needed

## Testnet Phases

Fine tuning Venn to reach these APIs will be completed in systematic phases.

### 1. False Negatives

{% hint style="info" %}
Phase 1 is currently in progress
{% endhint %}

* **Goal**\
  Minimize false negatives<br>
* **Test Set**\
  Transactions from at least 70 hacked protocols on mainnet Ethereum, from January 1, 2023 to the present<br>
* **Procedure**\
  Simulate all 70 transactions on all operators twice daily<br>
* **Rationale**\
  During this first phase, we'll make sure Venn can collectively identify hacked transactions, ignoring any other noise in the data<br>

### 2. False Positives

* **Goal**\
  Minimize false positives<br>
* **Test Set**

  All transactions from the same 70 protocols, starting from January 1st 2023 to present day<br>
* **Procedure**

  Cycle simulations based on overall network performance<br>
* **Rationale**\
  Now that Venn surgically detects the hacked transactions, we want to make sure it truthfully signs off on any and all other interactions for the same protocols in the test data

### 3. Performance

* **Goal**\
  Onboard operators at scale<br>
* **Test Set**\
  Up to 20 operators for this permissioned-phase testnet<br>
* **Procedure**\
  We will gradually onboard more nodes as we progress through the test phases, supporting operators and iterating on performance improvements<br>
* **Rationale**\
  This allows us to responsibly onboard node operators onto Venn, while still cycling through our test phases with fast iterations

## Test Data

We chose 70 hacked protocols for their diversity in industry, total value locked (TVL), attack vectors, and stolen goods.

This heterogeneous mix allows us to fine-tune Venn's malicious transaction detection system, ensuring broad and effective coverage.

{% hint style="info" %}
As we progress through iterations cycles, we will be releasing more information about the results of each phase and the hacked protocols that have been used for the tests
{% endhint %}

## Support

We deeply appreciate your support and commitment to our vision of a secure Web3.\
For any assistance during the integration process or after, our technical support team is ready to help.

* **Join Venn Discord - T**o access support, join the Venn Discord community using the link below:\
  [Venn Discord - Join Here](https://discord.gg/97cg6Qhg)<br>
* **Open a Support Ticket -** Once in the Discord server, navigate to the `#support-ticket` channel and open a ticket. Our team will respond promptly to assist you

[^1]: Malicios transactions flagged by Venn as valid

[^2]: Valid transactions that are flagged by Venn as malicious

[^3]: Valid transactions as well as hacking transactions