This repository has been archived by the owner on Apr 21, 2023. It is now read-only.
poll unconfirmed transactions in a loop #580
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Setup a loop to trigger a receipt of unconfirmed transactions over already established websocket channel. This should solve several recurring issues:
and maybe more. User experience is definitely increased. Possible side-effects (as described under #418 don't normally happen - multiple users don't watch the same address and if they do (i.e. cosigners of the same address), they are not on the same server/node, statistically. Even on the same node, it would be acceptable overhead in sake of user experience/usability. Last but not least - the side effect should be solved on server, anyway.