1.1 Objectives.

Stage 2 will focus on testing components in relations to onboarding community devices to NuNet and the discovery of other devices on the network.

Before participating in this Staged Test please read the Testing Configuration page.

1.2 Testing Type

This testing campaign will be focused on component testing. We will test DMS installation and onboarding devices to NuNet.

1.3 Scope of Testing

The following features and functionalities will be tested during this campaign

• Installing the DMS on community devices

• Running the DMS CLI - This will test onboarding devices, managing resources, wallets, and interactions with peers.

• Onboarding using wallet address created in Stage 1

• Testing Network Status Dashboard

• Peer Discovery

1.4 Testing schedule

This campaign will run from May 1st to May 8th

2.1 Documentation

This section includes the relevant links to documentation needed for this test stage:

• DMS (Device Management Software) Installation

• NuNet CLI - Command Line Interface (CLI) to onboard a device, manage resources, wallets, and interact with peers

• Connecting Test Wallets

• Network Status Board

• Video on how to onboard

2.2 Monitoring and Reporting Tools

• StatsDB

• Issues Tracker

4.1 Get Involved

Please join our Discord Server and head to #role-assignment click on 2️⃣ to be given access to the relevant testing channels.

In order to receive mNTX your wallet you will need to be added to our Testnet Stage 2 Whitelist to receive mNTX, you can find a link to the whitelist in the Welcome group on Discord Stage 2 category.

4.2 NTX Incentives

• Testers will be rewarded for the following:

• Bug discovery	Critical bugs discovered

4.3 Communication Channels

• Stage 2 Category

• Stage 2 Forum

• Communication Channel for Stage 2 testers

If you have any issues or bugs to report please follow our procedure outlined in our Contribution Guidelines page on GitLab

Report will be added after testing is complete.

1.1 Objectives

Stage 4 will focus on NuNet Compute Providers - deploying jobs, checking if they have ran successfully and testing payments for jobs ran on Compute Providers devices.

1.2 Testing Type

This testing campaign will be focused on Integration testing. Verifying that different components or modules work together as expected for Compute Providers.

1.3 Scope of Testing

The following features and functionalities will be tested during this campaign:

• Installing the Compute Provider Dashboard (CPD)

• Set/change resource parameters using the DMS CLI so this machine can be chosen to run a ML job

• Testing job deployment - waiting and see/monitor if any job was deployed and run successfully on this machine

• Payments - Claiming the NTX reward using the CPD and the wallet created on Stage 1

1.4 Testing schedule

This campaign will run when requirements of testing is met.

2.1 Documentation

This section includes the relevant links to documentation needed for this test stage:

• Onboard Device

• Install Compute Providers Dashboard

2.2 Monitoring and Reporting Tools

• StatsDB

• Issues Tracker

4.1 Get Involved

Please join our Discord Server and head to #role-assignment click on 3️⃣ to be given access to the relevant testing channels.

In order to receive mNTX your wallet you will need to be added to our Testnet Stage 3 Whitelist to receive mNTX, you can find a link to the whitelist in the Welcome group on Discord Stage 3 category.

4.2 NTX Incentives

• Testers will be rewarded for the following:

• Bug discovery	Critical bugs discovered

4.3 Communication Channels

• Stage 3 Category

• Stage 3 Forum

• Communication Channel for Stage 3 testers

If you have any issues or bugs to report please follow our procedure outlined in our Contribution Guidelines page on GitLab

Report will be added after testing is complete.

1.1 Objectives.

Stage 1 will focus on testing components in relation to Creating test wallets and receiving mNTX that will be needed to perform other tests.

1.2 Testing Type

This testing campaign will be focused on component testing. We will test mNTX and Testnet wallet functions in isolation.

1.3 Scope of Testing

The following features and functionalities will be tested during this campaign

• Using PreProd Cardano Network - Ensuring the community is able to create a PreProd Cardano Wallet

• Adding tADA - Adding tADA to testers wallets

• mNTX workflow - Testing the workflow in place to monitor and track community wallets, GitLab and Discord Names to determine rewards.

• Adding mNTX - Adding mNTX to testers wallets

• Test community communication - Testing communication workflows between NuNet team and community testers

1.4 Testing schedule

This campaign will run from April 28th to May 1st.

2.1 Documentation

This section includes the relevant links to documentation needed for this test stage:

• Create PreProd Cardano Wallet (Eternl or Nami) and Adding tADA

• Nami Website

• Eternl Website

• Add wallet to mNTX whitelist (Head to Discord and Join the Stage 1 testing Group)

  • mNTX Faucet Guidelines

4.1 Get Involved

Please join our Discord Server and head to #role-assignment click on 1️⃣ to be given access to the relevant testing channels.

In order to receive mNTX your wallet you will need to be added to our Testnet Whitelist to receive mNTX.

4.2 NTX Incentives

• Testers will be rewarded for the following:

• Bug discovery	Critical bugs discovered

4.3 Communication Channels

• Add your wallet to the mNTX Whitelist

• Stage 1 Forum

• Communication Channel for testers

If you have any issues or bugs to report please follow our procedure outlined in our Contribution Guidelines page on GitLab.

