Go to file
MacLane Wilkison 7d363434b4 Relicense to AGPLv3 for more freedom 2019-03-04 18:55:28 -08:00
.circleci Temp fix for failed CLI jobs on CI only. 2019-02-15 00:30:48 -07:00
deploy Update Moe Services Env Var 2019-02-14 11:32:39 -07:00
docs Addressing RFCs from @derekpierre and @mswilkison 2019-02-21 10:12:47 +01:00
examples Update Enrico.from_public_keys calls to new API 2019-02-16 19:27:02 +01:00
nucypher Add some TODOs in MiningAdjudicator 2019-03-02 09:10:45 +01:00
scripts Install solidity v0.5.3 by default 2019-02-09 13:51:29 -07:00
tests Some comments and require messages. 2019-02-24 21:46:35 -07:00
.bumpversion.cfg Bump version: 0.1.0-alpha.13 → 0.1.0-alpha.14 2019-02-16 15:55:12 -07: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 Adding pyenv meta to gitignore. 2019-02-15 00:28:53 -07: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 Relicense to AGPLv3 for more freedom 2019-03-04 18:55:28 -08:00
Pipfile Updates Pipfile.lock 2019-02-23 12:37:19 +03:00
Pipfile.lock Updates Pipfile.lock 2019-02-23 12:37:19 +03:00
README.md Addressing RFCs from @derekpierre and @mswilkison 2019-02-21 10:12:47 +01:00
dev-requirements.txt Updates requirements 2019-02-23 12:37:20 +03: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 Updates requirements 2019-02-23 12:37:20 +03:00
setup.cfg Extrapolate more testing steps for CI workflows; Skip publication steps (preversion). 2018-12-05 16:16:59 -08:00
setup.py Fixes bad render of markdown in pypi project description (see #794). 2019-02-20 12:40:33 +01:00

README.md

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

pypi pyversions coveralls circleci discord Documentation Status license


The NuCypher network uses the Umbral threshold proxy re-encryption scheme to provide cryptographic access control for distributed apps and protocols. Applications can use the NuCypher network to facilitate end-to-end encrypted data sharing via sharing policies. Access permissions are baked into the underlying encryption, and access can only be explicitly granted by the data owner. Consequently, the data owner has ultimate control over access to their data. At no point is the data decrypted nor can the underlying private keys be determined by the NuCypher network.

  1. Alice, the data owner, grants access to her encrypted data to anyone she wants by creating a policy and uploading it to the NuCypher network.

  2. Anyone can encrypt data using Alice's policy public key. The resulting encrypted data can be uploaded to IPFS, Swarm, S3, or any other storage layer.

  3. Ursula, a miner, receives the access policy and stands ready to re-encrypt data in exchange for payment in fees and block rewards. Thanks to the use of proxy re-encryption, Ursula and the storage layer never have access to Alice's plaintext data nor her private key.

  4. Bob, a data recipient, sends an access request to the NuCypher network. If Bob was granted an access policy by Alice, the data is re-encrypted for his public key, and he can subsequently decrypt it with his private key.

More detailed information:

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.