Serialization & Wire Formats

@qubiq/core/serialization keeps the tricky byte layouts close to the original C++ codebase. Downstream SDKs reuse these helpers for signing flows, transaction builders, and any custom transport layers they implement.

Transaction encoding

import { encodeTransaction, decodeTransaction } from "@qubiq/core/serialization";

const encoded = encodeTransaction({
  sourcePublicKey: "ab".repeat(32),
  destinationPublicKey: "cd".repeat(32),
  amount: BigInt(1_000_000),
  tick: 123,
  inputType: 1,
  inputSize: 0,
  signature: "ef".repeat(64),
});

const parsed = decodeTransaction(encoded);

• Layout: 32-byte source + 32-byte destination + 8-byte amount + 4-byte tick + 2-byte input type + 2-byte input size + payload + 64-byte signature.
• Guards: Zod schema validation, signature length enforcement, payload/inputSize consistency checks.
• Works with both Uint8Array and hex strings.

Request/response headers

import {
  encodeRequestResponseHeader,
  decodeRequestResponseHeader,
  REQUEST_RESPONSE_HEADER_SIZE,
} from "@qubiq/core/serialization";

const headerBytes = encodeRequestResponseHeader({
  size: 1024,
  type: MessageType.REQUEST_TICK_DATA,
  dejavu: 42,
});
const header = decodeRequestResponseHeader(headerBytes);

• Implements the 24-bit size + 1-byte type + 4-byte dejavu format the node expects.
• Validates MessageType enums and throws when the payload exceeds 24-bit constraints.

Byte helpers

Re-exported from @qubiq/core/utils/bytes:

import { hexToBytes, bytesToHex, concatBytes } from "@qubiq/core/utils";

Use them to prepare payloads before encoding transactions or contract calls.

Tests & fixtures

• tests/serialization/transaction.test.ts double-checks encoding/decoding parity.
• Use fixtures with automation pipelines to ensure offline bundles or queue dispatchers emit the exact bytes expected by the network.