Assignments in this course will consist of research paper reading and presentations, reviews of presented papers, a course project, and one finals assignment. The course project can take the form of implementing an existing technique, using or extending an existing tool relevant to the scope of the source, designing a new technique or application (must properly demonstrate security-related properties), or perform a literature review. Each project can be done individually or in teams of two (non-survey projects only).
All students are expected to participate in class discussions and perform all assignments regardless of the number of credit hours they are registered for.
Your instructor will treat you as a professional, and you should plan on conducting yourself in an appropriate way. No behavior that compromises academic honesty (such as use of someone else's work or code, using prohibited materials during tests, or making your work available to others) will be tolerated in this course. If you need assistance with anything, do not hesitate to contact the instructor.
It is expected that your work represents your own understanding of the problem. If work of others is used, it must be properly cited. Use of properly cited material is acceptable, but no referencing is treated as claiming the work as your own.
Academic dishonesty will not be tolerated in this course. It is the CSE policy that each case of academic integrity violation is recorded. The standing policy of the department is that all students involved in an academic integrity violation will receive an F grade for the course, unless the instructor recommends a lesser penalty for the first instance of academic integrity violation for the student in question.
Information about the CSE policies can be found here; UB academic integrity policies are available here; and UB graduate school guidelines can be found here.
|Week 1: February 1||
|Week 2: February 8||Bitcoin and blockchain description:|
|Week 3: February 15||Anonymity in bitcoin:|
|Week 4: February 22||Security analysis of bitcoin:|
|Week 5: March 1||Anonymous cryptocurrencies:|
|Week 6: March 8||More recent analysis of cryptocurrencies:|
|Week 7: March 15||Smart contracts:|
|Week 8: March 22||Spring break|
|Week 9: March 29||Privacy-preserving smart contracts:|
|Week 10: April 5||Abuse of smart contracts:|
|Week 11: April 12||Resistance to specialized hardware for mining:
|Week 12: April 19||Alternatives to Proof-of-Work:
|Week 13: April 26||Non-outsourceable PoW and alternatives to PoW:
|Week 14: May 3||Other issues (smart contract errors and selfish mining):
|Week 15: May 10||Project presentations|