Sending transactions to IP addresses should be removed or at least disabled by default. As has been stated by many members of the community, it is in no way secure. I also believe that it may actually allow an attacker to determine the identify of an operator of a bitcoin […]

So we have to choose something. May be Mantis? I don’t know anything about any of the bug trackers.  If we were to have one, we would have to make a thoroughly researched choice. We’re managing pretty well just using the forum.  I’m more likely to see bugs posted in […]

I’ve been playing around with visual studio (2010) trying to build bitcoin from the source that is included in the win32 zip archive. I created a new makefile project and imported the makefile, acquired the boost, wxwidgets, and the openssl sources, and a few other files which were reported missing […]

I have an unusual configuration: on my headless gateway there is bitcoind running and on my desktop standart bitcoin is running (both Linux OpenSuSE, gateway 11.1, desktop 11.3, bitcoin 0.3.12 both). TCP port 8333 forwarded on gateway to the desktop (so gateway client can’t has incoming connections). I don’t know […]

A thought has occurred to me that bitcoins client is released under mit which allows for closed source clients that would give someone an advantage over everyone by modifying the client and not releasing the code. If we changed to GPL this would force anyone who created a modified client […]

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 […]

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 […]

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: […]

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 […]

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 […]