[…] An interesting feature is that this simplifies the validation process. All that needs to be done is to parse the block list (of hashes) once. As each hash is parsed you simply look it up in a hash-set. If it doesn’t exist you add it. If it does exist […]

Building r127 here, we see some missing casts, apparently: Code: rpc.cpp: In function ‘json_spirit::Value gethashespersec(const json_spirit::Array&, bool)’: rpc.cpp:340: error: conversion from ‘int64’ to ‘json_spirit::Value’ is ambiguous json/json_spirit_value.h:283: note: candidates are: json_spirit::Value_impl<Config>::Value_impl(double) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >] json/json_spirit_value.h:275: note:                 json_spirit::Value_impl<Config>::Value_impl(uint64_t) […]

Quote from: jgarzik on August 10, 2010, 18:53:57 Ask some real-world business owners if they want to tell their customers about the chance of the money being lost forever, unrecoverable by either party. That makes it sound like it might somehow get lost and the parties can’t get it even […]

As some might have noticed, one of the things that bugs me about bitcoin is that the entire history of transactions is completely public. I totally understand the benefits of how this simplifies things and makes it easy for everyone to prove coins are valid. So this is not a […]

That’s a good point, I believe you could run with generation off if you don’t have SSE2. How about add to the top of cryptopp/config.h: #if !defined(_M_X64) && !defined(__x86_64__) #define CRYPTOPP_DISABLE_SSE2  1 #endif that would disable SSE2 for 32-bit builds.  (at least with GCC or MSVC) SVN rev 128: disable […]

Thanks very much for your reply. I agree with your analysis, and this thread has actually changed my mind as to my initial criticism. After more careful study of the design of the Bitcoin network and trying to understand the exact manner in which Bitcoin attempts to create value from […]

SVN rev 125: – Always make 8 outbound connections even if have 8 inbound – Limit outbound connections to one per a.b.?.? range – Switch -maxconnections=# I added the (currently undocumented) switch -maxconnections=#.  You shouldn’t use it unless you need to because your router can’t maintain a lot of connections, […]

The difficulty has gotten high enough that I wouldn’t worry about dropping block generation support for old computers if it’s hard to maintain compatibility. But the client should definitely provide some feedback explaining why the feature isn’t available. Perhaps you could make a message pop up that explains why generating […]

After testing the 32bit and 64bit builds, the problem I can confirm what was already posted here, it just affects the 64bit builds. When I go back and trace what’s being produced, it’s the 64bit Linux machines (the 64bit windows machines don’t appear to have this problem) that aren’t producing […]

As far as I can read C++, Bitcoin implementation stores timestamps as unsigned integers and block timestamp is a part of binary block format, of which a hash is computed. Since blocks are chained and the previous block is referenced in the current by it’s hash, you cannot simply recompile […]