Instructor: Wu-chang Feng
Zoom (T/Th 8am-9:50am): link
TA: Wenjing Wu (OdinID wwu , DM @wen pdx-cs.slack.com
Contact and discussion:

• DM @wuchang pdx-cs.slack.com
• Leave anonymous feedback here
• #cs410_510_blockchain on pdx-cs Slack

Office hours: here over Zoom
TA office hours: Friday 10am-noon on Zoom
Course material

• Attendance form
• Screencasts on MediaSpace
• Course slides: PSU Google Drive | old version
• Course student reviews
• Google's write-up

Useful links

• Python overview | screencast
• Metamask extension
• PSU Ropsten faucet
• MyCrypto web-based wallet (use with Metamask)
• Remix IDE
• Security Innovation CTF
• Ethereum unit converter
• Ethsum address checksums
• Etherscan (Ropsten) explorer
• Ethernaut CTF

Course Description This class provides an overview of blockchain systems, how they are built, and how they can be exploited. Students will get hands-on experience working with public blockchains such as Ethereum as well as build and deploy permissioned blockchains using Hyperledger Sawtooth on Google Cloud Platform. They will then examine security vulnerabilities in blockchain systems and how they may be automatically exploited.

• Examine the underpinnings of blockchain systems and their applications
• Develop and deploy blockchain applications and smart contracts (DApps)
• Analyze smart contracts for security vulnerabilities

• Exploit smart contract vulnerabilities
• Use symbolic execution to automatically reveal smart contract vulnerabilities

Grading

Attendance and participation	5%
Lab notebooks and code repository	65%
Final Project	30%

Attendance and participation Whether you are in-person or remote, class is synchronous and attendance is graded. Sometime during each class, the attendance form linked above will be enabled. Visit it and submit the form to record your attendance. If you miss class, extra credit will be given back for participation in the Slack channel. You are expected to follow this code of conduct when communicating.

Academic misconduct

• Includes allowing another student to copy your work unless specifically allowed by the instructor.
• Includes copying blocks of code from external sources without proper attribution
• Results in a grade of 0 for the assignment or exam.
• Results in the initiation of disciplinary action at the university level.

Lab notebooks, git repository
Lab assignments will be given each class covering the course material. You will perform each one, while maintaining a lab notebook in a Google Doc that documents your progress via screenshots with your OdinID, Google Cloud project identifier, or wallet address in them. Notebooks should be exported as a PDF file and include a table of contents generated by Google Docs. Submission will be done via adding, committing and pushing the file to your private course git repository. Notebooks are in sections (e.g. 1-5) and are due Friday of the following week the last lab in the section is assigned. Use the following naming convention to submit your notebooks.

• notebooks/<section_number>.pdf e.g. notebooks/1.pdf for the Sawtooth labs
  

The notebook will be graded based upon the following rubric:

• Neatness and organization
• Completeness
• Inclusion of OdinID, Google Cloud project identifier, or wallet address in screenshots

For notebook submission and assignments that require code to be written, you will maintain a private git repository that will be setup in the first assignment. You will share the repository with the instructor and TA.

Final project
You will build a DApp of your own using Vyper and/or web3.js. Then, via a narrated screencast of no more than 15 minutes, you have done via a demo and a source code walkthrough. Submission instructions and a grading rubric will be given when the project is assigned.