3NWeb protocols
PrivacySafe is built on the open 3NWeb protocols, formats and conventions. They describe how apps and services can put user control, privacy and sovereignty first, and they are documented in the open at IEEE SA Open.
The specifications live at IEEE SA Open
This page is where the protocol documentation will be brought into the PrivacySafe docs, with the same layout and search as the rest of the site. Until then, the links below go to the current documents.
What the protocols are for
They describe a user-centric digital space where people can:
- operate in a connected cyberspace,
- use multiple devices fluidly,
- keep full control over their tools and data, and
- choose between different vendors and service providers.
Together these components work like an operating-system-like environment. PrivacySafe is the implementation: a suite of end-user apps built on the protocols and developed at github.com/PrivacySafe.
The protocol layers
| Part | What it is | What it does |
|---|---|---|
| MailerId | Verifiable and private identity | Issues verifiable identity certificates while no identity provider learns where or when an assertion is used. Clients sign requests and services verify them without tracking. |
| ASMail | End-to-end encrypted messaging | Messages are encrypted end to end. The sender's identity is revealed only to the recipient, and the server sees no message content or metadata. |
| 3NStorage | Encrypted network storage | Encrypted blobs are stored without file names, structure or metadata. Clients rebuild the file system locally, and versioning and events keep devices in sync. |
| XSP | The encrypted file format | The format 3NStorage uses for encrypted files. |
Read the specifications
- Architecture overviewNotes and specifications for the 3NWeb protocols, formats and conventions. Also on GitHub as 3NWeb-architecture.
- Server-client protocolsThe MailerId, 3NStorage and ASMail protocol documentation.
- XSP file formatDocumentation for the XSP encrypted file format.
- 3NWeb on IEEE SA OpenEvery 3NWeb repository, where contributions are made under the IEEE SA Open CLA.
- 3nweb.comThe 3NWeb project site.
Implementations
- 3NWeb client libraryLibraries for building compatible applications.
- Core 3NWeb client libraryCore processes, cryptographic and protocol state, local caches and APIs.
- WASM message passing for 3NWebMessage passing between WebAssembly and the 3NWeb platform.
- XSP filesImplementation of the XSP encrypted-file format used by 3NStorage.
- 3NWeb spec serverReference server implementation and specification test suite.
- 3NWeb serviceDeployment documentation and tooling for MailerId, ASMail and 3NStorage services.
Contribute
Contributions are welcome. Fork, remix and open pull requests as part of IEEE SA Open. Never send sensitive information about you or other users through direct messages or unencrypted email.
3NWeb architecture, protocol and file format documentation is licensed under the Apache License 2.0 and contributed through IEEE SA Open under the IEEE SA Open CLA. 3NSoft®, 3NWeb® and PrivacySafe® are registered trademarks.
