Open Standards

Veydrin
Protocols

Open specifications for data interchange and community coordination. Built in public, licensed free, designed to outlast any single organization.

Specifications

VODS · Base Standard
Veydrin Open Data Standard

The base envelope for all Veydrin domain data exports. Defines the export identity, anonymization model, extensions namespace, and versioning contract. Domain specs (OHDS, OCEADS) inherit this envelope.

v1.0 Stable Base Layer CC-BY-4.0
OHDS · Domain Spec
Open Hive Data Standard

A universal interchange format for beekeeping citizen science data. One privacy-first export maps to BIP, COLOSS, HoneyBeeNet, and any future program. Built on VODS.

v1.0 Stable Builds on VODS CC-BY-4.0
OCEADS · Domain Spec
Open Controlled Environment Agriculture Data Standard

Soilless cultivation data interchange for hydroponic, aeroponic, aquaponic, fungal, and all controlled environment systems. Fields verified against NASA Advanced Plant Habitat parameters. Builds on VODS.

v1.0 Stable Builds on VODS CC-BY-4.0
VFDS · Domain Spec
Veydrin Financial Data Standard

The portable, privacy-preserving data format for household financial sovereignty and trust lifecycle data. Vault hierarchy, seven financial layers, ownership entity trees, encrypted document bundles, and offline-first storage. Built on VODS.

v1.0 Draft Builds on VODS CC-BY-SA-4.0
VCN · Community Spec
VCN Community Spec

The organizational governance layer for the Veydrin Community Network. Nine rules, node federation, peer-onboarding, trust badge, enforcement framework, and the relationship between nodes and the network.

v1.0 Stable Network Governance CC-BY-4.0
VCN · Protocol Spec
VCN Protocol Spec

The technical implementation standard for VCN-enabled applications. Node identity, packet format, six transport tiers, dedicated node mode, geohash/OSM addressing, Bloom filter sync, and the vcn_node package interface.

v1.0 Stable Network Transport AGPL-3.0
Open by default

All specs are CC-BY-4.0. Fork them, adopt them, build on them.

Spec before implementation

Every standard is written before any application implements it.

Privacy-first

The anonymization model is part of the standard, not an afterthought.

Designed to outlast

If the Veydrin Order disappears tomorrow, the specs and directory remain forkable and maintained by anyone.