Re: [bitcoin-dev] Hardfork to fix difficulty drop algorithm

> the network. This would result in a significantly longer block interval, > which > also means a higher per-block transaction volume, which could cause the block > size limit to legitimately be hit much sooner than expected. If this happens at all (the exchange rate of the coin can accomodate

Re: [bitcoin-dev] [BIP Draft] Datastream compression of Blocks and Transactions

> On 01 Dec 2015, at 06:28, Matt Corallo via bitcoin-dev > wrote: > > I'm really not a fan of this at all. To start with, adding a compression > library that is directly accessible to the network on financial software is a > really, really scary idea.

Re: [bitcoin-dev] [BIP Draft] Datastream compression of Blocks and Transactions

> On 02 Dec 2015, at 00:44, Simon Liu wrote: > > Hi Matt/Pavel, > > Why is it scary/undesirable? Thanks. Select your preferable compression library and google for it with +CVE. E.g. in zlib:

Re: [bitcoin-dev] Memory leaks?

> I just noticed that several of my running bitcoind processes were using > around 3+ GB of RAM, even though the mempool itself seemed to be under > control. > > @prime:~/bin$ ./bitcoin-cli getmempoolinfo > { > "size" : 1896, > "bytes" : 37341328 > } > > [total memory usage not

Re: [bitcoin-dev] On bitcoin-dev list admin and list noise

> On 29 Sep 2015, at 19:29, Mike Hearn via bitcoin-dev > wrote: > > There's a simple way to cut down on "noise" that doesn't involve people > shouting OFFTOPIC at each other: the maintainer needs to resolve discussions > by making decisions and saying,