25 lines
1.6 KiB
Markdown
25 lines
1.6 KiB
Markdown
|
|
### 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.
|
|
- 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.
|
|
### Formal Verification
|
|
- What is the expected level of background in Coq or formal methods?
|
|
> 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?
|
|
>
|
|
- 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?
|
|
- Which technologies are we going to be introduced to, if any? Will we have access to guides for Coq and Solidity?
|
|
- How do you envision the high-level Coq framework integrating with existing Solidity projects?
|
|
|
|
### Optional
|
|
|
|
- How much of the formal verification process will be based on axioms versus fully constructive proofs?
|
|
- Could you elaborate on the notion of “high-level primitives” (e.g., identity, item, property) and how flexible they need to be for different types of contracts?
|
|
- Could you specify what you mean by "real numbers and integer approximations"? Is it related to precision with math? How does that impact the security of a smart contract? Practical example?
|