Go to file
David Núñez ea7cbfba49 Naive approach for a CircleCI workflow to test the heartbeat demo 2019-02-07 11:04:15 +01:00
.circleci Naive approach for a CircleCI workflow to test the heartbeat demo 2019-02-07 11:04:15 +01:00
deploy Rendering node icons on the client side with handlebars. 2019-02-02 21:02:34 -05:00
docs Bump version: 0.1.0-alpha.7 → 0.1.0-alpha.8 2019-02-05 16:55:24 -08:00
examples Naive approach for a CircleCI workflow to test the heartbeat demo 2019-02-07 11:04:15 +01:00
nucypher Bump version: 0.1.0-alpha.7 → 0.1.0-alpha.8 2019-02-05 16:55:24 -08:00
scripts Include missing nicknames in package data 2018-11-09 09:29:12 -08:00
tests Mocking Response with namedtuple. 2019-02-02 21:02:34 -05:00
.bumpversion.cfg Bump version: 0.1.0-alpha.7 → 0.1.0-alpha.8 2019-02-05 16:55:24 -08:00
.coveragerc add coveragrc 2018-06-25 15:34:15 -07:00
.coveralls.yml Try on some coveralls 2018-12-03 14:42:48 -08:00
.gitignore Transparent logo 2019-01-25 18:12:58 -08:00
CODE_OF_CONDUCT.md Add Getting Started section, Code of Conduct, and symlink to Contribution Guide 2019-02-05 15:13:23 -08:00
CONTRIBUTING.rst Add Getting Started section, Code of Conduct, and symlink to Contribution Guide 2019-02-05 15:13:23 -08:00
LICENSE Use conventional top-level package structures 2018-11-09 07:43:31 -08:00
Pipfile Update Dependency Locks, update to Hendrix 3.2.1 2019-02-05 16:32:51 -08:00
Pipfile.lock Update Dependency Locks, update to Hendrix 3.2.1 2019-02-05 16:32:51 -08:00
README.md Add Getting Started section, Code of Conduct, and symlink to Contribution Guide 2019-02-05 15:13:23 -08:00
dev-requirements.txt Update Dependency Locks, update to Hendrix 3.2.1 2019-02-05 16:32:51 -08:00
mypy.ini Tone-down mypy even more 2018-09-21 11:43:07 -07:00
pytest.ini Test results were not captured by CircleCI. Fixed. 2019-01-05 00:54:34 +01:00
readthedocs.yml Include readthedocs.yml 2019-01-28 14:52:07 -08:00
requirements.txt Update Dependency Locks, update to Hendrix 3.2.1 2019-02-05 16:32:51 -08:00
setup.cfg Extrapolate more testing steps for CI workflows; Skip publication steps (preversion). 2018-12-05 16:16:59 -08:00
setup.py Removes python 3.5 trove classifier, fixes quickstart examples bug. 2019-02-01 08:26:00 -08:00

README.md

A proxy re-encryption network to empower privacy in decentralized systems

Documentation Status


Whitepapers

Network

"NuCypher - A proxy re-encryption network to empower privacy in decentralized systems"

by Michael Egorov, David Nuñez, and MacLane Wilkison - NuCypher

Economics

"NuCypher - Mining & Staking Economics"

by Michael Egorov, MacLane Wilkison - NuCypher

Cryptography

"Umbral: A Threshold Proxy Re-Encryption Scheme"

by David Nuñez

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.