Re:BitPay introduces Bitcore
by jonpaul on Friday February 14, 2014 @05:43PM
(#7241556)
Shameless plug: https://github.com/cryptocoinjs (Bitcoin JavaScript fork of the original BitcoinJS) Right now, we're focused on Bitcoin, but we're moving fast and will be expanding support for altcoins. Also, if you're interested in the intricacies of addresses and Bitcoin, I'd encourage to read a very detailed article that I wrote on Bitcoin Addresses and JavaScript: http://procbits.com/2013/08/27/generating-a-bitcoin-address-... Doesn't use CryptoCoinJS yet as the article was written before I started CryptoCoinJS.
[ Parent
| on HN ]
Re:BitPay introduces Bitcore
by 1qaz2wsx3edc on Friday February 14, 2014 @07:32PM
(#7242035)
Honest question, how does this different from bitcore & node-bitcoin? https://github.com/freewil/node-bitcoin
node-bitcoin is just an interface to bitcoind, so you also need to run bitcoind. bitcoinjs, cryptocoinjs, (and now bitcore) are stand-alone javascript implementations which replace bitcoind.
Bitcore is designed to interface with bitcoind, so you're wrong [1]
It is designed to run server side on node.js or client side in a web browser
and interect with a trusted bitcoin node (i.e. a bitcoind instance)
Re:BitPay introduces Bitcore
by martindale on Friday February 14, 2014 @06:39PM
(#7241858)
Nice work! We'd love to share improvements, as we're largely focused on Bitcoin but want to make Bitcore as simple to use as possible.
Really the only difference between "altcoins" and Bitcoin is the version number in the address, often not even that. "Support" isn't so much needed as incidentally created. Minor fiddling with the POW (often breaking core functionality in the process) doesn't affect things like transaction creation and address validation.
Re:BitPay introduces Bitcore
by steveklabnik on Friday February 14, 2014 @07:16PM
(#7241994)
Depends. This is mostly true, but there's also things like Ripple, Mastercoin, and even Dogecoin that have reasonably significant differences from the other 'tweaked some parameters' altcoins.
Dogecoin has no significant changes. The coinbase value is detirministic, the POW is altered slightly and some other values are changed. Nothing interfacing with it needs alterations, other than things with validate blocks and so forth.
Re:BitPay introduces Bitcore
by steveklabnik on Saturday February 15, 2014 @02:07AM
(#7242992)
Doge has random block rewards (which is not UNIQUE but is different) and is an inflationary currency, with no cap.
Still just minor value changes, no effect on processing transactions.
Please support Dogecoin.
I was actually experimenting yesterday with cryptocoinjs on dogecoin. It works with very few changes, if you find and change a few options/constants among the various modules (mainly btc-p2p and p2p-node), eg by modifying the installed packages in your ~/node_modules directory. The port needs to be 22556, the DNS seed to seed.dogecoin.com, and the "magic bytes" to 0xC0C0C0C0.
There's an example of using getData on the transaction hashes inside "inv" (inventory) messages. it works, but you get hex public keys. So remember to use version bytes of 30 (decimal integer) to a base58check encoding function, to get the dogecoin addresses that begin with "D". Well, at least the output addresses are easy enough. I'm still having trouble parsing the input addresses.
[edit] here's the getData example: https://github.com/cryptocoinjs/btc-p2p/blob/master/examples...
Seconding this post, because votes are mostly anonymous and you can't see I upvoted his/her comment.
Re:BitPay introduces Bitcore
by arasmussen on Friday February 14, 2014 @06:06PM
(#7241672)
What do you mean votes are "mostly" anonymous?
Among other things, pg and anyone with physical access to the HN server should have the capability to determine which users voted on a given comment, since the server needs to store that so it knows to not let you vote twice.