Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make a state machine design for dst software that is independant of perun contract versions. #11

Closed
manoranjith opened this issue Nov 13, 2019 · 2 comments
Assignees
Milestone

Comments

@manoranjith
Copy link
Contributor

dst project implements perun protocol to do offchain transactions. Current version of dst-go uses legacy contracts.

The contracts are being developed further and new versions are coming up. In near future, the dst-go project will have to be use these new versions. To provide a direction for this migration, a state machine design that can accommodate the workflows of both legacy and new versions needs to be created. The design should also be flexible to easily accommodate changes in contract that might come up in future.

The state machine design can be done in UML using plantuml tool. PlantUML tools allows one to write a UML diagram as simple text file (see here), from which PNG, JPEG and such image files can be created. This will also enable the changes to be easily tracked using version control systems like git.

@manoranjith manoranjith added this to To do in dst development via automation Jan 27, 2020
@manoranjith manoranjith added this to the v0.2.0 milestone Jan 27, 2020
@anagha-ks anagha-ks self-assigned this Feb 18, 2020
@project-bot project-bot bot moved this from To do to In progress in dst development Feb 18, 2020
manoranjith pushed a commit to boschresearch/dst-statemachine that referenced this issue Mar 18, 2020
- Also Readme file is updated.

Relates to hyperledger-labs/perun-doc#11

Signed-off-by: Anagha K Sukumaran <sukumaran.anaghak@in.bosch.com>
@anagha-ks
Copy link
Contributor

First version of State machine diagrams have been added here

@manoranjith
Copy link
Contributor Author

Issue closed, as it relates to the older implementation which is now archived on legacy/master

dst development automation moved this from In progress to Done May 6, 2020
@choeppler choeppler removed this from Done in dst development Aug 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants