If an unconfirmed transaction pointer has been pending for more than 10 minutes it will turn into a failed transaction pointer and records spent will be unspent, this check at the start of scans.
Scenario:
If the user left the app with a pending transaction and then comes back after at least >(10 - {amount of time already pending}) minutes then the transaction pointer will be rendered failed at the start of the next scan and when the transaction is found it currently does not update the current pointer but creates a new externally executed transaction as shown in the attached image below.
Note: Since we have checks on records stored this does not cause double counting it just causes the same transaction to be shown twice.
Version
v0.0.1-alpha
What operating system are you using?
None
Relevant log output
No response
Code of Conduct
[X] I agree to follow this project's Code of Conduct
Contact Details
None
contact
No response
What happened?
If an unconfirmed transaction pointer has been pending for more than 10 minutes it will turn into a failed transaction pointer and records spent will be unspent, this check at the start of scans.
Scenario: If the user left the app with a pending transaction and then comes back after at least
>(10 - {amount of time already pending})minutes then the transaction pointer will be rendered failed at the start of the next scan and when the transaction is found it currently does not update the current pointer but creates a new externally executed transaction as shown in the attached image below.Note: Since we have checks on records stored this does not cause double counting it just causes the same transaction to be shown twice.
Version
v0.0.1-alpha
What operating system are you using?
None
Relevant log output
No response
Code of Conduct