├── LICENSE └── README.md /LICENSE: -------------------------------------------------------------------------------- 1 | GNU GENERAL PUBLIC LICENSE 2 | Version 2, June 1991 3 | 4 | Copyright (C) 1989, 1991 Free Software Foundation, Inc., 5 | 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA 6 | Everyone is permitted to copy and distribute verbatim copies 7 | of this license document, but changing it is not allowed. 8 | 9 | Preamble 10 | 11 | The licenses for most software are designed to take away your 12 | freedom to share and change it. By contrast, the GNU General Public 13 | License is intended to guarantee your freedom to share and change free 14 | software--to make sure the software is free for all its users. This 15 | General Public License applies to most of the Free Software 16 | Foundation's software and to any other program whose authors commit to 17 | using it. (Some other Free Software Foundation software is covered by 18 | the GNU Lesser General Public License instead.) You can apply it to 19 | your programs, too. 20 | 21 | When we speak of free software, we are referring to freedom, not 22 | price. Our General Public Licenses are designed to make sure that you 23 | have the freedom to distribute copies of free software (and charge for 24 | this service if you wish), that you receive source code or can get it 25 | if you want it, that you can change the software or use pieces of it 26 | in new free programs; and that you know you can do these things. 27 | 28 | To protect your rights, we need to make restrictions that forbid 29 | anyone to deny you these rights or to ask you to surrender the rights. 30 | These restrictions translate to certain responsibilities for you if you 31 | distribute copies of the software, or if you modify it. 32 | 33 | For example, if you distribute copies of such a program, whether 34 | gratis or for a fee, you must give the recipients all the rights that 35 | you have. You must make sure that they, too, receive or can get the 36 | source code. And you must show them these terms so they know their 37 | rights. 38 | 39 | We protect your rights with two steps: (1) copyright the software, and 40 | (2) offer you this license which gives you legal permission to copy, 41 | distribute and/or modify the software. 42 | 43 | Also, for each author's protection and ours, we want to make certain 44 | that everyone understands that there is no warranty for this free 45 | software. If the software is modified by someone else and passed on, we 46 | want its recipients to know that what they have is not the original, so 47 | that any problems introduced by others will not reflect on the original 48 | authors' reputations. 49 | 50 | Finally, any free program is threatened constantly by software 51 | patents. We wish to avoid the danger that redistributors of a free 52 | program will individually obtain patent licenses, in effect making the 53 | program proprietary. To prevent this, we have made it clear that any 54 | patent must be licensed for everyone's free use or not licensed at all. 55 | 56 | The precise terms and conditions for copying, distribution and 57 | modification follow. 58 | 59 | GNU GENERAL PUBLIC LICENSE 60 | TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 61 | 62 | 0. This License applies to any program or other work which contains 63 | a notice placed by the copyright holder saying it may be distributed 64 | under the terms of this General Public License. The "Program", below, 65 | refers to any such program or work, and a "work based on the Program" 66 | means either the Program or any derivative work under copyright law: 67 | that is to say, a work containing the Program or a portion of it, 68 | either verbatim or with modifications and/or translated into another 69 | language. (Hereinafter, translation is included without limitation in 70 | the term "modification".) Each licensee is addressed as "you". 71 | 72 | Activities other than copying, distribution and modification are not 73 | covered by this License; they are outside its scope. The act of 74 | running the Program is not restricted, and the output from the Program 75 | is covered only if its contents constitute a work based on the 76 | Program (independent of having been made by running the Program). 77 | Whether that is true depends on what the Program does. 78 | 79 | 1. You may copy and distribute verbatim copies of the Program's 80 | source code as you receive it, in any medium, provided that you 81 | conspicuously and appropriately publish on each copy an appropriate 82 | copyright notice and disclaimer of warranty; keep intact all the 83 | notices that refer to this License and to the absence of any warranty; 84 | and give any other recipients of the Program a copy of this License 85 | along with the Program. 86 | 87 | You may charge a fee for the physical act of transferring a copy, and 88 | you may at your option offer warranty protection in exchange for a fee. 89 | 90 | 2. You may modify your copy or copies of the Program or any portion 91 | of it, thus forming a work based on the Program, and copy and 92 | distribute such modifications or work under the terms of Section 1 93 | above, provided that you also meet all of these conditions: 94 | 95 | a) You must cause the modified files to carry prominent notices 96 | stating that you changed the files and the date of any change. 97 | 98 | b) You must cause any work that you distribute or publish, that in 99 | whole or in part contains or is derived from the Program or any 100 | part thereof, to be licensed as a whole at no charge to all third 101 | parties under the terms of this License. 102 | 103 | c) If the modified program normally reads commands interactively 104 | when run, you must cause it, when started running for such 105 | interactive use in the most ordinary way, to print or display an 106 | announcement including an appropriate copyright notice and a 107 | notice that there is no warranty (or else, saying that you provide 108 | a warranty) and that users may redistribute the program under 109 | these conditions, and telling the user how to view a copy of this 110 | License. (Exception: if the Program itself is interactive but 111 | does not normally print such an announcement, your work based on 112 | the Program is not required to print an announcement.) 113 | 114 | These requirements apply to the modified work as a whole. If 115 | identifiable sections of that work are not derived from the Program, 116 | and can be reasonably considered independent and separate works in 117 | themselves, then this License, and its terms, do not apply to those 118 | sections when you distribute them as separate works. But when you 119 | distribute the same sections as part of a whole which is a work based 120 | on the Program, the distribution of the whole must be on the terms of 121 | this License, whose permissions for other licensees extend to the 122 | entire whole, and thus to each and every part regardless of who wrote it. 123 | 124 | Thus, it is not the intent of this section to claim rights or contest 125 | your rights to work written entirely by you; rather, the intent is to 126 | exercise the right to control the distribution of derivative or 127 | collective works based on the Program. 128 | 129 | In addition, mere aggregation of another work not based on the Program 130 | with the Program (or with a work based on the Program) on a volume of 131 | a storage or distribution medium does not bring the other work under 132 | the scope of this License. 133 | 134 | 3. You may copy and distribute the Program (or a work based on it, 135 | under Section 2) in object code or executable form under the terms of 136 | Sections 1 and 2 above provided that you also do one of the following: 137 | 138 | a) Accompany it with the complete corresponding machine-readable 139 | source code, which must be distributed under the terms of Sections 140 | 1 and 2 above on a medium customarily used for software interchange; or, 141 | 142 | b) Accompany it with a written offer, valid for at least three 143 | years, to give any third party, for a charge no more than your 144 | cost of physically performing source distribution, a complete 145 | machine-readable copy of the corresponding source code, to be 146 | distributed under the terms of Sections 1 and 2 above on a medium 147 | customarily used for software interchange; or, 148 | 149 | c) Accompany it with the information you received as to the offer 150 | to distribute corresponding source code. (This alternative is 151 | allowed only for noncommercial distribution and only if you 152 | received the program in object code or executable form with such 153 | an offer, in accord with Subsection b above.) 154 | 155 | The source code for a work means the preferred form of the work for 156 | making modifications to it. For an executable work, complete source 157 | code means all the source code for all modules it contains, plus any 158 | associated interface definition files, plus the scripts used to 159 | control compilation and installation of the executable. However, as a 160 | special exception, the source code distributed need not include 161 | anything that is normally distributed (in either source or binary 162 | form) with the major components (compiler, kernel, and so on) of the 163 | operating system on which the executable runs, unless that component 164 | itself accompanies the executable. 165 | 166 | If distribution of executable or object code is made by offering 167 | access to copy from a designated place, then offering equivalent 168 | access to copy the source code from the same place counts as 169 | distribution of the source code, even though third parties are not 170 | compelled to copy the source along with the object code. 171 | 172 | 4. You may not copy, modify, sublicense, or distribute the Program 173 | except as expressly provided under this License. Any attempt 174 | otherwise to copy, modify, sublicense or distribute the Program is 175 | void, and will automatically terminate your rights under this License. 176 | However, parties who have received copies, or rights, from you under 177 | this License will not have their licenses terminated so long as such 178 | parties remain in full compliance. 179 | 180 | 5. You are not required to accept this License, since you have not 181 | signed it. However, nothing else grants you permission to modify or 182 | distribute the Program or its derivative works. These actions are 183 | prohibited by law if you do not accept this License. Therefore, by 184 | modifying or distributing the Program (or any work based on the 185 | Program), you indicate your acceptance of this License to do so, and 186 | all its terms and conditions for copying, distributing or modifying 187 | the Program or works based on it. 188 | 189 | 6. Each time you redistribute the Program (or any work based on the 190 | Program), the recipient automatically receives a license from the 191 | original licensor to copy, distribute or modify the Program subject to 192 | these terms and conditions. You may not impose any further 193 | restrictions on the recipients' exercise of the rights granted herein. 194 | You are not responsible for enforcing compliance by third parties to 195 | this License. 196 | 197 | 7. If, as a consequence of a court judgment or allegation of patent 198 | infringement or for any other reason (not limited to patent issues), 199 | conditions are imposed on you (whether by court order, agreement or 200 | otherwise) that contradict the conditions of this License, they do not 201 | excuse you from the conditions of this License. If you cannot 202 | distribute so as to satisfy simultaneously your obligations under this 203 | License and any other pertinent obligations, then as a consequence you 204 | may not distribute the Program at all. For example, if a patent 205 | license would not permit royalty-free redistribution of the Program by 206 | all those who receive copies directly or indirectly through you, then 207 | the only way you could satisfy both it and this License would be to 208 | refrain entirely from distribution of the Program. 209 | 210 | If any portion of this section is held invalid or unenforceable under 211 | any particular circumstance, the balance of the section is intended to 212 | apply and the section as a whole is intended to apply in other 213 | circumstances. 214 | 215 | It is not the purpose of this section to induce you to infringe any 216 | patents or other property right claims or to contest validity of any 217 | such claims; this section has the sole purpose of protecting the 218 | integrity of the free software distribution system, which is 219 | implemented by public license practices. Many people have made 220 | generous contributions to the wide range of software distributed 221 | through that system in reliance on consistent application of that 222 | system; it is up to the author/donor to decide if he or she is willing 223 | to distribute software through any other system and a licensee cannot 224 | impose that choice. 225 | 226 | This section is intended to make thoroughly clear what is believed to 227 | be a consequence of the rest of this License. 228 | 229 | 8. If the distribution and/or use of the Program is restricted in 230 | certain countries either by patents or by copyrighted interfaces, the 231 | original copyright holder who places the Program under this License 232 | may add an explicit geographical distribution limitation excluding 233 | those countries, so that distribution is permitted only in or among 234 | countries not thus excluded. In such case, this License incorporates 235 | the limitation as if written in the body of this License. 236 | 237 | 9. The Free Software Foundation may publish revised and/or new versions 238 | of the General Public License from time to time. Such new versions will 239 | be similar in spirit to the present version, but may differ in detail to 240 | address new problems or concerns. 241 | 242 | Each version is given a distinguishing version number. If the Program 243 | specifies a version number of this License which applies to it and "any 244 | later version", you have the option of following the terms and conditions 245 | either of that version or of any later version published by the Free 246 | Software Foundation. If the Program does not specify a version number of 247 | this License, you may choose any version ever published by the Free Software 248 | Foundation. 249 | 250 | 10. If you wish to incorporate parts of the Program into other free 251 | programs whose distribution conditions are different, write to the author 252 | to ask for permission. For software which is copyrighted by the Free 253 | Software Foundation, write to the Free Software Foundation; we sometimes 254 | make exceptions for this. Our decision will be guided by the two goals 255 | of preserving the free status of all derivatives of our free software and 256 | of promoting the sharing and reuse of software generally. 257 | 258 | NO WARRANTY 259 | 260 | 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY 261 | FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN 262 | OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES 263 | PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED 264 | OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 265 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS 266 | TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE 267 | PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, 268 | REPAIR OR CORRECTION. 269 | 270 | 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 271 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR 272 | REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, 273 | INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING 274 | OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED 275 | TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY 276 | YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER 277 | PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE 278 | POSSIBILITY OF SUCH DAMAGES. 279 | 280 | END OF TERMS AND CONDITIONS 281 | 282 | How to Apply These Terms to Your New Programs 283 | 284 | If you develop a new program, and you want it to be of the greatest 285 | possible use to the public, the best way to achieve this is to make it 286 | free software which everyone can redistribute and change under these terms. 287 | 288 | To do so, attach the following notices to the program. It is safest 289 | to attach them to the start of each source file to most effectively 290 | convey the exclusion of warranty; and each file should have at least 291 | the "copyright" line and a pointer to where the full notice is found. 292 | 293 | 294 | Copyright (C) 295 | 296 | This program is free software; you can redistribute it and/or modify 297 | it under the terms of the GNU General Public License as published by 298 | the Free Software Foundation; either version 2 of the License, or 299 | (at your option) any later version. 300 | 301 | This program is distributed in the hope that it will be useful, 302 | but WITHOUT ANY WARRANTY; without even the implied warranty of 303 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 304 | GNU General Public License for more details. 305 | 306 | You should have received a copy of the GNU General Public License along 307 | with this program; if not, write to the Free Software Foundation, Inc., 308 | 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. 309 | 310 | Also add information on how to contact you by electronic and paper mail. 311 | 312 | If the program is interactive, make it output a short notice like this 313 | when it starts in an interactive mode: 314 | 315 | Gnomovision version 69, Copyright (C) year name of author 316 | Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 317 | This is free software, and you are welcome to redistribute it 318 | under certain conditions; type `show c' for details. 319 | 320 | The hypothetical commands `show w' and `show c' should show the appropriate 321 | parts of the General Public License. Of course, the commands you use may 322 | be called something other than `show w' and `show c'; they could even be 323 | mouse-clicks or menu items--whatever suits your program. 324 | 325 | You should also get your employer (if you work as a programmer) or your 326 | school, if any, to sign a "copyright disclaimer" for the program, if 327 | necessary. Here is a sample; alter the names: 328 | 329 | Yoyodyne, Inc., hereby disclaims all copyright interest in the program 330 | `Gnomovision' (which makes passes at compilers) written by James Hacker. 331 | 332 | , 1 April 1989 333 | Ty Coon, President of Vice 334 | 335 | This General Public License does not permit incorporating your program into 336 | proprietary programs. If your program is a subroutine library, you may 337 | consider it more useful to permit linking proprietary applications with the 338 | library. If this is what you want to do, use the GNU Lesser General 339 | Public License instead of this License. 340 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # awesome-decentralized-storage 2 | A curated list of proof of storage and decentralized storage resources and links. 3 | 4 | * Proof of Storage Schemes 5 | * Proof of Space Implementations 6 | * Decentralized Storage Platforms 7 | 8 | ## Proof of Storage Schemes 9 | 10 | * PDP/Proof of Data Possession 11 | * PoSE/Proof of Secure Erasure 12 | * PoRet/Proof of Retrievability 13 | * PoDR/Proof of Data Replication 14 | * PoSpace/Proof of Space 15 | * PoRep/Proof of Replication 16 | * PoSt/Proof of Spacetime 17 | 18 | ### **PDP** 19 | 20 | * \[1\] Giuseppe Ateniese, Randal Burns, Reza Curtmola, Joseph Herring, Lea Kissner, Zachary Peterson, and Dawn Song. 2007. [Provable data possession at untrusted stores](http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.478.5509&rep=rep1&type=pdf). In Proceedings of the 14th ACM conference on Computer and communications security \(CCS '07\). ACM, New York, NY, USA, 598-609 21 | 22 | * \[2\] Mehul A. Shah, Mary Baker, Jeffrey C. Mogul, and Ram Swaminathan. 2007. [Auditing to keep online storage services honest](http://static.usenix.org/legacy/events/hotos07/tech/full_papers/shah/shah.pdf). In Proceedings of the 11th USENIX workshop on Hot topics in operating systems \(HOTOS'07\), Galen Hunt \(Ed.\). USENIX Association, Berkeley, CA, USA, Article 11 , 6 pages 23 | 24 | * \[3\] Décio Luiz Gazzoni Filho and Paulo Sérgio Licciardi Messeder Barreto. 2006. [Demonstrating data possession and uncheatable data transfer](https://eprint.iacr.org/2006/150.pdf). Cryptology ePrint Archive, Report 2006/150 25 | 26 | * \[4\] Deswarte Y., Quisquater JJ., Saïdane A. \(2004\) [Remote Integrity Checking](https://pdfs.semanticscholar.org/897f/02111f5b954dd2fb2cb0f1eb77bd8c0374ad.pdf). In: Jajodia S., Strous L. \(eds\) Integrity and Internal Control in Information Systems VI. IICIS 2003. IFIP International Federation for Information Processing, vol 140. Springer, Boston, MA 27 | 28 | ### PoSE 29 | 30 | * \[1\] Karvelas N.P., Kiayias A. \(2014\) Efficient Proofs of Secure Erasure. In: Abdalla M., De Prisco R. \(eds\) Security and Cryptography for Networks. SCN 2014. Lecture Notes in Computer Science, vol 8642. Springer, Cham 31 | 32 | * \[2\] Perito D., Tsudik G. \(2010\) [Secure Code Update for Embedded Devices via Proofs of Secure Erasure](https://eprint.iacr.org/2010/217.pdf). In: Gritzalis D., Preneel B., Theoharidou M. \(eds\) Computer Security – ESORICS 2010. ESORICS 2010. Lecture Notes in Computer Science, vol 6345. Springer, Berlin, Heidelberg 33 | 34 | * \[3\] Karvelas, N. P. \(2013\). [Proofs of secure erasure](http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.675.56&rep=rep1&type=pdf). Athens, Greece: Masters thesis, University of Athens 35 | 36 | * \[4\] Harry Buhrman, Richard Cleve, Michal Koucký, Bruno Loff, and Florian Speelman. 2014. [Computing with a full memory: catalytic space](https://iuuk.mff.cuni.cz/~koucky/LBCAD/papers/catalytic.pdf). In Proceedings of the forty-sixth annual ACM symposium on Theory of computing \(STOC '14\). ACM, New York, NY, USA, 857-866 37 | 38 | ### **PoRet** 39 | 40 | * \[1\] Ari Juels and Burton S. Kaliski, Jr.. 2007. [Pors: proofs of retrievability for large files](http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.119.3294&rep=rep1&type=pdf). In Proceedings of the 14th ACM conference on Computer and communications security \(CCS '07\). ACM, New York, NY, USA, 584-597 41 | 42 | * \[2\] Kevin D. Bowers, Ari Juels, and Alina Oprea. 2009. [Proofs of retrievability: theory and implementation](http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.215.5388&rep=rep1&type=pdf). In Proceedings of the 2009 ACM workshop on Cloud computing security \(CCSW '09\). ACM, New York, NY, USA, 43-54 43 | 44 | * \[3\] Shacham H., Waters B. \(2008\) [Compact Proofs of Retrievability](http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.116.2133&rep=rep1&type=pdf). In: Pieprzyk J. \(eds\) Advances in Cryptology - ASIACRYPT 2008. ASIACRYPT 2008. Lecture Notes in Computer Science, vol 5350. Springer, Berlin, Heidelberg 45 | 46 | * \[4\] E. L. Miller and T. S. Schwarz. [Store, Forget, and Check: Using Algebraic Signatures to Check Remotely Administered Storage](https://www.researchgate.net/profile/Ethan_Miller/publication/224636589_Store_Forget_and_Check_Using_Algebraic_Signatures_to_Check_Remotely_Administered_Storage/links/55e737d308aeb6516262dcae.pdf). 26th IEEE International Conference on Distributed Computing Systems \(ICDCS'06\)\(ICDCS\), Lisboa, Portugal, 2006, pp. 12 \[[Slides](https://pdfs.semanticscholar.org/a440/925573bc4a2928439d4c34a1bf17d9e83b28.pdf)\] 47 | 48 | * \[5\] Ateniese G., Kamara S., Katz J. \(2009\) [Proofs of Storage from Homomorphic Identification Protocols](https://www.iacr.org/archive/asiacrypt2009/59120314/59120314.pdf). In: Matsui M. \(eds\) Advances in Cryptology – ASIACRYPT 2009. ASIACRYPT 2009. Lecture Notes in Computer Science, vol 5912. Springer, Berlin, Heidelberg \[[Slides](https://pdfs.semanticscholar.org/a440/925573bc4a2928439d4c34a1bf17d9e83b28.pdf)\] 49 | 50 | * \[6\] A. Miller, A. Juels, E. Shi, B. Parno and J. Katz. [Permacoin: Repurposing Bitcoin Work for Data Preservation](https://www.computer.org/csdl/proceedings/sp/2014/4686/00/4686a475.pdf). 2014 IEEE Symposium on Security and Privacy \(SP\), Berkeley, CA, USA, 2014, pp. 475-490 51 | 52 | * \[7\] Kopp H., Bösch C., Kargl F. \(2016\) [KopperCoin – A Distributed File Storage with Financial Incentives](https://www.gwern.net/docs/bitcoin/2016-kopp.pdf). In: Bao F., Chen L., Deng R., Wang G. \(eds\) Information Security Practice and Experience. ISPEC 2016. Lecture Notes in Computer Science, vol 10060. Springer, Cham 53 | 54 | ### PoDR 55 | 56 | * \[1\] Ivan Damgård and Chaya Ganesh and Claudio Orlandi. [Proofs of Replicated Storage Without Timing Assumptions](https://eprint.iacr.org/2018/654). Cryptology ePrint Archive, Report 2018/654 57 | 58 | * \[2\] R. Curtmola, R. Burns, G. Ateniese and O. Khan. [MR-PDP: Multiple-Replica Provable Data Possession](http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.646.7928&rep=rep1&type=pdf). 2008 28th IEEE International Conference on Distributed Computing Systems \(ICDCS\), Beijing, 2008, pp. 411-420 59 | 60 | * \[3\] Frederik Armknecht, Ludovic Barman, Jens-Matthias Bohli, and Ghassan O. Karame. [Mirror: Enabling proofs of data replication](https://www.usenix.org/system/files/conference/usenixsecurity16/sec16_paper_armknecht.pdf). In 25th USENIX Security Symposium, 2016 61 | 62 | ### PoSpace 63 | 64 | * \[1\] Dziembowski S., Faust S., Kolmogorov V., Pietrzak K. \(2015\) [Proofs of Space](http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.460.8936&rep=rep1&type=pdf). In: Gennaro R., Robshaw M. \(eds\) Advances in Cryptology -- CRYPTO 2015. CRYPTO 2015. Lecture Notes in Computer Science, vol 9216. Springer, Berlin, Heidelberg 65 | 66 | * \[2\] Ren L., Devadas S. \(2016\) [Proof of Space from Stacked Expanders](https://pdfs.semanticscholar.org/0c48/f0365c816d54cbebc47edbe71132d09b6436.pdf). In: Hirt M., Smith A. \(eds\) Theory of Cryptography. TCC 2016. Lecture Notes in Computer Science, vol 9985. Springer, Berlin, Heidelberg 67 | 68 | * \[3\] G. Ateniese, I. Bonacina, A. Faonio, and N. Galesi. [Proofs of space: When space is of the essence](https://eprint.iacr.org/2013/805.pdf). In Security and Cryptography for Networks \(SCN\), pages 538–557. Springer, 2014 69 | 70 | * \[4\] Georg Fuchsbauer. [SpaceMint: A Cryptocurrency Based on Proofs of Space](https://brage.bibsys.no/xmlui/bitstream/handle/11250/2461338/17937_FULLTEXT.pdf?sequence=1). ERCIM News 110, July 2017, Special theme: Blockchain Engineering. 2017, pp.13 71 | 72 | * \[5\] Vivek Bhupatiraju, John Kuszmaul, and Vinjai Vale. \[Slides\] [Exploring proof of space with hard-to-pebble graphs](https://math.mit.edu/research/highschool/primes/materials/2016/conf/10-2\ Bhupatiraju-Kuszmaul-Vale.pdf). 2016 73 | 74 | * \[6\] Abusalah H., Alwen J., Cohen B., Khilko D., Pietrzak K., Reyzin L. \(2017\) [Beyond Hellman’s Time-Memory Trade-Offs with Applications to Proofs of Space](https://pdfs.semanticscholar.org/18c0/84312e54533a65603d7e7d2aa652af940e24.pdf). In: Takagi T., Peyrin T. \(eds\) Advances in Cryptology – ASIACRYPT 2017. ASIACRYPT 2017. Lecture Notes in Computer Science, vol 10625. Springer, Cham \[[Slides](http://pub.ist.ac.at/~habusalah/files/function-inversion-pos_slides.pdf)\] 75 | 76 | ### PoRep 77 | 78 | * \[1\] Krzysztof Pietrzak. [Proofs of Catalytic Space](https://eprint.iacr.org/2018/194). Cryptology ePrint Archive, Report 2018/194 79 | 80 | * \[2\] Ben Fisch. [Tight Proofs of Space and Replication](https://eprint.iacr.org/2018/702.pdf). Cryptology ePrint Archive, Report 2018/702 81 | 82 | * \[3\] J. Benet, D. Dalrymple, and N. Greco. [Proof of replication](https://filecoin.io/proof-of-replication.pdf). Technical report, Protocol Labs, July 27, 2017 83 | 84 | * \[4\] B. Fisch, J. Bonneau, N. Greco, and J. Benet. [Scaling proof-of-replication for filecoin mining](https://web.stanford.edu/~bfisch/porep_short.pdf). Technical report, Stanford University, 2018 85 | 86 | * \[5\] Ben Fisch. [PoReps: Proofs of Space on Useful Data](https://eprint.iacr.org/2018/678). Cryptology ePrint Archive, Report 2018/678 87 | 88 | * \[6\] Ethan Cecchetti and Ben Fisch and Ian Miers and Ari Juels. [PIEs: Public Incompressible Encodings for Decentralized Storage](https://eprint.iacr.org/2018/684). Cryptology ePrint Archive, Report 2018/684 89 | 90 | * \[7\] Ben Fisch. \[Talk\] [Proof of Replication using Depth Robust Graphs](https://www.youtube.com/watch?v=8_9ONpyRZEI) - Ben Fisch BPASE '18, January 24-26th 2018, Stanford University Stanford Cyber Initiative \[[Slides](https://cyber.stanford.edu/sites/g/files/sbiybj9936/f/bpase_porep.pptx)\] 91 | 92 | ### PoSt 93 | 94 | * \[1\] Tal Moran and Ilan Orlov. [Rational Proofs of Space-Time](https://eprint.iacr.org/2016/035). Cryptology ePrint Archive, Report 2016/035 95 | 96 | ## Proof of Space Implementations 97 | 98 | * Burstcoin 99 | * Chia: Proof of Space and Time, VDF-based PoT 100 | * SpaceMint 101 | * SpaceMesh 102 | * Permacoin: only paper, no implementation 103 | * BitcoinOre: already dead 104 | 105 | ### Burstcoin 106 | 107 | * \[1\] Seán Gauld, Franz von Ancoina, Robert Stadler. [The Burst Dymaxion: An Arbitrary Scalable, Energy Efficient and Anonymous Transaction Network Based on Colored Tangles](https://dymaxion.burst.cryptoguru.org/The-Burst-Dymaxion-1.00.pdf) \(Whitepaper\) 108 | 109 | * \[2\] [Burstcoin Official Website](https://www.burst-coin.org/) 110 | 111 | * \[3\] [Butstwiki](https://burstwiki.org/wiki/Main_Page) 112 | 113 | * \[4\] [Technical information to create plot files](https://burstwiki.org/wiki/Technical_information_to_create_plot_files) - Burstwiki 114 | 115 | * \[5\] [Technical information about mining and block forging](https://burstwiki.org/wiki/Technical_information_about_mining_and_block_forging) - Burstwiki 116 | 117 | ### Chia 118 | 119 | * \[1\] [Chia Official Website](https://www.chia.net/) 120 | * \[2\] [Chia FAQ](https://www.chia.net/faq/) 121 | * \[3\] Bram Cohen, Chia Network. \[Talk\] [Stopping grinding attacks in proofs of space](https://www.youtube.com/watch?v=2Zlcgt8FVz4). Stanford Seminar, 2018 122 | * \[4\] Bram Cohen. \[Talk\] [Beyond Hellman’s Time-Memory Trade-Offs with Applications to Proofs of Space](https://www.youtube.com/watch?v=iqxkO7C-cyk&feature=youtu.be) - Bram Cohen BPASE '18, January 24-26th 2018, Stanford University Stanford Cyber Initiative 123 | * \[5\] Ben Fisch. \[Talk\] [Verifiable Delay Functions: Applications and Candidate Constructions](https://www.youtube.com/watch?v=qUoagL7OZ1k&feature=youtu.be) - Ben Fisch BPASE '18, January 24-26th 2018, Stanford University Stanford Cyber Initiative 124 | * \[6\] Bram Cohen. \[Talk\] [Proofs of Space and Time with Bram Cohen](https://www.facebook.com/BlockchainatBerkeley/videos/2006069823011271/) - with a lightning talk from Mark Nadal, 2018 \[[Slides](//view.publitas.com/chia-network/chia-1/page/1)\] 125 | * \[7\] Bram Cohen. \[Talk\] [Combining Proofs of Space and Proofs of Time](https://www.youtube.com/watch?v=aYG0NxoG7yw) - Bram Cohen \(Bittorrent, Inc\) BPASE '17, January 27th 2017, Stanford University Stanford Cyber Initiative \[[Slides](https://cyber.stanford.edu/sites/g/files/sbiybj9936/f/bramcohen.pdf)\] 126 | * \[8\] Bram Cohen. SF Bitcoin Devs Seminar: [Removing the Waste from Cryptocurrencies: Challenges and More Challenges](https://www.youtube.com/watch?v=zZaB4hM8SQ4). 2015 \[[Slides](https://view.publitas.com/chia-network/bitcoin_data_structures/page/1)\] \[[Code](https://github.com/bramcohen/MerkleSet)\] 127 | * \[9\] Krzysztof Pietrzak. [Simple Verifiable Delay Functions](http://drops.dagstuhl.de/opus/volltexte/2018/10153/pdf/LIPIcs-ITCS-2019-60.pdf). 10th Innovations in Theoretical Computer Science Conference \(ITCS 2019\), 60:1-15. Cryptology ePrint Archive, [Report 2018/627](https://eprint.iacr.org/2018/627) 128 | * \[10\] Cohen B., Pietrzak K. \(2018\) [Simple Proofs of Sequential Work](https://eprint.iacr.org/2018/183). In: Nielsen J., Rijmen V. \(eds\) Advances in Cryptology – EUROCRYPT 2018. EUROCRYPT 2018. Lecture Notes in Computer Science, vol 10821. Springer, Cham. Cryptology ePrint Archive, Report 2018/183 129 | * \[11\] Buchmann and Vollmer. [Binary quadratic forms](https://github.com/Chia-Network/vdf-competition/blob/master/classgroups.pdf). 2017 130 | * \[12\] Dan Boneh, Benedikt B¨unz, Ben Fisch. [A Survey of Two Verifiable Delay Functions](https://eprint.iacr.org/2018/712.pdf). Cryptology ePrint Archive, Report 2018/712 131 | * [CP19] [Bram Cohen and Krzysztof Pietrazak. The Chia Network Blockchain](https://www.chia.net/assets/ChiaGreenPaper.pdf). July 9, 2019 (Green Paper) 132 | * [Chia Proof of Space Construction](https://www.chia.net/assets/proof_of_space.pdf). 2019 133 | 134 | ### SpaceMint 135 | 136 | * \[1\] Georg Fuchsbauer. [SpaceMint: A Cryptocurrency Based on Proofs of Space](https://brage.bibsys.no/xmlui/bitstream/handle/11250/2461338/17937_FULLTEXT.pdf?sequence=1). ERCIM News 110, July 2017, Special theme: Blockchain Engineering. 2017, pp.13 \(PoSpace-04\) 137 | 138 | * \[2\] Trond Hønsi.[ SpaceMint: A Cryptocurrency Based on Proofs of Space](https://brage.bibsys.no/xmlui/bitstream/handle/11250/2461338/17937_FULLTEXT.pdf?sequence=1). Norwegian University of Science and Technology \(NTNU\): Master thesis, 2017 139 | 140 | ### SpaceMesh 141 | 142 | * \[1\] [SpaceMesh Official Website](https://spacemesh.io/) 143 | 144 | * \[2\] [Spacemesh: A fair, secure, decentralized and scalable cryptocurrency and a smart contracts computer](https://spacemesh.io/assets/built/whitepaper1.2.pdf) \(Whitepaper\) 145 | 146 | * \[3\] Github [spacemeshos/go-spacemesh](https://github.com/spacemeshos/go-spacemesh) 147 | 148 | ### Permacoin 149 | 150 | * \[1\] A. Miller, A. Juels, E. Shi, B. Parno and J. Katz. [Permacoin: Repurposing Bitcoin Work for Data Preservation](https://www.computer.org/csdl/proceedings/sp/2014/4686/00/4686a475.pdf). 2014 IEEE Symposium on Security and Privacy \(SP\), Berkeley, CA, USA, 2014, pp. 475-490 \(PoRet-06\) 151 | 152 | ### BitcoinOre 153 | 154 | * \[1\] [Bitcoin Ore \(BCO\) : A brand new PoC mining ecosystem for all](https://holybao.com/ipfs/QmaS7Ss9We7MVLv5g52qKzGfcmtMwSUFqk3NN57s5oYBHY). 2017 155 | 156 | ## Decentralized Storage Platforms 157 | 158 | * Sia 159 | * Storj 160 | * IPFS 161 | * Filecoin 162 | * Swarm 163 | * KopperCoin: only paper, no implementation 164 | * Retricoin: only paper, no implementation 165 | 166 | ### Sia 167 | 168 | * \[1\] [Sia Official Website](https://www.sia.tech/) 169 | 170 | * \[2\] [Sia Technology](https://sia.tech/technology) 171 | 172 | * \[3\] D. Vorick, L. Champine. [Sia: Simple Decentralized Storage](https://cryptorating.eu/whitepapers/Sia/sia.pdf). 2014 \(Whitepaper\) 173 | 174 | ### Storj 175 | 176 | * \[1\] [Storj Official Website](https://storj.io/) 177 | 178 | * \[2\] Storj Labs, Inc. [Storj: A Decentralized Cloud Storage Network Framework](https://storj.io/storjv3.pdf). 2018 \(Whitepaper 3.0\) 179 | 180 | * \[3\] Shawn Wilkinson, Tome Boshevski and etc.. [Storj: A Peer-to-Peer Cloud Storage Network](https://storj.io/storjv2.pdf). 2016 \(Whitepaper 2.0\) 181 | 182 | * \[4\] Tome Boshevski, Josh Brandof and Vitalik Buterin. [Storj: A Peer-to-Peer Cloud Storage Network](https://storj.io/storj2014.pdf). 2014 \(Whitepaper 1.0\) 183 | 184 | * \[5\] Shawn Wilkinson, Jim Lowry. [Metadisk: Blockchain-Based Decentralized File Storage Application](https://storj.io/metadisk.pdf). 2014 185 | 186 | ### IPFS 187 | 188 | * \[1\] [IPFS Official Website](https://ipfs.io/) 189 | 190 | * \[2\] [IPFS Documentation](https://docs.ipfs.io/) 191 | 192 | * \[3\] Juan Benet. [IPFS - Content Addressed, Versioned, P2P File System](https://arxiv.org/pdf/1407.3561v1.pdf). [arXiv:1407.3561](https://arxiv.org/abs/1407.3561) \[cs.NI\], 2014 193 | 194 | * \[4\] Maymounkov P., Mazières D. \(2002\) [Kademlia: A Peer-to-Peer Information System Based on the XOR Metric](http://www8.cs.umu.se/kurser/5DV153/HT14/literature/maymounkov2002kademlia.pdf). In: Druschel P., Kaashoek F., Rowstron A. \(eds\) Peer-to-Peer Systems. IPTPS 2002. Lecture Notes in Computer Science, vol 2429. Springer, Berlin, Heidelberg 195 | 196 | * \[5\] S. Mies and I. Baumgart. [S/Kademlia: A practicable approach towards secure key-based routing](http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.68.4986&rep=rep1&type=pdf). Parallel and Distributed Systems, International Conference on\(ICPADS\), Hsinchu, Taiwan, 2007, pp. 1-8 197 | 198 | * \[6\] Juan Benet of Protocol Labs. \[Talk\] Stanford Seminar - [IPFS and the Permanent Web](https://www.youtube.com/watch?v=HUVmypx9HGI). 2015 199 | 200 | ### Filecoin 201 | 202 | * \[1\] [Filecoin Official Website](https://filecoin.io/) 203 | 204 | * \[2\] [Filecoin FAQs](https://filecoin.io/faqs/) 205 | 206 | * \[3\] Protocol Labs, Inc. [Filecoin Primer](https://ipfs.io/ipfs/QmWimYyZHzChb35EYojGduWHBdhf9SD5NHqf8MjZ4n3Qrr/Filecoin-Primer.7-25.pdf). 2017 207 | 208 | * \[4\] Protocol Labs. [Filecoin: A Decentralized Storage Network](https://filecoin.io/filecoin.pdf). 2017 \(Whitepaper\) 209 | 210 | * \[5\] Filecoin.io. [Filecoin: A Cryptocurrency Operated File Storage Network](https://filecoin.io/filecoin-jul-2014.pdf). 2014 \(Original Whitepaper\) 211 | 212 | * \[6\] Protocol Labs. [Power Fault Tolerance](https://filecoin.io/power-fault-tolerance.pdf) Technical Report \(WIP\). 2017 213 | 214 | * \[7\] Juan Benet of Protocol Labs. [Filecoin Research Roadmap for 2017 ](https://filecoin.io/research-roadmap-2017.pdf) 215 | 216 | * \[8\] Ben Fisch. [Tight Proofs of Space and Replication](https://eprint.iacr.org/2018/702.pdf). Cryptology ePrint Archive, Report 2018/702 \(PoRep-02\) 217 | 218 | * \[9\] J. Benet, D. Dalrymple, and N. Greco. [Proof of replication](https://filecoin.io/proof-of-replication.pdf). Technical report, Protocol Labs, July 27, 2017 \(PoRep-03\) 219 | 220 | * \[10\] B. Fisch, J. Bonneau, N. Greco, and J. Benet. [Scaling proof-of-replication for filecoin mining](/Scaling proof-of-replication for filecoin mining). Technical report, Stanford University, 2018 \(PoRep-04\) 221 | 222 | * \[11\] Ben Fisch. [PoReps: Proofs of Space on Useful Data](https://eprint.iacr.org/2018/678). Cryptology ePrint Archive, Report 2018/678 \(PoRep-05\) 223 | 224 | * \[12\] Juan Benet. \[Talk\] [Filecoin: protocol overview, the important results, and new open problems](https://www.youtube.com/watch?v=vyRZBeMtkrA) - Juan Benet BPASE '18, January 24-26th 2018, Stanford University Stanford Cyber Initiative \[[Slides](https://cyber.stanford.edu/sites/g/files/sbiybj9936/f/filecoin.bpase-2018.compressed.pdf)\] 225 | 226 | * \[13\] Juan Benet of Protocol Labs. \[Talk\] [FILECOIN & THE RISE OF OPEN SERVICES](https://www.youtube.com/watch?v=IfLIoOr4p0A). 2018 227 | 228 | * \[14\] Juan Benet of Filecoin, Protocol Labs and IPFS: \[Talk\] "[Filecoin](https://www.youtube.com/watch?v=6h2WNxEV8q4)" \| Blockstack Berlin 2018 229 | 230 | * \[15\] [Filecoin Project Roadmap](https://docs.google.com/document/d/1cgss-rifFO2iSJgnMmOsD_tPal40MUp1m7crTFQuVYQ/edit) \(2018 Q2\) - Google Docs 231 | 232 | * \[16\] [Filecoin 2018 Q1 & Q2 Update](https://filecoin.io/blog/update-2018-q1-q2/) 233 | 234 | * \[17\] [Filecoin 2018 Q3 & Q4 Update](https://filecoin.io/blog/update-2018-q3-q4/) 235 | 236 | * \[18\] [Opening the Filecoin Project Repos](https://filecoin.io/blog/opening-filecoin-project-repos/) 237 | 238 | * \[19\] Github [filecoin-project/go-filecoin](https://github.com/filecoin-project/go-filecoin): the first implementation of the Filecoin Protocol 239 | 240 | * \[20\] Github [filecoin-project/specs](https://github.com/filecoin-project/specs): the specification of the Filecoin Protocol 241 | 242 | * \[21\] Github [filecoin-project/rust-fil-proofs](https://github.com/filecoin-project/rust-fil-proofs): proof-of-replication and other crypto components 243 | 244 | * \[22\] Github [filecoin-project/replication-game](https://github.com/filecoin-project/replication-game): proof-of-replication optimization competition 245 | 246 | * \[23\] Github [filecoin-project/research](https://github.com/filecoin-project/research): open problems, ideas, and discussions 247 | 248 | ### Swarm 249 | 250 | * \[1\] [Swarm Official Website](https://swarm-gateways.net/bzz:/theswarm.eth/) 251 | 252 | * \[2\] [Swarm Documentation](https://swarm-guide.readthedocs.io/) 253 | 254 | * \[3\] [Swarm Resources](https://swarm-guide.readthedocs.io/en/latest/resources.html) 255 | 256 | * \[4\] Viktor Trón, Aron Fischer, Dániel A. Nagy, Zsolt Felföldi, Nick Johnson. [swap, swear and swindle incentive system for swarm](https://swarm-gateways.net/bzz:/theswarm.eth/ethersphere/orange-papers/1/sw^3.pdf) \(Orange Paper 1/sw^3\), 2016 257 | 258 | * \[5\] Viktor Trón, Aron Fischer, Nick Johnson. [smash-proof: auditable storage for swarm secured by masked audit secret hash](https://swarm-gateways.net/bzz:/theswarm.eth/ethersphere/orange-papers/2/smash.pdf) \(Orange Paper 2/smash\), 2016 259 | 260 | * \[6\] Viktor Trón, Aron Fischer. [Generalized swam swear and swindle games](https://www.overleaf.com/read/yszmsdqyqbvc) \(Swap-swear-swindle Orange Paper/sw3paper\), Work In Progress, 2019 261 | 262 | * \[7\] Viktor Trón, Aron Fischer, Daniel A. Nag. [Swarm: a decentralised peer-to-peer network for messaging and](https://www.overleaf.com/read/gxhwssqzgfpr) [storage](https://www.overleaf.com/read/gxhwssqzgfpr) \(Orange Network Paper\), Work In Progress, 2019 263 | 264 | * \[8\] P.O.T. Data structure for decentralised database services on Swarm \(Orange Paper X\), In Preparation 265 | 266 | * \[9\] Mutable Resource Updates. An off-chain scheme for versioning content in Swarm \(Orange Paper X\). In Preparation 267 | 268 | * \[10\] Privacy on swarm. Encryption, access control, private browsing in Swarm \(Orange Paper X\). Tentative 269 | 270 | * \[11\] Analysis of attack resilience of swarm storage \(Orange Paper X\). Tentative 271 | 272 | * \[12\] [Swarm working groups](https://github.com/ethersphere/swarm/wiki/Working-groups/) 273 | 274 | * \[13\] Viktor Tron.\[Talk\] [Base layer infrastructure services for web3](https://www.youtube.com/watch?v=JgOU9MdgTGM#t=31m00s) - EthCC, Paris, March 2018 275 | 276 | * \[14\] Daniel A Nagy. \[Talk\] [Encryption in Swarm](https://www.youtube.com/watch?v=ZW7E8KTplgg) - EthCC, Paris, March 2018 277 | 278 | * \[15\] Louis Holbrook. \[Talk\] [Resource Updates](https://www.youtube.com/watch?v=CgvRFsezTI4&feature=player_embedded) - EthCC, Paris, March 2018 279 | 280 | * \[16\] Viktor Trón and Aron Fischer. \[Talk\] [Swap, Swear and Swindle Games](https://www.youtube.com/watch?v=9Cgyhsjsfbg) - Devcon3 Cancun, November 2017 281 | 282 | * \[17\] Viktor Tron. \[Talk\] [SWARM](https://www.youtube.com/watch?v=Bn65-bI-S1o) - Ethereum London, Octerber 2017 283 | 284 | ### KopperCoin 285 | 286 | * \[1\] Kopp H., Bösch C., Kargl F. \(2016\) [KopperCoin – A Distributed File Storage with Financial Incentives](https://www.gwern.net/docs/bitcoin/2016-kopp.pdf). In: Bao F., Chen L., Deng R., Wang G. \(eds\) Information Security Practice and Experience. ISPEC 2016. Lecture Notes in Computer Science, vol 10060. Springer, Cham \(PoRet-07\) 287 | 288 | ### Retricoin 289 | 290 | * \[1\] Binanda Sengupta, Samiran Bag, Sushmita Ruj, and Kouichi Sakurai. 2016. [Retricoin: Bitcoin based on compact proofs of retrievability](https://www.isical.ac.in/~binanda_r/publications/ICDCN2016.pdf). In Proceedings of the 17th International Conference on Distributed Computing and Networking \(ICDCN '16\). ACM, New York, NY, USA, Article 14, 10 pages 291 | 292 | 293 | 294 | 295 | 296 | --------------------------------------------------------------------------------