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

Lack of prioritization for Peggo orchestrator messages #179

Open
4 tasks
facundomedica opened this issue Feb 15, 2022 · 1 comment
Open
4 tasks

Lack of prioritization for Peggo orchestrator messages #179

facundomedica opened this issue Feb 15, 2022 · 1 comment
Labels

Comments

@facundomedica
Copy link

TOB-UMEE-031

The Peggo orchestrator's messages have no priority over other transactions whether they get included in a block or not. As a result, the orchestrator transactions may not be included in earlier blocks when the network is highly congested. This is a similar problem to the one described in finding TOB-UMEE-020


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
@facundomedica
Copy link
Author

Blocked until the new version of Cosmos SDK is out. This might not be the right place for this issue as it's something that should be done in the GB module.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant