...
- To review existing examples and approaches of automated programming for smart contracts on of other platforms (i.e., Solidity).
- To explore the technically feasible options of automated programming for Hyperledger Fabric (incl. chatGPT) and select one for further work.
- To formulate a chaincode specification style which “seems to work well enough” on a set of representative examples. (We don’t know yet what will work – One-shot/iterative? Requirement set or BDD? Conversational or formal? Etc.)
- To create support for translating the specification partially or fully to runtime verification code, which can wrap the chaincode implementation.
...
On the other hand, we expect to experiment chiefly with Behavior-Driven Development; this means Gherkin/Cucumber.
Technology/approach for runtime verification (https://en.wikipedia.org/wiki/Runtime_verification) will depend heavily on the results on the "constructive" side - we do not want to commit on this at this point.
Learning Objectives
Expected Outcome
- A definition of a natural-language "specification conversation set", which target a diverse, representative set of smart contract functionality and their key variations. (various token contracts, cross-organizational processes,
Relation to Hyperledger
Mentee Skills
...