Cryptographic Autonomy License: Difference between revisions
Jump to navigation
Jump to search
(Created page with " '''= "why we need a new kind of open source license for distributed P2P software".''' [https://medium.com/holochain/understanding-the-cryptographic-autonomy-license-172ac9209...") |
No edit summary |
||
| Line 18: | Line 18: | ||
[[Category:Cryptoledger Applications]] | [[Category:Cryptoledger Applications]] | ||
[[Category:P2P | [[Category:P2P Licensing]] | ||
Revision as of 09:31, 23 February 2019
= "why we need a new kind of open source license for distributed P2P software". [1]
Description
Arthur Brock:
"Holochain’s license boils down to this: You can run Holochain as free and open source software with a couple of conditions:
- The source code of Holochain and any derivative works must be provided under compatible open source terms which include this condition and the following condition related to privacy of cryptographic keys.
- You only have permission for “public performance” of Holochain (including use of its APIs for running your dApp) if you preserve each end-user’s privacy and autonomy of their private cryptographic keys.
If the privacy of user keys is compromised, then so is the ownership of their data, as well as user’s control of their own copies of the software."
(https://medium.com/holochain/understanding-the-cryptographic-autonomy-license-172ac920966d)