User Controlled Authorization Networks (UCANs) are decentralized, capabilities model authorization tokens.
UCAN is a trustless, secure, local-first, user-originated authorization and revocation scheme. UCAN is designed to be very flexible: you can use it offline, online, fully P2P, federated, or with central servers.
Please see the specs for more detail on implementation.
If you're interested in contributing to the development of UCANs, check out the GitHub Discussions. Introduce yourself and your project, and what you're looking to do with UCANs, and join the next community call to meet others. The Discord server is low volume and high signal, feel free to drop in.
- UCAN Token & Capabilities Format (🏁 start here!)
Below are listed specifications that are still relevant but should be updated to match the v1 core specifications.
- Testing
- Website
Note that while the below all describe UCAN at the time they were written, the spec has undergone updates. Please refer to the latest specs if you have questions.
- Connecting IPFS users and permissions to DIDs with UCAN (2022)
- Lightweight Credentials with UCAN (2021)
- UCAN (do) secure key management in a browser (2021)
- Coding Earth: Authorizing Users without a Backend (2020)
