Go to file
derekpierre 10b6e74854
Update versions of pre-commit, ruff - for pre-commit hooks.
2024-05-28 08:55:21 -04:00
.github Update old ruff command/options that currently have a deprecation warning. 2024-05-28 08:18:43 -04:00
deploy removes ursula extra from docker file; relayer docker file for faster build speed 2024-03-25 13:32:34 -04:00
examples Update ritual id for testnet examples - use ritual 0 for lynx that now uses polygon amoy. 2024-04-10 09:04:15 -04:00
newsfragments Add dev newsfragment for #3507. 2024-05-28 08:09:12 -04:00
nucypher Add a default freshness check for SIWE messages - this prevents perpetual reuse of the same SIWE message. 2024-05-16 19:46:42 -04:00
scripts rework dependency relock script to use poetry 2024-03-25 13:32:31 -04:00
tests Add a default freshness check for SIWE messages - this prevents perpetual reuse of the same SIWE message. 2024-05-16 19:46:42 -04:00
.bumpversion.cfg Bump version: 7.3.0 → 7.4.0 2024-05-13 09:25:49 -04:00
.coveragerc Update coverage configuration to allow for better categorization of coverage reporting. 2022-11-14 18:07:53 -05:00
.dockerignore cloudworkers: clean disk space more thoroughly, stop containers first 2021-03-27 12:11:57 -07:00
.flake8 removes documentation build support. 2023-10-30 23:13:12 +01:00
.gitignore Move PRE examples to their own subfolder. 2023-09-28 11:53:20 -04:00
.pre-commit-config.yaml Update versions of pre-commit, ruff - for pre-commit hooks. 2024-05-28 08:55:21 -04:00
CODE_OF_CONDUCT.md Add "end-of-file-fixer" to pre-commit hooks 2020-05-19 14:28:29 -04:00
CONTRIBUTING.rst remove Pipenv 2024-03-25 13:32:28 -04:00
LICENSE Relicense to AGPLv3 for more freedom 2019-03-04 18:55:28 -08:00
MANIFEST.in Cleanup build process 2024-02-07 21:09:10 +01:00
Makefile remove Pipenv 2024-03-25 13:32:28 -04:00
README.md Minor update to README - update discord link and TACo section title. 2024-04-18 13:37:33 -04:00
SECURITY.md removes documentation build support. 2023-10-30 23:13:12 +01:00
codecov.yml Fix code coverage to only focus on the `nucypher` folder. 2023-01-09 09:37:27 -05:00
dev-requirements.txt Add siwe (sign-in with ethereum) package dependency and relock dependencies. 2024-05-14 16:53:01 -04:00
mypy.ini Ignore setup.py in mypy configuration. 2020-05-28 11:59:47 -07:00
nucypher.png Relocate nucypher.png and releases.rst to the project root. 2023-10-30 23:13:12 +01:00
poetry.lock Add siwe (sign-in with ethereum) package dependency and relock dependencies. 2024-05-14 16:53:01 -04:00
pyproject.toml Update old ruff command/options that currently have a deprecation warning. 2024-05-28 08:18:43 -04:00
pytest.ini Run coverage directly and not through pytest-cov - there are discrepancy in reports. 2022-11-16 11:14:32 -05:00
releases.rst Release Notes for v7.3.0 2024-05-07 15:39:38 +02:00
requirements.txt Add siwe (sign-in with ethereum) package dependency and relock dependencies. 2024-05-14 16:53:01 -04:00
setup.cfg Reconfigure setup.py; External deps, code cleanup, post install hook, installation options. 2020-05-28 11:59:08 -07:00
setup.py updates search keywords on pypi 2024-03-25 13:32:35 -04:00

README.md

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.

pypi pyversions codecov discord license


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 here: https://docs.threshold.network/applications/threshold-access-control

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.