Seal brings onchain access control and threshold encryption to developers, providing a secure and flexible way to manage sensitive data, whether it's for encrypted storage, gated content, private messaging, or beyond!
Why Seal?
A ton of Web3 apps need secure data access — whether for encrypted storage, gated content, private messaging, and more. Right now, options are:
- Web2 solutions (AWS KMS, GCP Cloud KMS)
- Niche Web3 products (wallet-specific encryption or purpose-specific privacy tool)
Seal offers a generalized, decentralized alternative that integrates easily with any app or protocol, without sacrificing flexibility or security.
How it Works
- Onchain Access Control
Seal uses smart contracts written in Move to define flexible decryption policies, determining exactly who gets access to data and when.
- Threshold Encryption
Encryption keys are never stored in a single place. Instead, trust is distributed across a network of Seal key store services, eliminating single points of failure.
- Client-Side Encryption
Data is encrypted and decrypted locally by users, ensuring that sensitive information remains private.
- Storage Agnostic
Seal doesn't care where data is stored, it works with any storage layer, including decentralized storage solutions like Walrus.
What This Enables
With Seal, developers can build:
- Protect user data without relying on centralized key management
- Gate content for creators, NFT owners, DAOs, or private communities
- Secure private messaging for dApps
- Enable time-locked asset transfers with encryption-based handovers
Built for Builders
- Seal is designed to be plug-and-play. With the SDK, developers get:
- Scalability — Threshold encryption = no single point of failure
- Transparency — Onchain access controls
- Flexibility — Policies work across use cases
Example use cases
- Gated content — Monetize premium content on-chain
- Game logic — Encrypted assets and gated story progression
- Web3 messaging — End-to-end encrypted chats
- Secure NFT transfers — Set time-locks or dynamic access rules