<aside> 👉 What is TACo?
Threshold Access Control enables end-to-end encrypted data sharing and communication without the need to trust a centralized authority. It is the only access control layer available to Web3 developers that has already achieved true decentralization through a live and well-collateralized network, with sensitive cryptographic operations disassembled and distributed across ~150 independently operated nodes. Note that decentralization currently applies to the Proxy Re-Encryption service only, and the independence between nodes is observable, but not provable.
The Threshold Access Control service is built on two distinct technologies; Conditions-Based Decryption (CBD) and *Proxy Re-Encryption* (PRE), both of which provide end-to-end-encryption-as-a-service. PRE access control is currently executed by a decentralized array of Threshold nodes, and the same array will execute CBD access control once it launches (see the v.7.0.0 roadmap).
</aside>
| Name | Links |
|---|---|
| Docs | https://docs.threshold.network/applications/threshold-access-control |
| Github | https://github.com/nucypher/nucypher |
| Roadmap | https://github.com/orgs/nucypher/projects/31/ |
📔 Threshold Access Control (TACo) Documentation
🖲️ Conditions-Based Decryption (CBD) Documentation
Stakers Recruitment Brainstorming
| Task | DAO Members contributing |
|---|---|
| Naming (4.d) | , |
| Market research (4.a) | , , , |
| DAO tooling use cases | , , |
| Stakers Recruitment |