Skip to content
Halo

Born Between 2 Generals · Principal Channel

Halo — principal-grade encrypted comms

A private, verifiable channel for the Board Chair and the inner circle. End-to-end encrypted messaging over a closed trust network with an auditable key model.

5
Active members
?
Active membersPeople currently in the closed trust network. Revoked members are excluded.
7
Active devices
?
Active devicesEach member can enroll one or more devices; every device has its own key. Messages are sealed once per active device. Revoked devices are excluded.
3
Channels
?
ChannelsEncrypted conversations (1:1 or group). Open any channel from the Channels tab.
8
Sealed messages
?
Sealed messagesMessages stored as encrypted envelopes. The server holds ciphertext only — never the plaintext.

Key transparency

ledger.verify
$ halo verify --ledger
entries: 14
head: 24563f80360985d953c246c1570aba13…
chain: INTACT — no entry altered, reordered, or removed

Anyone holding the ledger can recompute this chain. Open the full ledger →

What Halo guarantees

End-to-end encryption

Messages are sealed per recipient device with X25519 + AES-256-GCM. The server stores ciphertext envelopes only.

Closed trust network

Invite-only. The network can grow only through a single-use invite issued by an existing active member.

Key transparency

Every key event is written to a hash-chained ledger you can re-verify — added, rotated, or revoked.

No metadata harvesting

Only routing data needed to deliver an envelope is kept. No read receipts, no contact graph mining, no ads.

Open channelsManage trust network

Ask AI

AI can be wrong. Not medical, legal, or financial advice.

Signal-grade claims are pending independent crypto review. This is a runnable MVP of the architecture, not a hardened production deployment.