Skip to content
This repository has been archived by the owner on Mar 15, 2023. It is now read-only.

near: ensure execution outcomes are finalized #36

Closed
heyitaki opened this issue Dec 29, 2022 · 0 comments · Fixed by #34
Closed

near: ensure execution outcomes are finalized #36

heyitaki opened this issue Dec 29, 2022 · 0 comments · Fixed by #34

Comments

@heyitaki
Copy link
Contributor

A transaction that is included in a finalized block may contain execution outcomes that are included in unfinalized blocks. Take for example this transaction that was executed in block 81623098 and has WH logs from receipt
8BD19w75XUxtsyPXqJVqB5cY5jL1452wqL1WNETEWLHG executed in block 81623100 2 seconds later.

A possible solution is to use a queue of transactions to fetch and re-add a transaction to queue to be processed later if it has an unfinalized outcome, similar to the way the NEAR guardian watcher works.

@heyitaki heyitaki changed the title near: near: ensure execution outcomes are finalized Dec 29, 2022
@heyitaki heyitaki mentioned this issue Jan 2, 2023
@aadam-10 aadam-10 linked a pull request Mar 15, 2023 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.

2 participants