Btcd - a Bitcoind Alternative Written In Go!
An anonymous reader writes "The folks at Conformal have announced btcd, an alternative full-node implementation to bitcoind, written in Go! They have released the first of their core packages, btcwire, available for download at GitHub. As a bitcoin user myself, I love the idea of a full alternative. It will only make bitcoin stronger and more independent. This will be great for the Go community, too!"
...in world full of banking problems, banking crises and eroding trust in fiduciary money. Way to go !
Religous speak to God. Insane are spoken to by God. When all shut up, one can finally hear Shostakovich in peace
TFS mixes the two: written in Go! and great for the Go community
TFA says: it's Go not Go!
Questions raise, answers kill. Raise questions to stay alive.
What have you bought over the last year? How has their price varied in dollars and in bitcoins? No currency's value is constant, but some are a lot more constant than others.
All they have released is a handler for the network protocol. This doesn't verify blocks, send transactions or anything else. Are the other parts closed source or do they just not exist?
As Bitcoin alternatives go, I really liked the idea behind Namecoin. Not that it's likely to go anywhere, but it's something that puts some real backing, value, to the currency while simultaneously doing something to address the piss poor domain name allocation system that we have right now. Bitcoin is currently just floating on enthusiasm and greed, this would actually have some worth if people got behind it.
My 6 year old loves to doodle with his crayons. Lately, I've been having him draw money. So far, the good ones are really rare. So I figure they are probably worth a substantial amount of money. I'm going to start releasing them as currency soon. I'm also working out a deal with Paypal to accept them.
Bitcoins have gone from worthless in 2010 to $120 a coin in 2013
$120 is only today's price. It can go down.
“...the system is secure as long as the honest nodes collectively control more [computing] power than any cooperating group of attacker nodes.” - Satoshi Nakamoto, creator of Bitcoin.
ie. If governments or bot-herders want to destroy Bitcoin, they can.
In fact, if I was a bot herder I'd be busy working on a way to manipulate the price of bitcoin for fun and profit.
No sig today...
Please: observe that "Go!" and "Go" are two quite different programming languages.
The client appears to be written in "Go" which is the language by google, but the headline would suggest "Go!" by McKabe & Clark.
I find the same ambiguity in the text... still, I am looking forward to the time we shall use the full unicode range in order to have
similar looking, yet entirely different, names. That shall be fun!
Given the (currently tiny) market for goods buyable with bitcoins, their 'value' is heavily dependent on the health of the exchanges where you can cash out into some other currency.
Incidentally, those exchanges appear to get hacked and/or DDsSed every couple of months...
With the GPU, FPGA, and ASIC miners either online or coming-real-soon-now, bot-herding in order to outcompete honest nodes is a substantial computational challenge, CPU miners are just too pitiful; but it would seem that the real weakness to exploit is the (much softer) underbelly of conventional web infrastructure and the price swings that attacks on that part of the bitcoin economy can create.
The trade between bitcoins and USD looks sort of like the buying and selling of stock, in a world where it's totally normal for the NYSE to be firebombed multiple times per year...
Go and Go! are very different language, which one was it programmed in?
GO: http://en.wikipedia.org/wiki/Go_(programming_language)
GO!: http://en.wikipedia.org/wiki/Go!_(programming_language)
They chose a bad, confusing name: btcd
Imagine if bitcoins were instead called x-Koins. What would this project be called?
Your post is extremely interesting, but the mandatory conclusion I make from it is the exact opposite of yours. If the original code is so full of idiosyncracies and gotchas then it's an extreme liability to everyone who values Bitcoin, and quite likely contains backdoors or deliberate weaknesses that are hidden by the obscurity.
There can be no more important task for the Bitcoin community I think than to specify all elements of the static protocol and dynamic behavior of all parts, and reimplement them in other languages, especially safe languages.
Go is certainly a good candidate for this large body of work, safe, clean, and fast.