Documentation
VeilNet's post-quantum PKI tree and where it is rooted, the protocol every node runs, the guardian console beside a private sovereign network, and conflux, which puts a machine on the overlay.
Four documentation sets
- VeilNet architectureHow a gossip mesh with no centre differs from every other kind of zero trust, and the post-quantum PKI tree it runs on, rooted at an organisation's own root node or at Traveller.
- A gossip mesh with no centre, against other zero trust
- The post-quantum PKI tree, from root key to node
- Private sovereign and public networks
- The anchor protocolIdentity, realms, powers, taints, admission, reachability, routing, the gossip controls and blocks: the model every anchor in the tree follows.
- Identity, realms, delegation and powers
- Taints, admission and post-quantum sealing
- Discovery, routing, gossip controls and blocks
- The guardian stackThe optional console you host beside your own network: commissioning, renewal and revocation through its root node, online or fully offline, and its telemetry, on your own infrastructure under your own change control.
- The stack, role by role
- Realms, commissioning, renewal and revocation
- Online, offline or air-gapped deployment
- ConfluxOne binary that puts a machine on the overlay, with quick starts for the databases and open-source services people expose most.
- Install, join and the two modes
- Quick starts for databases and open-source apps
- Commands, realm controls and troubleshooting