Seven specs, one mission
Published on April 11, 2026 by Veydrin Admin
The Veydrin Order publishes seven open specifications. All free. All public. All built to outlast any single organization. Here is what each one is and why it exists.
The specs
- VODS. Veydrin Open Data Standard. The base envelope every domain-specific spec inherits from. Portable, signed, auditable. Every Veydrin data export starts here.
- OHDS. Open Hive Data Standard. Universal interchange for apiary, pollinator, forage, and harvest data. v1.1 adds harvests, pollinator observations, and forage observations as first-class record types.
- OCEADS. Open Controlled Environment Agriculture Data Standard. Hydroponic, aeroponic, fogponic, Kratky, aquaponic, bio-integrated, and fungal cultivation. Fields verified against NASA Advanced Plant Habitat parameters.
- VFDS. Veydrin Financial Data Standard. Household financial sovereignty and trust lifecycle data. Offline-first, encrypted, local-only by design.
- VRS. Veydrin Rating Standard. Decentralized, git-backed software ratings and usage counters. Ed25519-signed, publicly auditable, no app store required. v1.0 is final with real test vectors, conformance profiles, and a written threat model.
- VCN Community Spec. The organizational standard for community networks. Rules, federation model, trust badge, enforcement framework.
- VCN Protocol Spec. The technical protocol powering VCN. Peer-to-peer discovery, signed packets, no central server. v1.1 formalizes channel patterns, org founder identity, and a universal BLE service ID so any two VCN devices can find each other.
What this gives you
If you're building software that handles beekeeping data, pollinator surveys, controlled-environment agriculture, household finance, software ratings, or peer-to-peer communication, these specs give you a published, versioned, auditable foundation to build on. No license fees. No gated enterprise tier. No central authority you need permission from.
If you're just here to read how open protocols get written and defended, read the specs. They're written to be understood by people who weren't in the room.
Every spec lives publicly at veydrin.codeberg.page/protocols. Read them. Implement them. Fork them. Improve them.
In service to Life