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.
FIG. 02How a VDXF request is made
Available →Thirteen chapters, from the object model and signature flags to envelopes, request families and ideals of synthesis.
- 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 in full · the index inside the book covers 06–13.
Scope: the book reads verus-typescript-primitives as cloned at 3ffa9d7 on main. Treat branch-specific behaviour as unverified until diffed against the generic-signed-request fork.
FIG. 03Identity Explorer
In developmentA neutral view of what identities publish — registrations, content maps, referral chains.
Unlinked in this plate: the target is in development. No address is bound to it yet.
FIG. 04Schemas
To followVDXF key namespaces and the payload shapes they carry, in one lookup.
Unlinked in this plate: the schema lookup is to follow.
FIG. 05Elsewhere in the stack
- VDXF overview — Verus docs ↗ The protocol’s own definition of VDXF: what it is for and why it exists.
- Build with data — Verus ↗ How on-chain data and identity content are used to build applications.
- verus-typescript-primitives ↗ The library this book reads — object model, serialisation, signing.
- verusid-ts-client ↗ The client layer above the primitives: build, sign and verify requests.