On Sun, Jul 22, 2012 at 11:37 PM, grarpamp wrote:
> Given a testbed: Pentium 4 1.8GHz single core, 2GB ram, FreeBSD 8,
> disk is geli aes-128 + zfs sha-256, bitcoin 0.6.3, Tor proxy,
> An estimate is made that by the end of the year bitcoin will
> completely overrun the capabilities of this reason
On Mon, Feb 6, 2012 at 5:27 PM, Wladimir wrote:
> Change BitcoinAddressValidator::MaxAddressLength to 35
> The addresses are validated with walletmodel->validateAddress which in turn
> calls CBitcoinAddress addressParsed(addr) and then isValid(). Does this work
> for the new addresses?
Should do
On Fri, Feb 3, 2012 at 9:22 AM, Michael Grønager wrote:
> Hi Gavin, others?
>
> I am trying to redo the performance test of the libcoin client against the
> 0.5.2 Satoshi client, that I have learned also have received quite some
> improvements in speed since 0.4.0 (e.g. from not verifying signat
On Wed, Feb 1, 2012 at 4:15 PM, Luke-Jr wrote:
> On Wednesday, February 01, 2012 10:58:28 AM Michael Grønager wrote:
>> Your CMake cannot find boost - use ccmake or cmake-gui to help it with the
>> location.
>
> I didn't see anything useful in ccmake. Boost is in the standard locations
> (/usr/inc
On Wed, Sep 14, 2011 at 3:45 PM, Gavin Andresen wrote:
> Modify the getwork code to build on the second-from-tip block if the
> first-on-tip block is on the discouraged list.
>
> Assuming a majority of pools/miners adopt the "discourage blocks with
> stale timestamps" rule, that should squash any
5 matches
Mail list logo
