Cryptographic primitives, hosted on the decentralized nodes of the Threshold network, offering accessible, intuitive, and extensible runtimes and interfaces for secrets management and dynamic access control.
Threshold Access Control (TACo)
TACo is end-to-end encrypted data sharing and communication, without the requirement of trusting a centralized authority, who might unilaterally deny service or even decrypt private user data. It is the only access control layer available to Web3 developers that can offer a decentralized service, through a live, well-collateralized and battle-tested network.
See more in the TACo docs.
Getting Involved
NuCypher is a community-driven project and we're very open to outside contributions.
All our development discussions happen in our Discord server, where we're happy to answer technical questions, discuss feature requests, and accept bug reports.
If you're interested in contributing code, please check out our Contribution Guide and browse our Open Issues for potential areas to contribute.
Security
If you identify vulnerabilities with any nucypher code, please email security@nucypher.com with relevant information to your findings. We will work with researchers to coordinate vulnerability disclosure between our stakers, partners, and users to ensure successful mitigation of vulnerabilities.
Throughout the reporting process, we expect researchers to honor an embargo period that may vary depending on the severity of the disclosure. This ensures that we have the opportunity to fix any issues, identify further issues (if any), and inform our users.
Sometimes vulnerabilities are of a more sensitive nature and require extra precautions. We are happy to work together to use a more secure medium, such as Signal. Email security@nucypher.com and we will coordinate a communication channel that we're both comfortable with.
A great place to begin your research is by working on our testnet. Please see our documentation to get started. We ask that you please respect testnet machines and their owners. If you find a vulnerability that you suspect has given you access to a machine against the owner's permission, stop what you're doing and immediately email security@nucypher.com.
4 maintainers
Metadata
4 maintainers
Release files for nucypher 7.6.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| nucypher-7.6.1.tar.gz | 283.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nucypher-7.6.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 615.6 kB
Release files / nucypher-7.6.1.tar.gz
| Download URL | nucypher-7.6.1.tar.gz |
|---|---|
| Size | 283.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f7ae86ddf5421e3aac70ee2f68fde1e5d2a85a644d1b4a30e98dd5ddaf1592d5
|
|
BLAKE2b-256 checksum How to use checksums |
d25966834b9c1a172b43913aba0255c50ed68b09cc9656a2275a31e15927a6af
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 24, 2025.
Transparency logRelease files / nucypher-7.6.1-py3-none-any.whl
| Download URL | nucypher-7.6.1-py3-none-any.whl |
|---|---|
| Size | 332.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a39f9dfe261cf0643df05dc28e9081783416441c22e4cb06f7c11a4dcdd663c7
|
|
BLAKE2b-256 checksum How to use checksums |
07263e5283a0239afc12c563480c755ed6ab3f643bd3be0761cd9bf7dd448d1f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 24, 2025.
Transparency log
