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

Visualization of Messages #15

Open
amiller opened this issue May 30, 2017 · 1 comment
Open

Visualization of Messages #15

amiller opened this issue May 30, 2017 · 1 comment

Comments

@amiller
Copy link
Owner

amiller commented May 30, 2017

A visualization of the protocol flow could facilitate understanding the protocol flow for newcomers. It could also provide a way to help debugging or diagnosing network problems/faults. Also it could help build a mental model for the relative costs and bandwidth usage for protocol components.

One of HoneyBadgerBFT's features is its regular message pattern. Each possible message fits into a predefined possibly possible slot. To me this suggests a "grid" layout to make the structure as clear as possible. Here's a mockup/sketch of a visualization panel:

honeybadger message dashboard 2

This would be a display of a single node's view of a single block/epoch of the honey badger protocol. The idea is that each possible message that could be received would be indicated by an unlit light (grey square), when such message is received, the light turns yellow. Messages sent

This visualization makes some invariants clear. For example, in Reliable Broadcast, only one ECHO message and one READY message can be received from any node (redundant such messages are discarded). In the case of Binary Agreement, possibly both of EST(0) or EST(1) could be received.

@sbellem
Copy link
Contributor

sbellem commented Aug 24, 2018

This issue was moved to initc3/HoneyBadgerBFT-Python#35

/cc @amiller

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