Access Control
Overview
One of the main advantages of Orbis is globally available data, accessible by anyone directly.
On top of that, all Orbis-powered applications are interoperable thanks to a set of standardized schemas.
However, maintaining privacy and allowing anyone to have a space (Context) of their own is important to us.
This is why Orbis comes built-in with Access Control in the form of Access Gating and Encryption.
These features are not mutually exclusive. An example is an encrypted DAO channel to which only specific token holders can add content.
| Access Gating | Encryption | |
|---|---|---|
| Content Control | Who can write | Who can read |
| Content Storage | Ceramic | Ceramic |
| Handled by | Orbis Nodes | Lit Protocol |
| Rules | DIDs, Credentials, Token & Metadata Gating | Token Gating, Custom Logic |
| Rules can be combined | ✅ [or] | ✅ [or, and] |
| Multi-chain | ✅ | ✅ |
Access Gating
Access Gating allows you to control who can add content to your Contexts.
This allows you to restrict input based on built-in rules which may include token-gating, a set of DIDs, Credentials or a combination of all three.
Learn more about Access Gating
Encryption
Encryption, handled by Lit Protocol, allows you to trustlessly restrict read access to your space.
It's handled by Lit's Nodes in a decentralized manner and encryption keys are never stored in a single place thanks to threshold cryptography.