Split broadcast state machine into two separate state machines
Open
enhancement
P3
- Dominant language
- Go
- Stars
- 1
- Forks
- 3
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 6
Description
We currently have a single broadcast state machine abstraction that can deal with all direct and permanent states (permanent+secondary), however, direct states never transition to permanent states, and vice versa. Therefore, we should really have two separate broadcast state machines; a direct broadcast state machine, and a permanent broadcast state machine. Then on entry into the state machine code, we enter the respective state machine based on the config parameters. This should greatly clean up the broadcast state machine code and make it easier to follow.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.