The University of Chicago
Department of Computer Science

MPCS 56600 Course Syllabus

Introduction to Blockchain

Summer 2018

Instructor:        Mark Shacklette
Office:               Young 208B
Office Hours:    Thursdays 3:30 PM - 5:30 PM and by Appt.

email:    mark@cs.uchicago.edu (read hourly or so)
              mshack@post.harvard.edu (read hourly or so)

Teaching staff: 

Lead TA:          Paul Bossi
Focus:               Class Operations and Lead TA
Office Hours:   T.B.D.
email:     T.B.D.

TA:            John Hadidian-Baugher
Focus:        Networking, Docker, Team Organization & Facilitation
Office Hours:    T.B.D.
email:     T.B.D.

TA:            Terry Lynch
Focus:        Algorithms & Math
Office Hours:    T.B.D.
email:     T.B.D.

SUBJECT	COURSE	TITLE	TIME	BUILDING
324	56600	Introduction to Blockchain:  Concepts, Technologies, Implementations	Thursday, 5:30pm	Ryerson 276

Texts: Required

Bitcoin and Cryptocurrency Technologies: A Comprehensive Introduction, Narayanan, et. al. Princeton, 2016.  ISBN: 978-0691171692

Mastering Bitcoin:  Programming the Open Blockchain, 2nd ed., Antonopoulos, O'Reilly, 2017.  ISBN:  978-1491954386

Texts: Highly Recommended

Docker Cookbook, Miell & Sayers, Manning, 2016, ISBN: 9781491919712

Docker in Practice, Sebastien Goasguen, O'Reilly, 2016, ISBN: 9781617292729

Recommended Reading

II. PREREQUISITE:

All students in this course are required to have passed core programming.  No exceptions.

Additionally, the following courses are suggested prerequisites for taking this course.  Those with this or equivalent background will find this course easier going:

Mathematics for Computer Science: Discrete Mathematics (MPCS 50103 or equivalent)
Algorithms (MPCS 55001 or equivalent)
Networks (MPCS 54001 or equivalent)

Solid comfort with one (or more) of the following programming languages:  Java (Javascript), C/C++, Python, Ruby, C#, Go, Objective-C/Swift.   If you have familiarity with any Lisp dialect (i.e., CLOS, Scheme, etc.), we can talk.

For those university students not enrolled in the MPCS:

For those students wishing to audit this course:

III. COURSE DESCRIPTION

V. ACADEMIC INTEGRITY

Students are expected to have read and understood the University's policy on Academic Integrity. This policy is detailed in the Student Manual of University Policies and Regulations, available online at https://masters.cs.uchicago.edu/page/program-policies.
 

VI. METHOD OF INSTRUCTION

Methods include lecture and project-related assignments. Your team work should be stored using a version-control system that allows us to easily view files and folders that you create.
 

VII. OTHER COURSE INFORMATION

Attendance:

No formal attendance taken. Absences will affect your team and likely impact your peer evaluation.  There may be information presented in class that is not in the texts. You will find the lectures helpful in doing the laboratory exercises.

Make-up Work:

Students are expected to read the assigned texts before class in order to be able to full participate in the discussions and course activities.
 

VIII. METHOD OF EVALUATING STUDENT PROGRESS

Assigned work evaluated as follows:

Grading scale:
 
95-100:     A
90-94:       A-
87.6-89:    B+
83-87.5:    B
80-82.9:    B-
76-79:       C+

Lab Deliverables will be graded on a 5-point basis.  Deliverable due dates are noted on the lab pages.  All labs and homework are due by 5:00 pm on the due date. For instructions about how to submit your lab work using svn/Subversion, see this page

All assignments are due as specified on this syllabus and lab and other deliverables.  This includes the final project deliverables.  Each team will be evaluated on the basis of the presentation of iteration deliverables and the final deliverable.  Any and all lateness will suffer penalties.  The penalty for late labs will be .50 points off for each 24-hour period the lab is late, through ten days late (10*.50=5.0).  After ten days delay, the lab will no longer be accepted for grading and will receive a 0.

The course project will be presented by all teams on August 23, 2018 for all students.  The requirements for the course project are described here.

NB:  The end of the quarter is the time at which the final grade you have earned through your work in the quarter is recorded with the registrar.  There is no extra credit offered in this course, either at the beginning or at the end.  If you are dissatisfied with the grade you have earned at the end of the quarter, your only options will be to retake the course the next time it is offered, or accept the grade you earned.

NB: The instructor reserves the right to alter the course contents, dates, times or percentage of credit based on time allowed and class progress through the course material. The instructor also reserves the right to curve grades if he deems it in the best interest of the majority of students.

IX. COURSE SCHEDULE

The following abbreviations reference the following works (see esp. Required Reading under Schedule below):

Abbreviation	Referenced Text
BCT	Bitcoin and Cryptocurrency Technologies.  Narayanan et. al.
MB	Mastering Bitcoin, Antonopoulos

Articles* (Abbreviations Key for Required texts (see esp. Required Reading under Schedule below):

*Articles starred may be found on the cluster under my pub directory (~mark/pub/56600/pdfs).  All numbers refer to chapters in texts, not pages, unless otherwise noted (as "pp. xxx").

EVERYONE:  Sign up on Piazza here!