Blocktree/doc/citations.bib

@article{filecoin,
    author = "Protocol Labs",
    title = "Filecoin: A Decentralized Storage Network",
    url = {https://filecoin.io/filecoin.pdf}
}

@inproceedings{blockstack,
    author = {Muneeb Ali and Jude Nelson and Ryan Shea and Michael J. Freedman},
    title = {Blockstack: A Global Naming and Storage System Secured by Blockchains},
    booktitle = {2016 USENIX Annual Technical Conference (USENIX ATC 16)},
    year = {2016},
    isbn = {978-1-931971-30-0},
    address = {Denver, CO},
    pages = {181--194},
    url = {https://www.usenix.org/conference/atc16/technical-sessions/presentation/ali},
    publisher = {USENIX Association},
    month = jun,
}

@misc{tahoe,
    author = {Zooko Wilcox-O'Hearn and Brian Warner},
    title = {Tahoe – The Least-Authority Filesystem},
    howpublished = {Cryptology ePrint Archive, Paper 2012/524},
    year = {2012},
    note = {\url{https://eprint.iacr.org/2012/524}},
    url = {https://eprint.iacr.org/2012/524}
}

@misc{tpm,
    title = {TPM 2.0 Library},
    url = {https://trustedcomputinggroup.org/resource/tpm-library-specification/}
}

@inproceedings {raft,
    author = {Diego Ongaro and John Ousterhout},
    title = {In Search of an Understandable Consensus Algorithm},
    booktitle = {2014 USENIX Annual Technical Conference (USENIX ATC 14)},
    year = {2014},
    isbn = {978-1-931971-10-2},
    address = {Philadelphia, PA},
    pages = {305--319},
    url = {https://www.usenix.org/conference/atc14/technical-sessions/presentation/ongaro},
    publisher = {USENIX Association},
    month = jun,
}

@article{bitcoin,
    author = {Nakamoto, Satoshi},
    year = {2009},
    month = {03},
    pages = {},
    title = {Bitcoin: A Peer-to-Peer Electronic Cash System},
    journal = {Cryptography Mailing list at https://metzdowd.com},
    url = {https://bitcoin.org/bitcoin.pdf}
}

@misc{raptorq,
    series =	{Request for Comments},
    number =	6330,
    howpublished =	{RFC 6330},
    publisher =	{RFC Editor},
    doi =		{10.17487/RFC6330},
    url =		{https://www.rfc-editor.org/info/rfc6330},
        author =	{Lorenz Minder and Amin Shokrollahi and Mark Watson and Mike Luby and Thomas Stockhammer},
    title =		{{RaptorQ Forward Error Correction Scheme for Object Delivery}},
    pagetotal =	69,
    year =		2011,
    month =		aug,
    abstract =	{This document describes a Fully-Specified Forward Error Correction (FEC) scheme, corresponding to FEC Encoding ID 6, for the RaptorQ FEC code and its application to reliable delivery of data objects. RaptorQ codes are a new family of codes that provide superior flexibility, support for larger source block sizes, and better coding efficiency than Raptor codes in RFC 5053. RaptorQ is also a fountain code, i.e., as many encoding symbols as needed can be generated on the fly by the encoder from the source symbols of a source block of data. The decoder is able to recover the source block from almost any set of encoding symbols of sufficient cardinality -- in most cases, a set of cardinality equal to the number of source symbols is sufficient; in rare cases, a set of cardinality slightly more than the number of source symbols is required. The RaptorQ code described here is a systematic code, meaning that all the source symbols are among the encoding symbols that can be generated. {[}STANDARDS-TRACK{]}},
}

@inproceedings{10.1145/3062341.3062363,
author = {Haas, Andreas and Rossberg, Andreas and Schuff, Derek L. and Titzer, Ben L. and Holman, Michael and Gohman, Dan and Wagner, Luke and Zakai, Alon and Bastien, JF},
title = {Bringing the Web up to Speed with WebAssembly},
year = {2017},
isbn = {9781450349888},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/3062341.3062363},
doi = {10.1145/3062341.3062363},
abstract = { The maturation of the Web platform has given rise to sophisticated and demanding Web applications such as interactive 3D visualization, audio and video software, and games. With that, efficiency and security of code on the Web has become more important than ever. Yet JavaScript as the only built-in language of the Web is not well-equipped to meet these requirements, especially as a compilation target.  Engineers from the four major browser vendors have risen to the challenge and collaboratively designed a portable low-level bytecode called WebAssembly. It offers compact representation, efficient validation and compilation, and safe low to no-overhead execution. Rather than committing to a specific programming model, WebAssembly is an abstraction over modern hardware, making it language-, hardware-, and platform-independent, with use cases beyond just the Web. WebAssembly has been designed with a formal semantics from the start. We describe the motivation, design and formal semantics of WebAssembly and provide some preliminary experience with implementations. },
booktitle = {Proceedings of the 38th ACM SIGPLAN Conference on Programming Language Design and Implementation},
pages = {185–200},
numpages = {16},
keywords = {just-in-time compilers, type systems, assembly languages, programming languages, virtual machines},
location = {Barcelona, Spain},
series = {PLDI 2017}
}

@article{wasm,
    author = {Haas, Andreas and Rossberg, Andreas and Schuff, Derek L. and Titzer, Ben L. and Holman, Michael and Gohman, Dan and Wagner, Luke and Zakai, Alon and Bastien, JF},
    title = {Bringing the Web up to Speed with WebAssembly},
    year = {2017},
    issue_date = {June 2017},
    publisher = {Association for Computing Machinery},
    address = {New York, NY, USA},
    volume = {52},
    number = {6},
    issn = {0362-1340},
    url = {https://doi.org/10.1145/3140587.3062363},
    doi = {10.1145/3140587.3062363},
    abstract = { The maturation of the Web platform has given rise to sophisticated and demanding Web applications such as interactive 3D visualization, audio and video software, and games. With that, efficiency and security of code on the Web has become more important than ever. Yet JavaScript as the only built-in language of the Web is not well-equipped to meet these requirements, especially as a compilation target.  Engineers from the four major browser vendors have risen to the challenge and collaboratively designed a portable low-level bytecode called WebAssembly. It offers compact representation, efficient validation and compilation, and safe low to no-overhead execution. Rather than committing to a specific programming model, WebAssembly is an abstraction over modern hardware, making it language-, hardware-, and platform-independent, with use cases beyond just the Web. WebAssembly has been designed with a formal semantics from the start. We describe the motivation, design and formal semantics of WebAssembly and provide some preliminary experience with implementations. },
    journal = {SIGPLAN Not.},
    month = {6},
    pages = {185–200},
    numpages = {16},
    keywords = {assembly languages, type systems, virtual machines, just-in-time compilers, programming languages}
}

@phdthesis{armstrong,
    author    = {Joe Armstrong},
    title     = {Making reliable distributed systems in the presence of software errors},
    school    = {Royal Institute of Technology, Stockholm, Sweden},
    year      = {2003}
}

@techreport{orleans,
    author = {Bernstein, Phil and Bykov, Sergey and Geller, Alan and Kliot, Gabriel and Thelin, Jorgen},
    title = {Orleans: Distributed Virtual Actors for Programmability and Scalability},
    year = {2014},
    month = {3},
    abstract = {High-scale interactive services demand high throughput with low latency and high availability, difficult goals to meet with the traditional stateless 3-tier architecture. The actor model makes it natural to build a stateful middle tier and achieve the required performance. However, the popular actor model platforms still pass many distributed systems problems to the developers.
    The Orleans programming model introduces the novel abstraction of virtual actors that solves a number of the complex distributed systems problems, such as reliability and distributed resource management, liberating the developers from dealing with those concerns. At the same time, the Orleans runtime enables applications to attain high performance, reliability and scalability.
    This paper presents the design principles behind Orleans and demonstrates how Orleans achieves a simple programming model that meets these goals. We describe how Orleans simplified the development of several scalable production applications on Windows Azure, and report on the performance of those production systems.},
    url = {https://www.microsoft.com/en-us/research/publication/orleans-distributed-virtual-actors-for-programmability-and-scalability/},
    number = {MSR-TR-2014-41},
}

@inproceedings{sfs,
    author = {Mazi\`{e}res, David and Kaashoek, M. Frans},
    title = {Escaping the Evils of Centralized Control with Self-Certifying Pathnames},
    year = {1998},
    isbn = {9781450373173},
    publisher = {Association for Computing Machinery},
    address = {New York, NY, USA},
    url = {https://doi.org/10.1145/319195.319213},
    doi = {10.1145/319195.319213},
    booktitle = {Proceedings of the 8th ACM SIGOPS European Workshop on Support for Composing Distributed Applications},
    pages = {118–125},
    numpages = {8},
    location = {Sintra, Portugal},
    series = {EW 8}
}

@inproceedings{quic,
    title	= {The QUIC Transport Protocol: Design and Internet-Scale Deployment},
    author	= {Adam Langley and Al Riddoch and Alyssa Wilk and Antonio Vicente and Charles 'Buck' Krasic and Cherie Shi and Dan Zhang and Fan Yang and Feodor Kouranov and Ian Swett and Janardhan Iyengar and Jeff Bailey and Jeremy Christopher Dorfman and Jim Roskind and Joanna Kulik and Patrik Göran Westin and Raman Tenneti and Robbie Shade and Ryan Hamilton and Victor Vasiliev and Wan-Teh Chang},
    year	= {2017}
}