RFC-001: The Yadal Open Protocol Specification
A decentralized, DNS-anchored framework for authentic two-way communications, zero-noise personal vault routing, and cryptographic career verification.
Abstract & Architectural Motivation
The original internet architecture decoupled transport from trust. In SMTP (Simple Mail Transfer Protocol), any server can attempt delivery to any mailbox. This design flaw transformed personal inboxes into a multi-billion dollar landfill of marketing spam, unsolicited sales pitches, and tracking pixels.
Simultaneously, professional networking platforms (such as LinkedIn) created a feudal model of identity: corporate employers issue credentials, but upon departure, employees are digitally evicted. Resumes remain unverifiable without 3-week manual screening agencies ($100+ per check), resulting in rampant resume fraud and toxic offboarding disputes.
Identity Grammar & Handle Structure
Yadal distinguishes between sovereign personal identity and corporate career roles using an unambiguous ABNF grammar:
DNS Cryptographic Record Schemas
Any organization becomes an authoritative issuer by publishing two standard DNS records in their authoritative nameservers:
v: Protocol version (must be YADAL1) • t: Entity type (org | person | ed) • pubkey: Organization Ed25519 public key.
Points all employment verification and relieving dispute escrow requests to a verified edge clearinghouse.
Edge DoH Resolution Protocol
Resolution is performed through DNS-over-HTTPS (RFC 8484) with sub-15ms worldwide response times via Cloudflare's global edge network:
Two-Sided Employment Lifecycle
Employment is treated as a cryptographic multi-signature state machine between the corporate domain root and the employee's lifelong Human Anchor:
Threat Model & Security Guarantees
Build on the Yadal Protocol
Join the working group, test the live resolver API, or reserve your permanent Human Anchor today.