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

[CONSENSUS] Generate asynchronous event channel for state synchronization #618

Open
9 tasks
Tracked by #890
gokutheengineer opened this issue Mar 24, 2023 · 1 comment
Open
9 tasks
Tracked by #890
Assignees
Labels
consensus Consensus specific changes

Comments

@gokutheengineer
Copy link
Contributor

gokutheengineer commented Mar 24, 2023

Objective

Currently, state sync events are sent and received using the common event channel. The objective is to create a separate channel for state sync module and consensus module interaction.

Origin Document

Goals

  • Separate interaction between state sync events from the main event bus.

Deliverable

  • New event bus between state sync and consensus modules.

Non-goals / Non-deliverables

  • Change business logic

General issue deliverables

  • Update the appropriate CHANGELOG(s)
  • Update any relevant local/global README(s)
  • Update relevant source code tree explanations
  • Add or update any relevant or supporting mermaid diagrams

Testing Methodology

  • Task specific tests or benchmarks: make ...
  • New tests or benchmarks: make ...
  • All tests: make test_all
  • LocalNet: verify a LocalNet is still functioning correctly by following the instructions at docs/development/README.md

Creator: @gokutheengineer
Co-Owners: @Olshansk

@gokutheengineer gokutheengineer added the consensus Consensus specific changes label Mar 24, 2023
@gokutheengineer gokutheengineer self-assigned this Mar 24, 2023
@Olshansk
Copy link
Member

@gokutheengineer Were you think of a different event bus, or just a different channel (i.e. go channel) that's maintained by the bus?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
consensus Consensus specific changes
Projects
Status: Backlog
Development

No branches or pull requests

3 participants