Skip to content
This repository has been archived by the owner on Dec 5, 2022. It is now read-only.

Error occured that "account sequence mismatch" #98

Open
gyuguen opened this issue Nov 4, 2022 · 0 comments · May be fixed by #101
Open

Error occured that "account sequence mismatch" #98

gyuguen opened this issue Nov 4, 2022 · 0 comments · May be fixed by #101
Assignees

Comments

@gyuguen
Copy link
Contributor

gyuguen commented Nov 4, 2022

Background

I had run two oracles, one is old oracle and the other oracle is the new oracle.
When an event occurs, both oracles subscribe at the same time.
And at the same time execute the transaction.
Two transactions are received in blockChain at the same time.
Resultly, One transaction is success, another transaction is failed.
The failed reason is account sequence mismatched.

Implement

When oracle starts, it gets the active uniqueID from the blockchain and compares one's own uniqueID.

  • If two uniqueID match, Oracle starts subscribing to the vote event.
  • Is not matched, Oracle doesn't subscribe to the vote event.
  • In both case, It does subscribed OracleUpgradeEvent.

And when Oracle receives OracleUpgradeEvent, it compares one's own UniqueID.

  • If two uniqueID match, Oracle starts subscribing to the vote event.
  • Is not matched, Oracle stopping subscribe to the vote event.
@gyuguen gyuguen added this to the Oracle Upgrade milestone Nov 4, 2022
@gyuguen gyuguen self-assigned this Nov 4, 2022
@gyuguen gyuguen linked a pull request Nov 9, 2022 that will close this issue
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant