Timeline for Speeding up walletnotify
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Apr 27, 2018 at 20:42 | history | bounty ended | CommunityBot | ||
| S Apr 27, 2018 at 20:42 | history | notice removed | CommunityBot | ||
| Apr 23, 2018 at 16:10 | history | tweeted | twitter.com/StackBitcoin/status/988450129316405249 | ||
| Apr 19, 2018 at 20:47 | comment | added | Will Gu |
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
|
|
| Apr 19, 2018 at 19:29 | comment | added | Ava Chow♦ | 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? | |
| S Apr 19, 2018 at 19:07 | history | bounty started | Fibericon | ||
| S Apr 19, 2018 at 19:07 | history | notice added | Fibericon | Draw attention | |
| Apr 16, 2018 at 15:10 | comment | added | Fibericon | @RaghavSood 124 from getconnectioncount | |
| Apr 16, 2018 at 15:02 | comment | added | Fibericon | Yes, it seems to be synched (blockcount is accurate). | |
| Apr 16, 2018 at 14:44 | comment | added | Tailer | is your wallet synced? because bitcoind send the notification once they received your transaction. make sure your bitcoind is synced. | |
| Apr 16, 2018 at 10:04 | comment | added | Raghav Sood | How well connected is your node? 10 minutes is a long delay | |
| Apr 16, 2018 at 6:39 | history | asked | Fibericon | CC BY-SA 3.0 |