LogoLogo
WebsiteYellowpaperTechnical DocumentationNuNet History and Operation
NuNet Public Alpha on Testnet (Deprecated)
NuNet Public Alpha on Testnet (Deprecated)
  • NuNet in Brief
  • NuNet Architecture
  • Fundamental Algorithms
  • Testing Use Cases
    • Decentralized ML Use Case
      • Compute Provider on NuNet
      • Service Provider on NuNet
  • Testing Configuration
    • Nami Wallet Setup
    • Eternl Wallet Setup
    • Cardano Testnet Guide: Basic Outline
    • tADA Faucet: Get tADA for transactions
    • mNTX Faucet: Get mNTX for testing
  • Components Installation
    • DMS (Device Management Service)
    • NuNet CLI: For Device Onboarding
    • Compute Provider Dashboard
    • Service Provider Dashboard
  • Telemetry Information
  • Troubleshooting Tools
  • Testing Campaigns - Get Involved
    • Stage 1: Create wallet (using Nami or Eternl)
    • Stage 2: Onboard on NuNet
    • Stage 3: Act as a Service Provider
    • Stage 4: Act as a Compute Provider
    • Request mNTX and Faucet
  • ML Code Examples
  • Research Papers
    • Extending GPU Container Support to AMD and Intel: A Developer Approach for Decentralized Scaling
  • Disclaimer
Powered by GitBook
On this page
Export as PDF
  1. Testing Campaigns - Get Involved

Stage 4: Act as a Compute Provider

This page will detail Stage 4 testing campaign

PreviousStage 3: Act as a Service ProviderNextRequest mNTX and Faucet

Last updated 1 year ago

Please read NuNets before installing any software on your devices.

Testing Plan

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

1.4 Testing schedule

This campaign will run when requirements of testing is met.

Test Environment (Testing Steps)

2.1 Documentation

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

2.2 Monitoring and Reporting Tools

Community Participation

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

    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

  • Stage 3 Category

  • Stage 3 Forum

  • Communication Channel for Stage 3 testers

Contribution Guidelines

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

Report

Report will be added after testing is complete.

Disclaimer
Stage 1
Onboard Device
Install Compute Providers Dashboard
StatsDB
Issues Tracker
Contribution Guidelines