vault backup: 2025-02-20 16:21:47

This commit is contained in:
Boyan 2025-02-20 16:21:47 +01:00
parent 88c988e284
commit f5bf5e4f3e
2 changed files with 8 additions and 7 deletions

View File

@ -27,15 +27,16 @@
"state": {
"type": "markdown",
"state": {
"file": "Software Engineering/Initial Questions.md",
"file": "Software Engineering/Meeting.md",
"mode": "source",
"source": false
},
"icon": "lucide-file",
"title": "Initial Questions"
"title": "Meeting"
}
}
]
],
"currentTab": 1
}
],
"direction": "vertical"
@ -213,11 +214,11 @@
"omnisearch:Omnisearch": false
}
},
"active": "fcc28e70ad8acbd2",
"active": "2768622d9c36a711",
"lastOpenFiles": [
"Software Engineering/Initial Questions.md",
"Software Engineering/Meeting.md",
"Software Engineering/TA Meeting 1.md",
"Software Engineering/Meeting.md",
"Extracurricular/Misc/Plan.md",
"Extracurricular/Misc/Proposed Routine Plan.canvas",
"Extracurricular/Misc/Ideas.md",

View File

@ -1,7 +1,7 @@
### Logistics
- Will we have access to an overview of the project roadmap, including deliverables?\
> No. It is a research project, hence no deliverables and such.
> **No. It is a research project, hence no deliverables and such.**
- Do you need us to use specific project management tools (e.g. GitHub, Jira, etc.)?
- How often are you available? Is it possible to have weekly progress reports?
> Every week is good.
@ -10,7 +10,7 @@
> It's possible to catch up to speed in a couple of months
- Can you explain the process by which a smart contract's safety properties will be validated formally?
- Are there any existing case studies or example proofs we might refer to for a better understanding of the expected output?
> > You will be linked to existing projects
> You will be linked to existing projects
- Define the contract verification criteria
### Project scope clarifications
- Among the seven smart contracts being verified, which ones do you expect us to work on, and why those?