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
On Fri, May 31, 2013 at 5:56 AM, Rune Kjær Svendsen runesv...@gmail.comwrote:
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
On Fri, May 31, 2013 at 2:10 PM, Michael Hendricks mich...@ndrix.orgwrote:
On Fri, May 31, 2013 at 5:56 AM, Rune Kjær Svendsen
runesv...@gmail.comwrote:
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,
On Fri, May 31, 2013 at 7:56 AM, Rune Kjær Svendsen runesv...@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
I just posted the following to bitcointalk.
https://bitcointalk.org/index.php?topic=221164.0
Right now between two to four running the largest pools control Bitcoin
in the short term. That's a lot of hashing power in the hands of very,
very few people. In addition pools have little incentive to
I like this idea a lot.
To add: I think it is a bug and security risk if pooled-solo or (current
pooled miners) do not add randomness to their extraNonce2 (like 128-bits of
it). For privacy and to avoid various hostile-pre-mining attacks it should
be done this way. Lack of the self-chosen
On Fri, May 31, 2013 at 8:37 AM, Rune Kjær Svendsen runesv...@gmail.com wrote:
I've thought about this as well. It just seems somewhat clunky to me. I'd
really prefer having bitcoind put out messages in batches, if it's doable,
that is.
I'd run into a lot of concurrency issues, as far as I
On Fri, May 31, 2013 at 11:56 PM, Rune Kjær Svendsen
runesv...@gmail.com wrote:
I'm not quite so how to go about this.
As others have said, queuing outside of bitcoind is a better approach.
I use zeromq for this situation. blocknotify runs a program which uses
zeromq's pub/sub to queue and the
Chris,
Using zmq is a great fit for high-speed notifications such as this. Have
you seen the pull request to integrate zmq directly into bitcoind, so that
you don't even need -blocknotify?
https://github.com/bitcoin/bitcoin/pull/2415
If not: we could use some testing there!
Wladimir
On Sat,
On Sat, Jun 1, 2013 at 11:29 AM, Wladimir laa...@gmail.com wrote:
Using zmq is a great fit for high-speed notifications such as this. Have you
seen the pull request to integrate zmq directly into bitcoind, so that you
don't even need -blocknotify?
https://github.com/bitcoin/bitcoin/pull/2415
10 matches
Mail list logo