2
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?
2
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?
How well connected is your node? 10 minutes is a long delay – Raghav Sood – 2018-04-16T10:04:18.753
is your wallet synced? because bitcoind send the notification once they received your transaction. make sure your bitcoind is synced. – Adam – 2018-04-16T14:44:50.930
Yes, it seems to be synched (blockcount is accurate). – Fibericon – 2018-04-16T15:02:10.520
@RaghavSood 124 from getconnectioncount – Fibericon – 2018-04-16T15:10:32.753
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? – Andrew Chow – 2018-04-19T19:29:44.753
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,walletnotifyis called twice withconfirmations=0, and once withconfirmations=1. See if there's any delay. You could also test withblocknotifyand log the timestamp when you receive the block containing your transaction. It'd be odd thatblocknotifyis triggered but yourwalletnotifyis not – Will Gu – 2018-04-19T20:47:45.630