Bitcoin Forum
February 29, 2024, 03:24:17 PM *
News: Latest Bitcoin Core release: 26.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Bitcoin / Development & Technical Discussion / Re: Understanding BIP 32: private derivation and public keys on: January 09, 2014, 08:18:00 PM
I don't know how to interpret M/i'.

I'd say its trying to mean the public key of m/i'.

Quote
One weakness that may not be immediately obvious, is that knowledge of the extended public key + a private key descending from it is equivalent to knowing the extended private key (i.e., every private and public key) in case public derivation is used. This means that extended public keys must be treated more carefully than regular public keys. This is the reason why accounts at the first level of the default wallet layout use private derivation, so a leak of account-specific (or below) private key never risks compromising the master.

It looks like its assuming that you are, by default, protecting the master private key by always making the first generation of children through private derivation.

Quote
2) If the primed lines cannot be derived from public keys, is it true that M alone cannot be used for complete auditing? If so, then every primed node has to share its public key with the auditor for access, and whoever holds M can never be sure that the holder of m didn't create hidden wallets

Yes.

Quote
Can it be that parts of the document are not in line with each other after some changes in the ideas/notes/text?

That's what it looks like to me.
2  Bitcoin / Development & Technical Discussion / Golang BIP 32 implementation on: January 06, 2014, 02:11:53 AM
I made a little BIP 32 implementation in Go. Hierarchical deterministic wallets, yay!

https://github.com/WeMeetAgain/go-hdwallet
documentation: http://godoc.org/github.com/WeMeetAgain/go-hdwallet

It tests against the BIP 32 page  test vectors (https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki#test-vectors) and passes. (I'm sure it could use more eyes on the code, though)

I used this as reference: https://github.com/vbuterin/pybitcointools/blob/master/pybitcointools/deterministic.py

Examples included in README!

Cheers!

Edit: changed repo name, added documentation link
3  Bitcoin / Project Development / Bitcoin Point-of-Sale Device - Will be at Bitcoin Conference on: May 11, 2013, 05:07:44 PM
Hey all,

I've built a simple point-of-sale device that facilitates bitcoin transactions. It consists of a numpad and character display for a 'cashier' and a small LCD display for the 'customer'. This device simply allows the cashier to enter a dollar amount on the keypad and have a QR code generated for the customer. The device will display a confirmation screen once it receives the unconfirmed transaction from the customer.

Here's a small demonstration: http://youtu.be/3uetgK0brgA

I figure something like this would be great for a small business to be able to use to easily, yet professionally accept bitcoin -- an all-in-one solution that can just be dropped next to a cash register and work. I have seen plenty of tablets being used as point-of-sale devices, but that involves pecking in the transaction total and awkwardly passing the tablet back and forth. This is just a stationary, dedicated unit.

My friend will be using one of these devices at the Bitcoin Conference next weekend!
Look out for BitcoinNotBombs.

Developy Stuff:
I put the code and build instruction on github: https://github.com/WeMeetAgain/btcpos
I'll keep upgrading this code in the future.
I've also included some security considerations in the README.

This box simply uses the blockchain.info API to handle bitcoin address generation(a new one for each transaction), listening for transactions, and sending bitcoins. No information is stored on the device except the information necessary to communicate with blockchain.info and the address to which to send the bitcoins.

Let me know what you guys think.
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!