integration

Qubic Core Network

[!IMPORTANT] The Qubic Core Main-Net runs on TCP Sockets with Port 21841

The Qubic Test-net runs on TCP Port 31841

The default Buffer size is defined in BUFFER_SIZE with 33554432

Table of Content

Qubic Core Network

General Concepts

todo: explain used crypto, private/public key, signing/verify

Term	Description
Epoch	An epoch describes a period of time in which the network runs without resetting the nodes data.
Tick	A Tick is a Block in Qubic. It describes one Block in the Blockchain
TickLeader	The TickLeader is the Computor which is responsible for a certain Tick

Basic Communication Structure

Communication in Qubic is basically a continious TCP Stream. All starts with the RequestResponseHeader which contains the information about the current Packet to be transfered.

struct RequestResponseHeader
{
private:
    unsigned char _size[3];
    unsigned char _type;
    unsigned int _dejavu;
    // ... code cutted
}

_size => The size of the Packet. Total size including Header size.
_type => Type of Packet. Refer to Qubic Types
_dejavu => Marker to know if a packet was relayed, new or if we already know it. It is also used in replies to mark a response as an answer to your request.

A complete Qubic TCP Packet is defined by:

RequestRepsonseHeader
Payload

Examples / Use Cases

We provide you same use cases to understand how to interact with the Qubic API.

When talking to the Qubic Network and you don’t operate your own Computor be careful to use only trusted Peers.

[!IMPORTANT] To get reliable information, use only trusted Peers to request data.