### Week 0 ..May 07 - *Review Period* - Studying Schnorr signatures in depth (Mastering Bitcoin, online resources) ### Week 1 May 08..May 15 - *Kick-Off and Onboarding* - Knowledge exchange with mentors (what research has already been done?, Is there anything existing to build on already?, how can they support me?, exchanging important resources) - Exchanging ideas with the mentors on how to tackle the implementation, what to consider (e.g. RoboSats specific details) ### Week 2 May 16..May 22 - *start of project phase 1* Research: - Reading BIPs (86, 114, 340, 341, 342) - Learning Miniscript - Researching MuSig2 ### Week 3-4 May 23..June 05 - Researching P2P pipelines/contracts (existing ones, iterating on new ones) - Exchange with RoboSats devs and mentors on researched pipelinesΒ  ### Week 5-6 June 06..June 19 - Construction of the contract in Miniscrip, clear definition and documentation ### Week 7-8 June 06..July 01 - Beginning with Rust implementation of Pipeline - First simple functions to verify and test defined outputs ## First evaluation [July 01..July 05] - time buffer, otherwise continuing implementation ### Week 9-10 July 04..July 17 - Implementation of functional CLI tool (client and coordinator) - Reviewing pipeline again, new insights? ### Week 11-12 July 18..July 31 - Implementation of RoboSats specific functionality to prepare for integration - Documentation - Thorough testing (Function tests, Signet tests) ### Week 13-14 August 01..August 15 - *finishing* If sufficient time is left: - Compile to WASM binary, bundle into NPM package - Experiment with integration in RoboSats client and coordinator * Discuss about UI implementation and userspace documentation - Finish up code and documentation.Β  - Review with mentors - Submission πŸŽ‰πŸ€–πŸŽ‰πŸ€–πŸŽ‰πŸ€–πŸŽ‰πŸ€–πŸŽ‰ ⛓️⛓️⛓️⛓️⛓️⛓️⛓️⛓️⛓️