Skip to content

README.md

Latest commit

 

History

History
136 lines (100 loc) · 5.47 KB

README.md

File metadata and controls

136 lines (100 loc) · 5.47 KB

Qubic - Monero POC

Highlevel Process Description

Qubic - Outsourced Computing Highlevel Monero POC Process FlowChart

Click here for PDF

QUBIC's Monero Wallet Address

Wallet address and view key are valid per epoch and shared after an epoch ends on the Qubic discord.

POC Phases

The POC is junked into Phases.

  1. Basic Testing of Messaging ✅
  2. Connect Qubic Messaging with Monero (Bridging)✅
  3. End-To-End Messaging (including signaling and real monero tasks) ✅
  4. Solution Validation (Oracle) and Revenue Calculation ✅
  5. Final Test Round ✅
  6. Go-Live ✅ See stats page

The Principle

For the POC we need high speed delivery of tasks and solutions. We will build on top of the Qubic Broadcast Message to achieve this.

Threfore we introduce two new message types:

  1. #define MESSAGE_TYPE_CUSTOM_MINING_TASK 1

  2. #define MESSAGE_TYPE_CUSTOM_MINING_SOLUTION 2

  3. Custom Mining Task This type is used by ARB to send out a Task. The interval between tasks is dynamic and may vary from a few seconds up to a few 10s of seconds.

The Task struct

struct
{
    unsigned int sizeAndType;
    unsigned int dejavu;

    unsigned char sourcePublicKey[32]; // the source public key is the DISPATCHER public key
    unsigned char zero[32];  // empty/zero 0
    unsigned char gammingNonce[32];

    unsigned long long taskIndex; // ever increasing number (unix timestamp in ms)

    unsigned char m_template[896]; // monero block template

    unsigned long long m_extraNonceOffset; // offset to place extra nonce
    unsigned long long m_size; // size of template
    unsigned long long m_target; // target difficulty
    unsigned long long m_height; // current network height
    unsigned char m_seed[32]; // seed hash for XMR

    unsigned char signature[64];
} task;

Note

The shared key for Destination=0 is all-zeros

To verify the message, please refer to https://github.com/qubic/core/blob/main/src/qubic.cpp#L474 To find the message type, please refer to https://github.com/qubic/core/blob/main/src/qubic.cpp#L555

  1. Custom Mining Solution After Processing the Task and generating the solution. The solution needs to be sent back to the network.

The Solution struct

struct
{
    unsigned int sizeAndType;
    unsigned int dejavu;

    unsigned char sourcePublicKey[32];
    unsigned char zero[32]; // empty/zero 0
    unsigned char gammingNonce[32];

    unsigned long long taskIndex; // sohuld match the index from task
    unsigned long long combinedNonce; // (extraNonce<<32) | nonce
    unsigned long long encryptionLevel; // 0 = no encryption, 2 = EP173+ encryption
    unsigned long long computorRandom; // random number which fullfils the condition computorRandom % 676 == ComputorIndex
    unsigned long long reserve2; // reserved
      
    unsigned char result[32];   // xmrig::JobResult.result

    unsigned char signature[64];
} solution;

Caution

The Above structs already contain the RequestResponseHeader.

What Monero mining software to be used?

For the POC we gonna try with XMRig. If you want to user your own. Feel free to do so.

How to receive a task?

Connect to the network and listen for the packet type BROADCAST_MESSAGE (1).

Identify a Task:

  1. The source must be DISPATCHER
  2. Verify Signature
  3. Check the Message type (sample: https://github.com/qubic/core/blob/main/src/qubic.cpp#L555)
  4. Verify taskIndex is higher than previous loaded task

If the above match, use that task and proceed with solution finding.

How to send back a solution?

If you have found a solution, pack it into the solution struct.

  • sourcePublicKey must be your computor public key
  • taskIndex must be the task indes from recevied task
  • combinedNonce must be the xmrig::JobResult.nonce + your extranonce ((extraNonce<<32) | nonce) and equal to a value such that firstComputorIndex + nonce % (676 / task.NumberOfUpstreams) == computorIndex
  • encryptionLevel must be 2 = EP173+ Encryption; 0 is allowed for legacy purposes
  • computorRandom (ex reserve1) must be a random number and equal a value such that computorRandom % 676 == computorIndex; 0 is allowed for legacy purposes
  • result must be the result from xmrig::JobResult.result

Sign your solution packet with your computor seed. make the dejavu = 0 to allow propagation of your solution in the network.

Caution

Non encrypted solutions are legacy and may be not accepted by ARB. Please use latest encryption level.

How to encrypt the solution?

Please reach out to the core development team with a signed message from your computor to receive latest instructions.