📅 Original date posted:2013-05-31 📝 Original message:On Fri, May 31, 2013 at ...

Jeff Garzik [ARCHIVE] /

npub1kf0…3f58

2023-06-07 15:02:34

in reply to nevent1q…grcq

📅 Original date posted:2013-05-31
📝 Original message:On Fri, May 31, 2013 at 7:56 AM, Rune Kjær Svendsen <runesvend at gmail.com> wrote:
> Hello dear list
>
> I have an application that wants to keep up with new blocks as they come in.
> For that I can use the -blocknotify option with bitcoind, which will execute
> my application for each new block.
>
> The problem is that my app isn't necessarily quick enough to finish its work
> before a new block comes in and the app is executed again. This means the
> that bitcoind might keep executing my application even though the previous
> instance hasn't finished, and that's fairly inefficient resource-wise, as
> many instances of the application will be running simultaneously.
>
> I've discussed this with wumpus on bitcoin-dev, and we figured out a
> solution that might be better. It could replace -blocknotify or we could put
> it in a new function called -batchblocknotify

Similar to other suggestions in this thread,

If your -blocknotify execution is too slow, then create a solution
that simply queues work. There is no need to add this code to
bitcoind itself.

Another solution is modifying pynode to directly listen to a trusted
node (bitcoind), and monitor blocks as they arrive and are announced.
That does not fix the problem of slow block processing on your side,
but is another way to implement -blocknotify-like behavior.

--
Jeff Garzik
Senior Software Engineer and open source evangelist
BitPay, Inc. https://bitpay.com/

Author Public Key

npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58

Show more details

Published at

2023-06-07 15:02:34

Kind type

1 Short Text Note

Event JSON

{ "id": "bcc658578247de80d0b6dab524a1941a1100dcabeafc8974cb5b12ef2d43f410", "pubkey": "b25e10e25d470d9b215521b50da0dfe7a209bec7fedeb53860c3e180ffdc8c11", "created_at": 1686150154, "kind": 1, "tags": [ [ "e", "ef3511574a96b47529fa1d6c1878eeed24d9a6448c393b6a3a9eb7b72164923e", "", "root" ], [ "e", "9cb74abf9e327eb93c7eadb8f5443c65bb8266feddced2619fc2ac510e7da525", "", "reply" ], [ "p", "99bec497728c848e65549d1a5257d08de97621edcb4b77073269a45dac708d59" ] ], "content": "📅 Original date posted:2013-05-31\n📝 Original message:On Fri, May 31, 2013 at 7:56 AM, Rune Kjær Svendsen \u003crunesvend at gmail.com\u003e wrote:\n\u003e Hello dear list\n\u003e\n\u003e I have an application that wants to keep up with new blocks as they come in.\n\u003e For that I can use the -blocknotify option with bitcoind, which will execute\n\u003e my application for each new block.\n\u003e\n\u003e The problem is that my app isn't necessarily quick enough to finish its work\n\u003e before a new block comes in and the app is executed again. This means the\n\u003e that bitcoind might keep executing my application even though the previous\n\u003e instance hasn't finished, and that's fairly inefficient resource-wise, as\n\u003e many instances of the application will be running simultaneously.\n\u003e\n\u003e I've discussed this with wumpus on bitcoin-dev, and we figured out a\n\u003e solution that might be better. It could replace -blocknotify or we could put\n\u003e it in a new function called -batchblocknotify\n\nSimilar to other suggestions in this thread,\n\nIf your -blocknotify execution is too slow, then create a solution\nthat simply queues work. There is no need to add this code to\nbitcoind itself.\n\nAnother solution is modifying pynode to directly listen to a trusted\nnode (bitcoind), and monitor blocks as they arrive and are announced.\nThat does not fix the problem of slow block processing on your side,\nbut is another way to implement -blocknotify-like behavior.\n\n-- \nJeff Garzik\nSenior Software Engineer and open source evangelist\nBitPay, Inc. https://bitpay.com/", "sig": "7523d040d4c452a9bbe5f4178934bd484f53936ae3b72ce89057f091967eda3b55a66c9265430ff9ac2015b433f8ed347f2e6c61f5c5a51a56f4becef2c7c359" }