Veritas record integration

PATENT PENDING — Ma'atara Protocol. Reviewed 21 September 2026.

This SDK guide retains the historical /developer/block-preimage URL for existing links. The internal byte-level specification is not published here.

Select the supported profile

The portable SDK supports native Veritas v4. Current Core includes native v4 reads and appends. Use the endpoint's declared profile and supported SDK/transport contract. Never relabel a stored record or infer compatibility from similar fields.

Validate a portable record

After toolkit initialization, adapt its identity and signature methods:

import { validateBlockV4 } from '@maatara/veritas-chain/v4';

const encodeUtf8 = (value: string) =>
  btoa(String.fromCharCode(...new TextEncoder().encode(value)))
    .replace(/\+/g, '-')
    .replace(/\//g, '_')
    .replace(/=+$/, '');

const verification = {
  deriveDid: (publicKey: string) => proto.tree.didFromPublicKey(publicKey).did,
  verifySignature: (publicKey: string, message: string, signature: string) =>
    proto.pqc.verify(encodeUtf8(message), signature, publicKey),
};
const errors = validateBlockV4(record, verification);
if (errors.length > 0) throw new Error(errors.join('; '));

record is the received portable record; proto is the initialized toolkit. The validator owns canonical processing. The adapter supplies SDK identity binding and signature verification. Neither callback may return constant success.

Use validateBlockTransitionV4 for each successor with its predecessor and required authority approval. Check completeness and current lifecycle authority separately. An isolated signature does not establish authorship, legal identity or independently witnessed time.

Signing and transport

Use released SDK types and record helpers with an approved endpoint signer. Do not serialize arbitrary objects and assume their signing contracts are identical. Keep private keys off the network and transmit only supported ciphertext and public evidence.

Follow Core API for service calls and Anchors for external commitments. Legacy aliases and silent conversion are not integration mechanisms. Temporary healing is retired (HTTP 410).

Identity derivation, canonical message layouts and protocol replication recipes remain outside this public integration guide.