DB_PRIVATE enables a few optimizations by making the assumption that only one process will access the db4 database. Notably, this flag enables db4 to use pthreads-style mutex locking rather than heavy, operating-system-provided flock and shared memory. Ref: DB_ENV->open documentation. The general motivation is that db4 databases can be safely accessed […]
Read moreMonth: September 2010
Re: Running on a port other than 8333
Quote from: lachesis on August 10, 2010, 15:24:55 Also, does Bitcoin open the BerkeleyDB as exclusive, precluding the need for a file lock?It does not — did my own tests. Is there a way to open BerkeleyDB exclusive? DB_PRIVATE is the worst of both worlds. DB_PRIVATE is not exclusive, but […]
Read moreRe: Auto-detect for 128-bit 4-way SSE2
Quote from: teknohog on September 09, 2010, 19:32:05 Since the function CallCPUID function contains x86 assembler, it breaks the build on other architectures. I’ve changed line 2770 in main.cpp to #if defined(__GNUC__) && defined(CRYPTOPP_X86_ASM_AVAILABLE) to make it compile again, at least on ARM. Added in SVN rev 152 Related posts: […]
Read moreRe: Won’t let me send coins because it requires a transaction fee?
I think I know what happened. Doubleclick on the generated transaction. It probably has a sub-0.01 transaction fee in it. Someone has been paying a 0.00000010 transaction fee. I don’t think you can even set that with -paytxfee, I think you’d have to modify the code to do it. Your […]
Read moreRe: Won’t let me send coins because it requires a transaction fee?
If you send your entire balance, then you won’t have enough left to pay any fee. You could send 49.99. […] I think I know what happened. Doubleclick on the generated transaction. It probably has a sub-0.01 transaction fee in it. Someone has been paying a 0.00000010 transaction fee. I […]
Read moreRe: Won’t let me send coins because it requires a transaction fee?
If you send your entire balance, then you won’t have enough left to pay any fee. You could send 49.99. I don’t know why that’s happening. There shouldn’t be a fee for any non-combined transaction. What version is the one where this happened? Release build, or built it yourself? Which […]
Read moreAuto-detect for 128-bit 4-way SSE2
SVN rev 150 has some code to try to auto-detect whether to use 4-way SSE2. We need this because it’s only faster on certain newer CPUs that have 128-bit SSE2 and not ones with 64-bit SSE2. It uses the CPUID instruction to get the CPU brand, family, model number and […]
Read moreRe: Bitcoin Blogger: Is It Better To Buy Or Generate Bitcoins?
Quote from: BitLex on September 07, 2010, 20:10:54 AMD X3 @2.8ghz ->stock client ~3800khs ~150Watt Did you try -4way? Quote How many hashes can I expect with a 24 core machine? I have a quad-core generating 4,300 hashes-per-second, so I am estimating a 24-core machine could mine bitcoins at 25,000 […]
Read moreRe: Version 0.3.12
What does the prohibition of “nonstandard” transactions do? Code: main.cpp:506 // Rather not work on nonstandard transactions if (GetSigOpCount() > 2 || ::GetSerializeSize(*this, SER_NETWORK) < 100) return error(“AcceptToMemoryPool() : nonstandard transaction”); What is included in “GetSigOpCount”, and what does “GetSerializeSize” measure? This is “lightly” enforced by the network: Code: main.cpp:1425 […]
Read moreRe: Always pay transaction fee?
What is the current threshold, and how does a client know to pay for this in advance? Currently, paying a fee is controlled manually with the -paytxfee switch. It would be very easy to make the software automatically check the size of recent blocks to see if it should pay […]
Read more