vdxf.net An independent reference for the Verus VDXF data-definition layer

The VDXF protocol, made readable.

VDXF is Verus’s data-definition layer — how identities, currencies and on-chain content declare what they mean. 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 Available

How a VDXF request is made

Thirteen chapters, from the object model and signature flags to envelopes, request families and provisioning.
Inspect In development

Identity Explorer

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

Reference Coming soon

Schemas

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

How a VDXF request is made

Thirteen chapters, from the object model and signature flags to envelopes, request families and ideals of synthesis. The book reads verus-typescript-primitives as cloned at the pinned revision below.

1Orientation — what this library is
2The VDXF object model — version, type, key, data
3Request, Response and the challenge hash
4VerifiableSignatureData — a signature that explains itself
5GenericEnvelope and GenericRequest — flags as a table of contents

13 chapters in the book index — first five shown here.

The full book index, The VDXF request lifecycle, continues at /docs/ in the full site. →

Elsewhere in the stack

VDXF overview — Verus docs docs.verus.io
The protocol's own definition of VDXF: what it is for and why it exists.
Build with data — Verus verus.io
How on-chain data and identity content are used to build applications.
verus-typescript-primitives github.com
The library this book reads — object model, serialisation, signing.
verusid-ts-client github.com
The client layer above the primitives: build, sign and verify requests.
The book reads verus-typescript-primitives 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.