NuNet is happy to share its first Public Alpha Testnet Report with our community. This report will focus on Stage 1: Create a wallet (using Nami or Eternl).

Testing scope

The following features and functionalities will be tested during this campaign

• Using PreProd Cardano Network - Ensuring the community is able to create a PreProd Cardano Wallet

• Adding tADA - Adding tADA to testers wallets

• mNTX workflow - Testing the workflow in place to monitor and track community wallets, GitLab and Discord Names to determine rewards.

• Adding mNTX - Adding mNTX to testers wallets

• Test community communication - Testing communication workflows between NuNet team and community testers

Results

• Assigned Tester Role: 68

• Number of whitelisted wallets: 56 (Within Stage 1 Timeframe)

Using PreProd Cardano Network

• Success

• Some improvements in relation to documentation to remind users that we will only use test wallets for the campaign and only test wallets can receive mNTX.

• Some small bugs with Eternl configuration wallet where the plugin got disconnected, testers refreshed and got it working again.

• Remind users that collateral has to be set up and to connect wallets in the Dapp.

Adding tADA

• Success

mNTX workflow and Adding mNTX

• Success

• Suggestion to create a message on the faucet that reads ‘Wallet not whitelisted’.

Test community communication

• In general it worked well. Some small improvements can be made based on community feedback such as direct links to testing campaigns and instructions.

1.1 Objectives

Stage 3 will focus on testing deploying jobs from the Service Provider Dashboard.

1.2 Testing Type

This testing campaign will be focused on Integration testing. Verifying that different components or modules work together as expected for Service Providers.

1.3 Scope of Testing

The following features and functionalities will be tested during this campaign

• Installing the Service Provider Dashboard (SPD)

• Using the SPD and the wallet created on Stage 1 request to run a ML job (this will lock the mNTX funds)

• Waiting and checking to finish the ML job and review results

1.4 Testing schedule

This campaign will run from May 22nd and from next week will work with Stage 4(Acting as a Compute Provider). IMPORTANT Stage 4 Delay We are waiting until we can test / prove multiple jobs can be run by a service provider. Once we prove we have lots of jobs successfully running it will mean most users will have mNTX to claim. We expect at least one update to DMS and the SPD before we are at that point. We are expecting new releases of Compute provider dashboard next week. (Week commencing 22nd May)

2.1 Documentation

This section includes the relevant links to documentation needed for this test stage:

• If you haven't already, complete Stage 1 and Stage 2.

• Install Service Provider Dashboard.

• Enable debugging mode using the info in the troubleshooting tools section.

• Follow the steps to use the Service Provider Dashboard.

• Please post your successes or issues into the stage 3 Discord chat. Which will allow us to gauge how well things are working.

2.2 Monitoring and Reporting Tools

• Please log any problems you come across in the Issues Tracker

4.1 Get Involved

Please join our Discord Server and head to #role-assignment click on 4️⃣ to be given access to the relevant testing channels.

In order to receive mNTX your wallet you will need to be added to our Testnet Stage 4 Whitelist to receive mNTX, you can find a link to the whitelist in the Welcome group on Discord Stage 4 category.

4.2 NTX Incentives

• Testers will be rewarded for the following:

• Bug discovery	Critical bugs discovered

4.3 Communication Channels

• Stage 3 Category

• Stage 3 Forum

• Communication Channel for Stage 3 testers

If you have any issues or bugs to report please follow our procedure outlined in our Contribution Guidelines page on GitLab

Report will be added after testing is complete.

Video Walk Through

https://youtu.be/JkHLTqXeTZs

Step 1

You must have completed stages 1 and 2 so that you have a Pre-Production Testnet wallet with some mNTX, and have onboarded your device to NuNet (everyone has to allocate some resources to NuNet, even those ordering jobs as a service provider). Check that you have some DHT peers with the "nunet peer list" command before proceeding.

Step 2

Download and install the service provider dashboard and access it using localhost:9991 in your browser.

Instructions: https://docs.nunet.io/nunet-public-alpha-testnet/components-installation/service-provider-dashboard

Step 3

-Press ctrl+shift+i on localhost:9991 and click the Console tab so you can see that the process is working at all times.

-Connect your PreProd Tesnet wallet to localhost:9991

-Paste in this URL to the web app to order its machine learning script: https://gitlab.com/nunet/ml-on-gpu/ml-on-cpu-service/-/raw/develop/examples/cpu-ml-test-scikit-learn.py

-Choose CPU

-Choose Low

-Click "Please enter any additional required dependencies" and type in matplotlib

-Enter 30 (minutes) as the estimated time

-Click Next

Step 4

On the next page of the web app

-Check that the wallet address matches your own

-Enter an amount of mNTX to spend (1000 may work)

-Submit and sign the transaction in your wallet

Step 5

Wait for the job to complete. DO NOT refresh the web page, this will prevent you from seeing if the job completes. You should see in the Console (ctrl+shift+i) when the job completes.

Please report any errors or problems you have completing this process on the Gitlab issue submission page (with the exception of the issue stated below): https://gitlab.com/nunet/documentation/-/issues

IMPORTANT: It is currently a known issue that you cannot order a second job, even after the first one completes. Please only order one job and do not report that a second one cannot be ordered, this issue is already being fixed.