blockchain.lucas.zip

Schedule

What happens, in what order, and roughly how far apart. The dates themselves are on the intranet. · Updated 2 September 2026

The module runs over about seven weeks: two consecutive days on site to launch it, two remote lessons, an intermediate defence, and a final defence. This page gives the sequence and the spacing; the dates, times, and rooms are on the school’s intranet, which is the reference if anything here seems to disagree with it. The module is run twice a year and the dates differ between runs; the sequence does not.

EventFormatWhen
Day 1, seminarOn site, hands-onOpens the module
Day 2, seminarOn site, hands-onThe next day. The project starts at the end of it, and everything below counts from it
Group and subject declaredOn TeamsDay 2 + 1 week
Day 3, remote lessonRemote, lectureDay 2 + 2 weeks, about
Intermediate defence30 minutes per groupDay 2 + 3 weeks, about
Day 4, remote lessonRemote, lectureDay 2 + 4 weeks, about
Code freezeEnd of a working dayDay 2 + 6 weeks, the day before the first final defence
Final defence1 hour per groupDay 2 + 6 weeks, over two defence days

Day 1’s date, which anchors all of the above, is on the intranet’s entry for this module.