What’s DDO?
DDO (DaaS Data Object) is the basic packet format used to exchange data between nodes in the DaaS network. The definition of DDO is part of the ‘DaaS Protocol Specifications’.
The DDO is encoded by the source node and decoded at the destination. To make this possible, metadata is used to specify how the packet was created.
In addition to the information to be transferred (payload), the DDO structure also includes the source node address, timestamp, and a key code called ‘typeset’. Typeset is a sub-code used to carry all the information needed to decode and process the packet at the destination node:
The DDO is exchanged via another structure, called DDE (DDO Exchanging Packet), which encapsulates the DDO by adding additional details:
Ultimately, within a DaaS network, all data packets flow carrying all the information needed to manage the exchange process:
What’s Typeset?
The typeset is a 32-bit integer used to encode control information associated with a DDO (DaaS Data Object).
Its structure is interpreted through bitwise masking logic, where each group of bits represents a specific attribute.
Field Structure
level [1 : .daas, 0 : .user]
Discriminates the type of message:
- 1 (.daas) – Service messages handled exclusively by the node stack.
- 0 (.user) – Messages containing user-defined data.
The LibDaas interface only exposes and processes DDO.user, while DDO.daas are internally managed by the node.
reserved
Reserved space for future protocol extensions. Must be set to 0 when unused to ensure backward and forward compatibility.
sequence
When the value is greater than 0, it indicates that the DDO packet is part of a sequence of fragments generated by the source node to transfer an extended data block.
The sequence field holds the total number of fragments, required for proper reassembly on the receiving node.
Fragmentation and recomposition are synchronized according to the network timestamp, ensuring data integrity and consistency.
format [0 : .binary, 7 : .json]
Defines the payload encoding format:
- 0 – Binary encoding (.binary).
- 7 – JSON encoding (.json).
This enables seamless interoperability between low-level binary data and human-readable structured formats.
code
Payload classification code, used to identify the type or category of data being transmitted.
This field can be leveraged for routing, filtering, or processing logic at the node level.