Bitcoin Forum
October 19, 2018, 07:57:29 AM *
News: Make sure you are not using versions of Bitcoin Core other than 0.17.0 [Torrent], 0.16.3, 0.15.2, or 0.14.3. More info.
 
  Home Help Search Donate Login Register  
  Show Posts
Pages: [1]
1  Bitcoin / Development & Technical Discussion / Re: MoneyTree - a Ruby gem for creating HD Bitcoin Wallets on: January 03, 2014, 08:30:09 AM
Sorry for the late reply. OpenSSL will only work with Ruby 2.0.0 and greater. This is because the version of OpenSSL included with previous versions of Ruby did not include an OpenSSL::PKey::EC::Point#mul (point multiplication) method, which is required in order to calculate a Bitcoin public key from a private key.
2  Alternate cryptocurrencies / Marketplace (Altcoins) / Re: MasterCoin Buyer/Seller Thread on: October 16, 2013, 08:55:07 PM
Please remove my sell order of 100 mastercoins from the order book. They have been transferred. Thanks!
3  Bitcoin / Bitcoin Discussion / Re: Governments now own BTC on: October 13, 2013, 07:07:04 AM
Perhaps the US will just hold on to the BTC as a hedge against its own fiat currency going down the toilet. #irony
4  Bitcoin / Bitcoin Discussion / Serious Bitcoin bling on: October 12, 2013, 04:02:31 AM
Check out this 65BTC necklace



Some serious bling sported at the LA Bitcoin Meetup (http://www.meetup.com/Los-Angeles-Bitcoin/events/139996962/) last night.
5  Bitcoin / Meetups / Re: Los Angeles (SoCal) Bitcoiners Meetup? on: October 12, 2013, 03:38:31 AM
Good times last night!  Wow, what a turnout.  So many people, so many projects.
The night ended far too soon.

Since there may not be another LA meetup before Oct 31 (when the Satoshi Nakamoto Whitepaper 5th anniversary commemorative becomes no longer available) if you wanted to get one and missed me there, let me know soon and we will find a way.


Thanks for the beautiful silver coins. I picked up five last night, and can vouch that they are brilliant. Really nice design, and there's something about holding a weighty silver coin in your hand that's very gratifying.
6  Bitcoin / Meetups / Re: Meet the founders of BitPay, Gyft and CoinMKT in Los Angeles tonight! on: October 11, 2013, 12:56:52 AM
Darn! why such short notice ? I'll try to make this.

Nevermind, I see you posted this Oct. 1st! lol

Yeah, I edited the title of the post to make it more time relevant. =)
7  Bitcoin / Meetups / Re: Meet the founders of BitPay, Gyft and CoinMKT in Los Angeles tonight! on: October 10, 2013, 09:10:47 PM
This is a quick reminder about our big Bitcoin event happening tonight in Santa Monica. If you're in the LA area tonight come on out.

The event starts at 7pm, free food and drinks, and some awesome speakers who flew out just for this event.

For more details: http://www.meetup.com/Los-Angeles-Bitcoin/events/139996962/

See you tonight.

Wink
8  Bitcoin / Meetups / Re: Los Angeles (SoCal) Bitcoiners Meetup? on: October 10, 2013, 09:03:00 PM
Is there parking at Coloft?

There is usually ample street parking available in the area after 6pm, especially on Santa Monica Blvd. Please do not park in the back lot, it's reserved for the tenant upstairs. Also, watch out for any posted signs, the Santa Monica ticket patrol is fierce.

For more details about tonight's big Bitcoin event, check out the details at http://www.meetup.com/Los-Angeles-Bitcoin/events/139996962/
9  Bitcoin / Meetups / Meet the founders of BitPay, Gyft and CoinMKT in Los Angeles tonight! on: October 01, 2013, 06:02:29 PM
The Los Angeles Bitcoin meetup group is hosting a panel event on October 10 in Santa Monica, CA. If you're going to be in the LA area definitely drop by and meet our group.

Special guests include:
• Tony Gallippi (CEO and founder of BitPay - the largest Bitcoin merchant processor)
• Vinny Lingham (CEO and cofounder of Gyft - a mobile gift card company which just raised $5MM in Series A and gives Bitcoiners a way to spend their coins at major retailers)
• Travis Skweres (CEO and founder of CoinMKT.com - a recently launched Bitcoin exchange) 

Free food and drinks are graciously provided by BitPay.

For more details: http://www.meetup.com/Los-Angeles-Bitcoin/events/139996962/
10  Alternate cryptocurrencies / Marketplace (Altcoins) / Re: MasterCoin Buyer/Seller Thread on: September 18, 2013, 06:18:42 PM
Selling 100 MasterCoins @ 0.025 BTC each

http://mastercoin-explorer.com/addresses/1H5i3Pz9y1mYnXqXDAxJPohggwyBT98oc1
11  Bitcoin / Development & Technical Discussion / Re: MoneyTree - a Ruby gem for creating HD Bitcoin Wallets on: September 17, 2013, 07:42:02 PM
Not a ruby programmer myself, but just wanted to say thank you!
I appreciate that! There is an enormous community of developers/startups/infrastructure built around the Ruby ecosystem, and it would be great to migrate more of those developers over to the Bitcoin community.
12  Bitcoin / Development & Technical Discussion / MoneyTree - a Ruby gem for creating HD Bitcoin Wallets on: September 17, 2013, 07:02:03 PM
Money Tree

