The VDXF protocol, made readable.█

VDXF is Verus’s data-definition layer — how identities, currencies and on-chain content describe themselves. This site is an independent reading of it: a book that walks the TypeScript primitives line by line, and a neutral explorer for the data identities actually publish.

Not affiliated with Verus. Built against the source at a pinned revision.

three doors

read

How a VDXF request is made

Thirteen chapters: the object model, the signature flags, the envelopes, the request families, and the ideals of synthesis.

available →
explore

Identity Explorer

A neutral view of what identities publish — registrations, content maps, referral chains.

in development
lookup

Schemas

VDXF key namespaces and the payload shapes they carry, in one lookup.

to follow

the book

  • 01Orientation — what this library is
  • 02The VDXF object model — version, type, key, data
  • 03Request, Response and the challenge hash
  • 04VerifiableSignatureData — a signature that explains itself
  • 05GenericEnvelope and GenericRequest — flags as a table of contents

13 chapters total — first five shown above.

This book reads the library as cloned at 3ffa9d7 on main. A fork maintains a generic-signed-request branch; the classes used here (envelope/, request/, login/, identity/, payment/, appencryption/, data/, provisioning/) are present on main, but line-level details may differ from that branch. Treat branch-specific behaviour as unverified until diffed against it.