A concise overview of HDMEx (stable).
HDMEx is a human decentralized message exchange built for offline-first missions.
Participants carry encrypted payloads locally and sync once links return.
Every package stays auditable through Proof of Participation (PoP) trails.
Wallet, explorer and APIs consume the same ledger so ops stay consistent.
Peer-to-peer (P2P) transport is the default path so that exchanges stay offline-first.
HDMEx packages a mission as a sealed intent: metadata, policy, audit hashes.
Messages, files and mission checklists can move without any central server.
Operators can prep drops on laptops, tablets or rugged field hardware.
The network remains verifiable even when coverage is intermittent.
P2P delivery keeps payload custody under human control instead of servers.
COURSE = one-time delivery: C initiates, Vx carries, Dx receives, then the mission ends.
BAL = persistent mailbox: a fixed drop zone that keeps accepting encrypted packages.
Both modes share the wallet, PoP, and explorer surfaces.
Encapsulated payment instructions or decrypt keys may travel with either mode.
C encrypts the payload (file/message + metadata) and creates a delivery intent.
A carrier (Vx) relays the sealed package offline (local link / file / QR).
The recipient (Dx) confirms with the previously derived keys.
Once online, those events synchronize to PoP and become blocks finalized by Va.
Roles: C initiates and pays • Vx carries • Dx confirms • Va finalizes.
Wallet UX compatible with common seed flows (BIP-39) and a local encrypted vault.
Chroma Guard rotates secrets (monthly or high-sensitivity daily) using on-chain activity as input.
File encryption uses standard primitives (SHA-3, AES-256-GCM; internal HDMEx KDF).
Offline-safe access: an “open token” can be published on-chain and addressed to the recipient to recover the file key later.
HDMEx uses its own internal addressing/identity format (separate from external wallet addresses).
PoP records relay/delivery/validation events and ties them to mission hashes.
Participants sign events locally; validators (Va) replay them into blocks.
Disputes are solved by replaying the encrypted audit trail bound to each event.
PoP powers explorer traces, validator incentives and compliance exports.
Delivery rewards: carriers (Vx) are paid once Dx confirms the mission funded by C.
Block validation rewards: validators (Va) earn for producing/finalizing PoP blocks.
Encapsulated payments: payment instructions/decrypt keys can travel with the payload for later settlement.
Incentives keep messaging, relay and validation aligned without centralized escrow.
Full publication in progress.
