Monitor transactions and/or blocks #12

1. 
   gavinandresen commented at 2:40 pm on December 22, 2010: contributor

   Design and implement a RPC call to register a HTTP-JSON-RPC callback, and have it get called when blocks and/or “transactions of interest” occur.

   Gavin has already implemented a version of this; unresolved issues are:

   • How to specify which transactions are “of interest” ? Transactions to a specific address after A/B/C confirmations? All transactions to (or from?) the wallet? All transactions to (or from?) a specific account?

   Note: information reported should be same as gettransaction.

   • What information to report about blocks (if any). Perhaps implement a getblock before monitorblock.
2. 
   gavinandresen commented at 7:36 pm on January 6, 2011: contributor

   Discussion here: http://www.bitcoin.org/smf/index.php?topic=2647.0
3. 
   mndrix commented at 6:09 pm on February 9, 2011: contributor

   If debug.log showed full transaction IDs in the “got inventory” line, one could do:

   0tail -F debug.log | grep "got inventory.*new" | my-script
   

   to monitor for new transactions and then run gettransaction to see the details. For some projects, this would be easier since no HTTP server is required. As it is, only partial transaction IDs are visible in debug.log so this doesn’t work.

4. 
   jgarzik commented at 6:22 am on February 10, 2011: contributor

   Suggested monitorblocks API posted to forum.
5. 
   jgarzik commented at 9:28 pm on July 5, 2012: contributor

   The current -blocknotify seems to take care of this. Addressing $IssueText directly, HTTP callbacks seem to have lost favor over program execution.
6. jgarzik closed this on Jul 5, 2012

   ---

7. jefflarkin referenced this in commit fe36ba4db8 on Apr 30, 2013
8. nelisky referenced this in commit 884ededd8f on Nov 8, 2013
9. justmoon referenced this in commit 5bc9ac0437 on Apr 7, 2014
10. rdponticelli referenced this in commit 634bc1820c on Nov 26, 2014
11. MarcoFalke referenced this in commit 313e7f5c89 on Oct 9, 2015
12. brishtiteveja referenced this in commit 9880cb9b1a on Jan 25, 2016
13. brishtiteveja referenced this in commit 0a8227f744 on Jan 25, 2016
14. ptschip referenced this in commit 0521802eda on Feb 17, 2016
15. destenson referenced this in commit 19b95268bb on Jun 26, 2016
16. Christewart referenced this in commit 18a606d524 on Jun 17, 2017
17. CryptAxe referenced this in commit c7317ce9c0 on Jun 20, 2017
18. AkioNak referenced this in commit 59fa42a9b9 on Jul 24, 2017
19. MarcoFalke referenced this in commit a68aed5c27 on Sep 29, 2017
20. ptschip referenced this in commit a19dd533dd on Nov 4, 2017
21. CryptAxe referenced this in commit 41231a2458 on Dec 28, 2017
22. classesjack referenced this in commit 74bea6adf4 on Jan 2, 2018
23. KrzysiekJ referenced this in commit c71b057f3b on Mar 28, 2018
24. effectsToCause referenced this in commit 0146695e2d on Jun 22, 2018
25. dooglus referenced this in commit 6d4d468db7 on Oct 21, 2018
26. DigiGreenCoin referenced this in commit 4125432ebc on Oct 29, 2019
27. Warchant referenced this in commit 7958da26e8 on Dec 31, 2019
28. KolbyML referenced this in commit 94c2fdffb6 on Aug 1, 2020
29. laanwj referenced this in commit 924a4ff7eb on Oct 29, 2020
30. MarcoFalke referenced this in commit bce09da122 on Apr 28, 2021
31. fanquake referenced this in commit fa00bb2c5c on Apr 29, 2021
32. cryptapus referenced this in commit dd908da96b on May 3, 2021
33. MarcoFalke referenced this in commit eb9a1fe037 on May 7, 2021
34. MarcoFalke referenced this in commit c857148636 on May 15, 2021
35. rajarshimaitra referenced this in commit c4346af75c on Aug 5, 2021
36. DrahtBot locked this on Sep 8, 2021

Contributors
gavinandresen mndrix jgarzik

Labels
Feature