Main page | Study Branches/Specializations | Groups of Courses | All Courses | Roles                Instructions

A course is the basic teaching unit, it's design as a medium for a student to acquire comprehensive knowledge and skills indispensable in the given field. A course guarantor is responsible for the factual content of the course.
For each course, there is a department responsible for the course organisation. A person responsible for timetabling for a given department sets a time schedule of teaching and for each class, s/he assigns an instructor and/or an examiner.
Expected time consumption of the course is expressed by a course attribute extent of teaching. For example, extent = 2 +2 indicates two teaching hours of lectures and two teaching hours of seminar (lab) per week.
At the end of each semester, the course instructor has to evaluate the extent to which a student has acquired the expected knowledge and skills. The type of this evaluation is indicated by the attribute completion. So, a course can be completed by just an assessment ('pouze zápočet'), by a graded assessment ('klasifikovaný zápočet'), or by just an examination ('pouze zkouška') or by an assessment and examination ('zápočet a zkouška') .
The difficulty of a given course is evaluated by the amount of ECTS credits.
The course is in session (cf. teaching is going on) during a semester. Each course is offered either in the winter ('zimní') or summer ('letní') semester of an academic year. Exceptionally, a course might be offered in both semesters.
The subject matter of a course is described in various texts.

NIE-BLO Blockchain Extent of teaching: 1P+2C
Instructor: Bielik M., Gattermayer J., Lórencz R., Růžička J. Completion: Z,ZK
Department: 18106 Credits: 5 Semester: Z

Annotation:
Students will understand the foundations of blockchain technology, smart contract programming, and gain an overview of most notable blockchain platforms. They will be able to design, code and deploy a secure decentralized application, and assess whether integration of a blockchain is suitable for a given problem. The course places an increased emphasis on the relationship between blockchains and information security. It is concluded with a defense of a research or applied semester project, which prepares the students for implementing or supervising implementation of blockchain-based solutions in both academia and business.

Lecture syllabus:
1. Prerequisites and fundamentals: Databases, Decentralized/distributed databases/ledgers, Blockchain-related cryptography, Consensus/trust, types of proofs, Public vs. private blockchains, Blockchain programming languages (Solidity, Rust, WASM..)
2. Cryptocurrencies and major blockchain platforms: Digital currencies, Popular platforms (Bitcoin, Ethereum, Avalanche, etc.), Smart contracts, Decentralized applications, Cryptocurrency trading, Governance, Limitations and future development
3. Systems design, hands-on development: Fitness for purpose, Software architecture, languages, and libraries, Web3.js development - mock projects / simple games, launching ICO, representing identity, exchanging data, tracking goods, smart contracts etc.
4. Security: Most notable hacks (The DAO hack, etc.), Attack vectors, Threat modelling, Anonymity, Post-quantum cryptography, Platform governance, Best practices
5. Applications and case studies: Finance, Enterprise networks, Legal relationships/contracts, Public service, Other use-cases, Startup, corporate and country case studies, Most notable blockchain apps (Uniswap, Compound, Aave, etc.)

Seminar syllabus:
1. Programming language Solidity & Ethereum Virtual Machine
2. Architecture of a decentralized application, interfaces (ERC-20, ERC-721, etc.). We create an ERC-20 token and list it on DEX on testnet
3. Front-end, back-end, co-design (which logic to code on blockchain and which not)
4. Security of blockchain applications (we take examples containing bugs and try to find them/fix them)
5. Devops/testing blockchain applications (how to properly test/deploy smart contract)
6. Economy of decentralized apps - why do we need a token?
7. Presentation of team works

Literature:
1. Bashir, Imran. Mastering Blockchain: Distributed Ledgers, Decentralization, and Smart Contracts Explained. 2nd edition, Packt Publishing, 2018.
2. Antonopoulos, Andreas M. Mastering Bitcoin: Programming the Open Blockchain. 2nd edition, O'Reilly, 2017.
3. Song, Jimmy. Programming Bitcoin: Learn How to Program Bitcoin from Scratch. O'Reilly, 2019.
4. Antonopoulos, Andreas M., and Gavin Wood. Mastering Ethereum: Building Smart Contracts and DApps. O'Reilly, 2019.
5. Gerard, David. Attack of the 50 Foot Blockchain: Bitcoin, Blockchain, Etherium and Smart Contracts.CreateSpace Independent Publishing Platform, 2017.

Requirements:
Fundamentals of cryptography, computer security (i.e. BI/E-KAB or BI/E-BEZ) and programming.

https://courses.fit.cvut.cz/NIE-BLO/

The course is also part of the following Study plans:
Study Plan Study Branch/Specialization Role Recommended semester
NI-PB.2020 Computer Security V Není
NI-ZI.2020 Knowledge Engineering V Není
NI-SPOL.2020 Unspecified Branch/Specialisation of Study V Není
NI-TI.2020 Computer Science V Není
NI-TI.2023 Computer Science V Není
NI-NPVS.2020 Design and Programming of Embedded Systems V Není
NI-PSS.2020 Computer Systems and Networks V Není
NI-MI.2020 Managerial Informatics V Není
NI-SI.2020 Software Engineering (in Czech) V Není
NI-SP.2020 System Programming V Není
NI-WI.2020 Web Engineering V Není
NI-SP.2023 System Programming V Není
NIE-SI.21 Software Engineering 2021 V Není
NIE-TI.21 Computer Science 2021 V Není
NIE-DBE.2023 Digital Business Engineering V Není
NIE-NPVS.21 Design and Programming of Embedded Systems 2021 V Není
NIE-PSS.21 Computer Systems and Networks 2021 V Není
NIE-PB.21 Computer Security 2021 V Není
NIE-DBE.2023 Digital Business Engineering PV 1


Page updated 25. 4. 2024, semester: Z,L/2023-4, Z/2019-20, Z/2024-5, L/2022-3, Z/2020-1, Z,L/2021-2, L/2020-1, Z/2022-3, L/2019-20, Send comments to the content presented here to Administrator of study plans Design and implementation: J. Novák, I. Halaška