Stage 1: Create wallet (using Nami or Eternl)

This page will detail Stage 1 testing campaign that will run from April 28th to May 1st.

Please read NuNets Disclaimer before installing any software on your devices.

Rewards for Stage 1 have stopped at 4pm UTC May 1st!

Testing Plan

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.

Test Environment (Testing steps)

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

Community Participation

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
  	Major bugs discovered
  	Minor bugs discovered
  Test case creation/improvement	New test cases created
  	Significant improvements to existing cases
  Bug fixing/code contributions	Critical bugs fixed
  	Major bugs fixed
  	Minor bugs fixed
  	Code improvements
  Community support/engagement	Helpful answers on forums
  	Knowledge-sharing (tutorials, articles)
  	Active moderation/ambassadorship
  Quality feedback/suggestions	High-impact suggestions
  	Moderate-impact suggestions
  	Low-impact suggestions

4.3 Communication Channels

• Add your wallet to the mNTX Whitelist

• Stage 1 Forum

• Communication Channel for testers

Contribution Guidelines

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

Report

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.