I've just released an open-source Ruby gem for creating Hierarchical Deterministic Bitcoin Wallets. This gem will allow you to generate or import a random seed and create an entire tree of Bitcoin keypairs derived from that seed. So you don't need to backup all of your keypairs, you just need to backup the seed.

This gem follows the spec at https://en.bitcoin.it/wiki/BIP_0032 and passes all test vectors provided there.

Let me know what you think!

You can check out the repo at https://github.com/wink/money-tree

Why would I want an HD Wallet?
Hierarchical Deterministic (HD) Bitcoin Wallets offer several advantages over traditional Bitcoin wallets.

One of the problems with traditional Bitcoin wallets is that the wallet may hold a whole bunch of keypairs, each with Bitcoins attached to them. When you want to back up your wallet, you backup all of the current keys that you control in that wallet. However, if you later generate a new key, you need to make a brand new back up of your wallet. In fact, you need to back up your wallet every time you generate a new key.

Easy backups

HD wallets allow you to create a huge number of Bitcoin keys (keypairs) that all derive from a parent master key. This means that if you control the master key, you can generate the entire tree of children keys. So instead of needing to make repeated backups of your wallet, you can create a single backup when you create the wallet, and from then on to the end of time, you will never need to make a new backup, because you can just recreate ALL of the child keys from your master key.

Safely store your private keys offline

Additionally, HD wallets introduce cool new features to wallets, like being able to derive the entire tree of public keys from a parent public key without needing ANY private keys. For instance, let's say you have your master private key backed up on a paper wallet and stored offline in a safe somewhere, but you have the master public key available. Using just this public key, you can generate an entire tree of receive-only child public keys.

For instance, let's say you wanted to open a Bitcoin ecommerce website. With HD wallets, you can keep your master private key offline, and only put your public key onto the public webserver. Your website can then use that key to generate a receiving address for each and every product on your site, a unique address for each one of your customers, or even a key unique to each customer/product combo. (The uses are left up to your imagination.) And since the private key is stored offline, nobody will ever be able to hack your site and steal your Bitcoins.

Access controls

One bonus feature of HD Wallets is that they give you a lot of control over who in your organization has access to which keys. Like an organizational chart for a business, HD wallets are arranged in a tree formation. You could create whole branches of keypairs for each department in your organization, and by giving each department only the private key at the top of their department branch, each department will only be able to spend the coins on their branch. However, since you hold the master key, you can watch and spend ALL coins in the entire tree.

Accounting

Want to give your accountant access to view all transactions, but you don't want to give her access to spend any of your coins? No problem. You can simply give her the public key at any level in the tree that you desire, and she will be able to view transactions below that key in the tree, but won't be able to spend any of the coins.
13  Bitcoin / Development & Technical Discussion / Re: BIP0032 HD Wallet private key derivation incorrect? on: September 04, 2013, 09:59:06 PM
I think that the (mod n) was added as an indication that this should happen, not as a mathematical notation. It's syntactically incorrect, which kind of gives it away.

Yes, I believe you're right. And in retrospect that makes total sense! Grin However, it's confusing given its placement right next to the equation. At any rate, it wouldn't hurt to make the documentation more clear in case any other developers are as unfamiliar with crypto concepts and byte management as I was. At least I learned a lot about bits/bytes/elliptic curves and everything else I tried in search of the answer.
14  Bitcoin / Development & Technical Discussion / BIP0032 HD Wallet private key derivation incorrect? on: September 04, 2013, 06:09:23 PM
I have been implementing the BIP0032 HD Wallet protocol, and ran into an issue in the documentation at https://en.bitcoin.it/wiki/BIP_0032 which slowed me down for an entire day. Here is the documentation on private child key derivation.

Private child key derivation
To define CKD((kpar, cpar), i) → (ki, ci):
Check whether the highest bit (0x80000000) of i is set:
If 1, private derivation is used: let I = HMAC-SHA512(Key = cpar, Data = 0x00 || kpar || i) [Note: The 0x00 pads the private key to make it 33 bytes long.]
If 0, public derivation is used: let I = HMAC-SHA512(Key = cpar, Data = χ(kpar*G) || i)
Split I = IL || IR into two 32-byte sequences, IL and IR.
ki = IL + kpar (mod n).
ci = IR.

It says you should add IL to kpar(mod n).
In pseudo code, this would be:
Code:
i_left + (kpar % n)

Adding these two values together should always create a new number that is 32 bytes long. However, for some values of IL and kpar(mod n), adding them together can create a number that is greater than 32 bytes long, and is therefore no longer a valid 256bit private key.

It appears the parenthesis are in the wrong place in the documentation. It should read:

ki = (IL + kpar) mod n.

or in pseudo code:
Code:
(i_left + kpar) % n

Changing the parenthesis finally made all of my test vectors pass. I'm posting this to hopefully save someone else a world of trouble. Can we change the documentation?
15  Other / Beginners & Help / Re: Bitcoin Businesses and Developers, Let's Get Started! on: July 19, 2013, 11:00:57 PM
Hi community,

I'm a Ruby/iOS/javascript developer looking to meet like minded developers and build bitcoin tools so easy to use, my grandmother could do it.

I'm currently awaiting delivery on my first two 5GH BFL miners and own a whopping 7 bitcoins.

Thank you for your hospitality,

Wink  Wink
Pages: [1]
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!