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

[Feature Request] walletnotify config argument #17

Open
EggPool opened this issue Mar 13, 2018 · 2 comments
Open

[Feature Request] walletnotify config argument #17

EggPool opened this issue Mar 13, 2018 · 2 comments
Assignees

Comments

@EggPool
Copy link
Collaborator

EggPool commented Mar 13, 2018

From @Aareon

Reference: https://en.bitcoin.it/wiki/Running_Bitcoin

A wallet transaction includes any transaction for any given address belonging to said wallet.

Usage: -walletnotify=echo “Transaction received... TXID: %s”

@EggPool EggPool self-assigned this Mar 13, 2018
@EggPool
Copy link
Collaborator Author

EggPool commented Mar 15, 2018

@Aareon How do you deal with rollbacks?
You can be notified several times of the same tx, or be notified for a tx that will disappear later on
(even if we wait for a minimum number of confirmations, and in that case, it's no more real time)

@Aareon
Copy link

Aareon commented Mar 15, 2018

Walletnotify typically notifies twice per transaction. Once when it arrives, another when it gets one confirmation. If a transaction doesn’t confirm, it’s up to whatever is taking said notifications to handle that logic. I failed to mention that this is how it works, I apologize.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants