|2||Jan 17th||-||What is a blockchain and how does it work? Distributed consensus.||Discussion topics : What is blockchain? Discuss origins, core concepts of distributed consensus, and compare/contrast traditional ways of accounting or recording information with the blockchain. Decentralized vs. centralized.||
|3||Jan 24th||-||Cryptographic basics: Hash functions and Public Key Cryptography.||What is a hash function? Why is the blockchain "secure"? Public keys as identities. Talk and questions with Ben Jun (Co-founder of Cryptography Research, Advisory Board @ RSA, and current CEO of HVF).||
|4||Jan 31st||-||Smart Contracts and Decentralized Applications.||Introduce concepts of smart contracts. Public vs. private blockchains. Applications to Ethereum and developing in Solidity.||
|5||Feb 7th||-||Architectural weaknesses of current protocols. Proof of stake and zero-knowledge proofs/protocols.||Scaling, energy utilisation, 51% attacks, growing length of blockchains, incentive misalignments (e.g. in Ripple), hard forks. Problems with Proof-of-work; Alternative mechanisms such as Proof-of-Stake; The ability of zero-knowledge proofs to ensure security and privacy (examples: Zcash and Ethereum).||
|6||Feb 14th||-||Implications: Secure distributed storage and compute.||Use of blockchains and distributed trust to safely store massive amounts of information in peer-peer networks (examples: FileCoin). The IPFS (InterPlanetary File System) hypermedia distribution protocol (addressed by content and identities); bittorrent swarms.||
|7||Feb 21st||-||Implications: Healthcare and MedRec/MedChain.||Talk and questions with Asaph Azaria (PhD from MIT Media Lab, started MedRec). How can blockchain help create a more secure and efficient system to store and transfer medical records/research data? Current limitations on medical records.||
|8||Feb 28th||-||Implications: Micropayments and the unbanked.||Micropayment applications to the Energy sector. Current limitations of transaction fees. Segwit/Lightning as a potential two-layer approach to micropayments on top of Bitcoin.||
|9||Mar 7th||-||Implications: Sharing personal data for discovery.||Privacy and third-party access to personal data. MIT Media Lab's Project Enigma.||
|10||Mar 14th||-||Implications: Intelligent currencies.||Cryptocurrencies and the dynamics of the crypto market as a whole. What's next? Talk and questions with Bradley Miles (Founder of Turing Advisory).||
|11||TBD||-||Project/Final Presentations||More info on this later.||-|
Richard Chen (rchen8 (at) stanford (dot) edu)
Renee Li (reneeli (at) stanford (dot) edu)
Raymond Thai (raythai (at) stanford (dot) edu)
Nancy Xu (xnancy (at) stanford (dot) edu)
(Lots of guest speakers)
Wed 5:30-6:20 Shriram 052 (except for 2/7, which will be in Shriram 102)
Talk to us during class or email firstname.lastname@example.org to make an appointment.
We use the mailing list generated by Axess to convey messages to the class. We will assume that all students read these messages.
(From the Office of Community Standards): The Honor Code is the university's statement on academic integrity written by students in 1921. It articulates university expectations of students and faculty in establishing and maintaining the highest standards in academic work. The Honor Code is an undertaking of the students, individually and collectively: that they will not give or receive aid in examinations; that they will not give or receive unpermitted aid in class work, in the preparation of reports, or in any other work that is to be used by the instructor as the basis of grading; that they will do their share and take an active part in seeing to it that others as well as themselves uphold the spirit and letter of the Honor Code. The faculty on its part manifests its confidence in the honor of its students by refraining from proctoring examinations and from taking unusual and unreasonable precautions to prevent the forms of dishonesty mentioned above. The faculty will also avoid, as far as practicable, academic procedures that create temptations to violate the Honor Code. While the faculty alone has the right and obligation to set academic requirements, the students and faculty will work together to establish optimal conditions for honorable academic work.
In this class, we will bring together experts in cryptography, healthcare, and distributed consensus with students across the university. The first weeks present a technical overview of blockchain primitives. In the following weeks, the class will focus on discussing applications and policy issues through lectures and guest speakers from various domains across both academia and industry.
Attendance will be taken at the start of each class, and will be mandatory. You have one free absence for the quarter (email the course staff if there are extenuating circumstances).
1. Student teams form and work together to create a youtube lecture/how-to that is related to a class topic and explains a technical aspect to a layman. For example, a youtube lecture/how-to could describe how zero knowledge proofs work, and why they might be relevant to biomedical research, medical diagnostics, and banking.
2. Student teams form to create a 4 part blog post related to an aspect of the course. For example, the blog post could cover incentive alignments (or misalignments) in the various protocols, or specific applications (e.g. electronic medical records on the blockchain), or cryptographic primitives.
3. A team or individual implementation project of their choice (we can provide ideas/guidance). For example, a student team could try to design a protocol that replaces the standard proof of work functions (e.g. SHA-256 hashing) with more useful calculations.