Skip to content
A proxy re-encryption network to empower privacy in decentralized systems.
Branch: master
Clone or download
cygnusv Merge pull request #830 from KPrasch/denominations
Base Denominations Management
Latest commit 3f94b93 Mar 19, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci Automated demo testing, reorganized nucypher entry point scripts; Tes… Mar 7, 2019
deploy Update networks.json Mar 9, 2019
docs
examples Merge pull request #782 from mallek/postmancollection Mar 15, 2019
nucypher Merge pull request #830 from KPrasch/denominations Mar 19, 2019
scripts Deploy then stake example script Mar 12, 2019
tests Merge pull request #830 from KPrasch/denominations Mar 19, 2019
.bumpversion.cfg
.coveragerc
.coveralls.yml Try on some coveralls Dec 3, 2018
.gitignore
CODE_OF_CONDUCT.md Add Getting Started section, Code of Conduct, and symlink to Contribu… Feb 5, 2019
CONTRIBUTING.rst Add Getting Started section, Code of Conduct, and symlink to Contribu… Feb 5, 2019
LICENSE Relicense to AGPLv3 for more freedom Mar 5, 2019
Pipfile Automated demo testing, reorganized nucypher entry point scripts; Tes… Mar 7, 2019
Pipfile.lock Updates Pipfile.lock Feb 23, 2019
README.md Change "block rewards" to "token rewards" Feb 28, 2019
dev-requirements.txt Post rebase cleanup for stakling CLI over native CLI Mar 10, 2019
mypy.ini
pytest.ini
readthedocs.yml Include readthedocs.yml Jan 28, 2019
requirements.txt
setup.cfg
setup.py Use official AGPL trove classifier. Mar 8, 2019

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. Using her policy's public key, any entity can encrypt data on Alice's behalf. This entity could be an IoT device in her car, a collaborator assigned the task of writing data to her policy, or even a third-party creating data that belongs to her – for example, a lab analyzing medical tests. The resulting encrypted data can be uploaded to IPFS, Swarm, S3, or any other storage layer.

  3. A group of Ursulas, which are nodes of the NuCypher network, receive the access policy and stand ready to re-encrypt data in exchange for payment in fees and token rewards. Thanks to the use of proxy re-encryption, Ursulas and the storage layer never have access to Alice's plaintext data.

  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.

You can’t perform that action at this time.