HDMEx

Human Decentralized Message Exchange

Human layer.

Offline-first P2P exchange of encrypted messages and files, carried by participants and synchronized when connectivity returns.

Chroma Guard: rotating keys + on-chain open-token for offline reliability.

How it works

Encrypt on-device (message/file + metadata).

Create a delivery intent (optional encapsulated payment instructions).

No server required to start.

A carrier (Vx) relays the encrypted payload offline (local link / file / QR).

Delivery is confirmed by the recipient (Dx).

No plaintext exposure.

PoP records delivery/relay/validation events.

When connectivity returns, events sync and become blocks.

Validators (Va) finalize.

Roles: C initiates and pays • Vx carries • Dx confirms • Va finalizes.

Modes: COURSE = one-time delivery • BAL = persistent mailbox.

BIP-39 seed onboarding → secp256k1 keys; encrypted key storage (Secure Enclave/Keystore), not the seed.
Chroma Guard: SHA3-256 + AES-256-GCM + HDMEX-Stretch (64MiB RAM, 3×SHA-3) with KMonth schedule keys.
Activity-driven rotation: Activityₙ hash → XOR into Chroma → SHA3, reducing harvest-now/decrypt-later risk.
Offline fail-safe: on-chain Token (Header|Body|Tag) encapsulates KF via Ktoken = KMonthₙ XOR SHA3-256(addr_D), internal HDMEx addressing.

Internal HDMEx addressing is separate from external wallet addresses.

Carriers (Vx) are paid per successful delivery.

In COURSE: Cx funds the reward → Vx receives 97% after Dx confirmation (3% fee).

Validators stake and validate blocks under PoP rules.

Rewards are paid for block production / finalization.

Payment instructions and/or decrypt keys can travel with the encrypted payload (file/QR), offline.

Settlement happens when devices reconnect and validation is recorded.

A single section per day is readable; come back tomorrow to discover the rest.

Loading today’s rotation…