<p>In the case of a notice at 0 confirmations, I'm seeing the transaction end up on blockchain.info a lot faster than bitcoind is calling the walletnotify callback - about 10 minutes faster. Is it possible to speed this up?</p>

CC BY-SA 3.0
2018-04-16T10:04:18.753Z
How well connected is your node? 10 minutes is a long delay
Raghav Sood
CC BY-SA 3.0
2018-04-16T14:44:50.930Z
is your wallet synced? because bitcoind send the notification once they received your transaction. make sure your bitcoind is synced.
Tailer
CC BY-SA 3.0
2018-04-16T15:02:10.520Z
Yes, it seems to be synched (blockcount is accurate).
Fibericon
CC BY-SA 3.0
2018-04-16T15:10:32.753Z
@RaghavSood 124 from getconnectioncount
Fibericon
CC BY-SA 3.0
2018-04-19T19:29:44.753Z
When you see the transaction on blockchain.info, are you sure the transaction is not in bitcoin already? Is it possible that whatever is being called just takes a long time to respond?
Ava Chow
CC BY-SA 3.0
2018-04-19T20:47:45.630Z
I'd suggest log a timestamped message with the callback, and the exact message as well to see its `confirmations`. Also test with sending bitcoin, in which case, `walletnotify` is called twice with `confirmations=0`, and once with `confirmations=1`. See if there's any delay. You could also test with `blocknotify` and log the timestamp when you receive the block containing your transaction. It'd be odd that `blocknotify` is triggered but your `walletnotify` is not
Will Gu
<bitcoind><wallet-notify>
Speeding up walletnotify
Fibericon
# Speeding up walletnotify

(Asked by: username_0 on 2018-04-16)

In the case of a notice at 0 confirmations, I'm seeing the transaction end up on blockchain.info a lot faster than bitcoind is calling the walletnotify callback - about 10 minutes faster. Is it possible to speed this up?

**Tags:** bitcoind, wallet-notify

> **Comments:**
> **username_1**: How well connected is your node? 10 minutes is a long delay  
> **username_2**: is your wallet synced? because bitcoind send the notification once they received your transaction. make sure your bitcoind is synced.  
> **username_0**: Yes, it seems to be synched (blockcount is accurate).  
> **username_0**: @username_1 124 from getconnectioncount  
> **username_3**: When you see the transaction on blockchain.info, are you sure the transaction is not in bitcoin already? Is it possible that whatever is being called just takes a long time to respond?  
> **username_4**: I'd suggest log a timestamped message with the callback, and the exact message as well to see its `confirmations`. Also test with sending bitcoin, in which case, `walletnotify` is called twice with `confirmations=0`, and once with `confirmations=1`. See if there's any delay. You could also test with `blocknotify` and log the timestamp when you receive the block containing your transaction. It'd be odd that `blocknotify` is triggered but your `walletnotify` is not  

---

## 0 answers

