Friendly communication identity
Canonical VIX registry identity such as VIX_FRED controls enrolled devices and conversations.
Protocol, identity, node and integration documentation.
This documentation surface describes the current live architecture and clearly separates operational capabilities from planned or connector-ready features.
VIX-MSG message model
CLIENT DEVICE
generate / hold local private agreement + signing keys
↓
VIX-MSG ENVELOPE
fresh AES-256-GCM content key
X25519 + HKDF recipient key wrap
Ed25519 device signature
authenticated metadata + replay identifier
↓
AUTHENTICATED MAILBOX
recipient-wallet + recipient-device scoped
↓
VIX PROOF
hash / route / receipt metadata only
plaintext: excluded
Identity model
Chain wallet identity
A BIX address can bind to a VIX identity only after Ed25519 challenge-response and exact public-key address derivation.
Group model
VIX-MSG 2.3 currently uses pairwise E2EE fanout for groups. Group metadata tracks membership and epoch; each message is encrypted independently to each active member device, avoiding a single long-lived server-visible group key. MLS remains the intended scale-up path for larger asynchronous groups.
Node platform
Root of trust
Chain authority, entitlement signing, policy, revocation and update governance.
Managed edge
Customer-controlled admin, relay, messaging and isolated hosting connected to the master trust fabric.
Integration families
Connector targets include FIX/FIXP/FIXS, ISO 20022, mTLS APIs, SFTP, AS2/AS4, PKI/X.509, PIV/CAC-compatible identity, IPsec/IKEv2 and Web3 asset adapters. These are connector families; availability depends on implementation profile and authorization.