Gold is recently at new highs for the Euro, Argentine Peso, Brazilian Real, Swiss Franc, Indonesian Rupiah, Indian Rupee, Pakistan Rupees and South African Rand. You'll see new highs in US dollars, Great British Pounds, Japanese Yen and others reasonably soon.

The price of gold has just reached $1,000,000 an ounce...



yes that's right, I'm selling an ounce of gold for one million dollars... any takers?

Thanks for the vote.

Well done to OpenTransactions which might not specifically be a bitcoin project but compliments bitcoin nicely.

I think my project is a bit too early to prove itself yet. When I get my full block-chain downloader/validator working I think it will create much more interest.

Alpha 3 is released. In this release the CBAddressManager test is fixed for new version numbers, the README has been improved, an old copyright notice has been removed since it is not needed and a problem with the script interpreter was fixed.

I just need to say that you are thinking of the world wide web.  Technically bitcoin is part of the internet so therefore the internet as a whole has to me more powerful.

I'm looking forward to the announcement on the 30th of September 23:59

Python is reeeeaaaaallllly sloooooooow on OSX for some reason. It's not so bad on Linux or Windows as I've experienced. Maybe it's just my Mac.

Possibly on embedded systems if you can get dynamic allocation to work and implement some of the standard library.

C is one of the most popular languages out there and I like coding with C which is why I'm using it.

I'm beginning to feel sorry for that poor chap who develops cbitcoin at only 10% in last place. 

Thanks, I'm sure those random digits will come in handy. 

I've got some code up for the fully validating node software: https://github.com/MatthewLM/BitEagle-FullNode

Hopefully that will come along smoothly.

Thank you very much for the donation.


I cannot say I'll be able to satisfy every need and complaint but I am all ears to suggestions and comments about bitcoin.

1.0 Alpha 2 is now available for download: http://cbitcoin.com.

I removed some include directives that should not be there. I fixed some warnings by changing the services bitfield to CBVersionServices and fixed the error handling in the CBNetworkCommunicator code. See commits here: https://github.com/MatthewLM/cbitcoin/commits/alpha

Well I have an updated description: https://github.com/MatthewLM/cbitcoin/

cbitcoin is a bitcoin library written in standard C99. It is currently in alpha-stage and should only be used experimentally. The purpose of the library is to make it easier for developers to create bitcoin applications and the library should be versatile enough to be used in many bitcoin projects. It is not a client library, rather it provides the basic building blocks of the bitcoin protocol.

The features includes:

Bitcoin message structures including serailisation and deserialisation functions.
A bitcoin script interpreter.
Functions for building and verifying merkle trees.
Basic functions which can be used in various validation models (full nodes, pruning nodes, SPV nodes or whatever).
Asynchronous networking code whcih provides a simple interface to the bitcoin network for sending and receiving messages.
A network address manager
Automatic bitcoin handshakes.
Automatic peer discovery.
Automatic pings.
Base-58 bitcoin address encoding.
Simple reference counting memory management.
Doxygen documentation and well-documented source code.
Purely standard C99 with weakly linked function prototypes for cryptography, PRNG and network dependencies.
Implementations of the dependencies using libevent and openssl.

Thanks to both of you.

I'm working on the full validating node software now. Somewhat soon I should commit some code to https://github.com/MatthewLM/BitEagle-FullNode This should aid with the testing of cbitcoin as I code the components for BitEagle.

Thank you.


The build script compiles shared/dynamic libraries for Linux and OSX. There is no Windows support yet. You can build or use the source code any way you want of-course.


Though cbitcoin will likely not be windows friendly. It would be good for any Windows developers to see if they can get it to work in Windows. I understand that the Windows C compiler doesn't support C99 so that will be a problem, though the code can be modified for C89 to compile for Windows or some other compiler can be used if it exists.

BitEagle will be an alternative client. If people want to use it in place of bitcoind (There should be a library and daemon interface) they can, but if they want to keep bitcoind then that's up to them. So "displace" isn't the word.

Thanks. Contributions are very much welcome. Look out for "" in comments. I put "" wherever I'm unsure about something or I think something could be improved. Be wary of the documentation which is incomplete and wrong is areas (Contributions to improved documentation would be helpful).

BitEagle will use SPV combined with a server-side full node. The server is there to behave as a trusted node to protect against attacks against your internet connection. Unlike some people have misbelieved this does not mean the security depends on the server because the client software will still do SPV validation on the bitcoin network. I will release the server-side full validation code as open-source so someone could make a fully validating client with it. With BitEagle I'm aiming to provide an intelligent mixture of security and convenience. More details will follow at a later date since it's still quite conceptual at this stage.


Thank you very much for the donation. And I hope to ensure that this is a worthy project. ;-)


Thank you!

I did take many of the script tests from the C++ bitcoin client and I should look at the other tests to add to mine, though sometimes it complicated trying to copy from C++ client.  


Still got a lot to do, especially with BitEagle but I'll get through it all... eventually. I've got some exciting stuff planned.