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

Add API to query account sequence number in mempool #683

Closed
1 of 4 tasks
zemyblue opened this issue Sep 21, 2022 · 0 comments · Fixed by #840
Closed
1 of 4 tasks

Add API to query account sequence number in mempool #683

zemyblue opened this issue Sep 21, 2022 · 0 comments · Fixed by #840
Assignees
Labels
A: improvement Changes in existing functionality

Comments

@zemyblue
Copy link
Member

Summary

In order to know the appropriate the sequence number of the account, we need to be able to inquire the sequence number of the account registered in the mempool.

Problem Definition

If some target node is down, we need to wait or change the target node.
However, if the transaction created by the account exists in the mempool in the changed target node when changing the target node, the appropriate sequence number of the account cannot be retrieved.

Background

  • The normal query api for the account info is inquired from deliverState.
  • This deliverState is updated when the block is confirmed. So we cannot query the information to be reflected in mempool through the normal query api.

So we need to be able to query the sequence number of the account in the mempool.

Proposal

Add the query api about account info from checkState.


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
@zemyblue zemyblue added the A: improvement Changes in existing functionality label Sep 21, 2022
@tkxkd0159 tkxkd0159 self-assigned this Dec 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A: improvement Changes in existing functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants