Architecture

Null should use a layered architecture so that identity ownership, message encryption, delivery, storage, and payments remain separable.

flowchart TD
    A[Web and mobile clients] --> B[Null SDK]
    B --> C[Identity registry]
    B --> D[Encryption layer]
    B --> E[Message relay network]
    B --> F[Encrypted storage]
    B --> G[Payment modules]
    C --> H[Wallet and smart accounts]
    G --> I[Supported blockchain networks]

Client

Responsible for key generation, encryption and decryption, the local message database, wallet signatures, contact permissions, the user interface, and secure backups.

Identity registry

Maps Null identifiers to communication keys and wallet-controlled proofs. It should not publish unnecessary personal information.

Relay network

Routes encrypted message envelopes and supports offline delivery.

Encrypted storage

Stores encrypted message payloads and files according to retention policies.

Payment modules

Handles requests, receipts, escrow, and supported settlement integrations — see Null Pay.