-
Notifications
You must be signed in to change notification settings - Fork 38
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
Add modules.md #401
Add modules.md #401
Conversation
The module may also have another storage (other than DMS) to store its | ||
internal states, which can deduce the set of messages to be broadcasted upon | ||
the `flush`() operation. | ||
- In the `update()` operation, the module reads the message stored in DMS and |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ditto.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Plus, does the module read a single message during the update()
operation? If not, please fix to messages.
- During each operation, the module may store some messages to its local DMS. | ||
- In the `flush()` operation, the module stores all the messages it wants to | ||
broadcast. These messages may or may not have been stored by other operations. | ||
The module may also have another storage (other than DMS) to store its |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How is this done?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you mean?
## Repository | ||
|
||
TODO | ||
|
||
## Governance | ||
|
||
TODO | ||
|
||
## Consensus | ||
|
||
TODO | ||
|
||
## Chat | ||
|
||
TODO |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about leaving documents under each module's repository and putting a link to it above in Modules section?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure. Let's think about after we got actual contents
Co-authored-by: Taehoon Tom Kim <kim.taehoon@snu.ac.kr>
2. Governance: This module manages a node's client in the p2p governance voting | ||
protocol. | ||
3. Consensus: This module manages a node's state machine of the BFT algorithm | ||
(Vetomint). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(Vetomint). | |
([Vetomint](https://github.com/postech-dao/simperby/blob/main/docs/vetomint.md)). |
I think it would be nice to have a link.
After some more consideration while designing the interface, I think this description is slightly outdated and I need another way to explain the structure. Let me revisit this issue soon. |
No description provided.