Re: [Bitcoin-development] bitcoind stops responding

2013-09-30 Thread Chris Double
slush writes: > I observed this problem with version 0.8.2, but it is still happening with > 0.8.5. I see this as well with 0.8.2+. I don't see it on 0.8.1. I originally hit the '4 keep alive thread limit' where four clients on the same bitcoind would result in other clients not being able to c

Re: [Bitcoin-development] SPV client in pure JavaScript?

2013-08-12 Thread Chris Double
On Sat, Aug 10, 2013 at 12:14 AM, Mike Hearn wrote: > Oh, I forgot to make it clear - Chrome apps/extensions can make raw TCP > socket connections: > >http://blog.chromium.org/2012/11/introducing-tcp-listen-new-api-for.html There's a Raw Sockets proposal at the W3C that provides TCP sockets:

Re: [Bitcoin-development] Implementing batch processing for -blocknotify

2013-05-31 Thread Chris Double
On Sat, Jun 1, 2013 at 11:29 AM, Wladimir 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 > > If not:

Re: [Bitcoin-development] Implementing batch processing for -blocknotify

2013-05-31 Thread Chris Double
On Fri, May 31, 2013 at 11:56 PM, Rune Kjær Svendsen 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 application subscrib

Re: [Bitcoin-development] Alternative to OP_EVAL

2011-12-30 Thread Chris Double
On Fri, Dec 30, 2011 at 5:42 AM, wrote: > Basically OP_DUP lets you duplicate the code on the stack and that is the > key to looping.  I'm pretty sure from here we get get Turing completeness. > Using the stack operations I expect you can implement the SK-calculus > given an OP_EVAL that allows a

Re: [Bitcoin-development] Transaction limit size in CWallet::CreateTransaction

2011-09-03 Thread Chris Double
On Sun, Sep 4, 2011 at 1:52 AM, Chris Double wrote: > So was the intent to use the CWalletTxn size, and the casting is > superfluous, or was it supposed to be the CTransaction* portion and > the cast is an incorrect way of doing that? Or am I suffering from > late night programmer

[Bitcoin-development] Transaction limit size in CWallet::CreateTransaction

2011-09-03 Thread Chris Double
In CWallet::CreateTransaction there is a call to 'GetSerializeSize' on line 979 (https://github.com/bitcoin/bitcoin/blob/master/src/wallet.cpp#L979). It looks like: -8<-- unsigned int nBytes = ::GetSerializeSize(*(CTransaction*)&wtxNew, SER_NETWORK) if (nBytes >= MAX_BLOCK_SIZE_GEN