Update: 12/04/2012
Finished the BOM today. It can be viewed here:
https://www.dropbox.com/s/o8u356ubi61wzy6/BOM_0.1_LastUpdate_10_25_2012.pdf
The total COMPONENT price is $30.91 USD (note: price for components ordered individually).
I think I will be able to get the component price below $20.00 USD with samples and a larger order.
Instead of waiting to see who will order to get an idea of how many of these to build, I went ahead
and decided to build 50+. It will be a risk on my part and I will be putting all the money down.
Look what I discovered:
The first time the name "BitSafe" was used can be found here:
https://github.com/rb1205/BitSafe
Credits go to Riccardo Belloli for the name
Topic: BitSafe Hardware Wallet Development - page 2. (Read 11214 times)
Who Knows, when I'm done publishing all my design files to this thread, it may even help them.
Although we're using another platform, your choice for HRNG is quite interesting. We ordered some Atmel samples and we will do some tests with them. Unfortunatey Atmel is very unclear about *how* their HRNG works. I must say that bitcoin wallet requires much stronger HRNG source than any other common device and I'm concerned about the true randomness of it.
That's cool Slush. Please let me know how it goes.
Comparing apples and oranges here. Bitsafe is MIPS architecture, ours is ARM. MIPS binaries are approx 2x bigger than ARM ones.
Are you sure? Are you really comparing MIPS16 with Thumb?I've seen some numbers for an older project and the MIPS vs. MIPS16
and ARM vs. Thumb sizes were within about 10% of each other. Tests were made with commercial C compilers, not GCC though. Maybe some GCC oddity?
Yes, it is true. They are pretty close. Someone42 has even verified this.
Thanks
Comparing apples and oranges here. Bitsafe is MIPS architecture, ours is ARM. MIPS binaries are approx 2x bigger than ARM ones.
Are you sure? Are you really comparing MIPS16 with Thumb?I've seen some numbers for an older project and the MIPS vs. MIPS16
and ARM vs. Thumb sizes were within about 10% of each other. Tests were made with commercial C compilers, not GCC though. Maybe some GCC oddity?
Actually 512kB is far enough for this purpose. We're working on solution with 256kB of flash. And yes, BIP32 is a way to go for such small devices.
Comparing apples and oranges here. Bitsafe is MIPS architecture, ours is ARM. MIPS binaries are approx 2x bigger than ARM ones.
Who Knows, when I'm done publishing all my design files to this thread, it may even help them.
Although we're using another platform, your choice for HRNG is quite interesting. We ordered some Atmel samples and we will do some tests with them. Unfortunatey Atmel is very unclear about *how* their HRNG works. I must say that bitcoin wallet requires much stronger HRNG source than any other common device and I'm concerned about the true randomness of it.
Who is writing the software for this? 512 kB is probably smaller than the smallest MIPS program I can easily write (eg, standard C).
Actually 512kB is far enough for this purpose. We're working on solution with 256kB of flash. And yes, BIP32 is a way to go for such small devices.
Cool and good luck.
So I'm a bit confused, is this going to work similar to the piglet or what is the difference?
Overall, there's not Much Difference really. This has been in the works for a few months now.
The Piglet took me by surprise and I wasn't sure what to do.
I've decided to go full steam ahead. In the end, it can only help Bitcoin.
Who Knows, when I'm done publishing all my design files to this thread, it may even help them.
So I'm a bit confused, is this going to work similar to the piglet or what is the difference?
It has sufficient to store private keys and generate signatures. That's the important part.
Where will you store the private keys? The EEPROM says not there, and I presume the SoC flash is for code...For something like this, it really makes sense to use a HD wallet.
The EEPROM is an external chip. Not ideal for storing keys that are not encrypted. It's good for storing small chunks of data regarding addresses and transactions.
The Chip can self write to the Flash and is as good as EEPROM other than the write time is a little longer.
What's an HD Wallet?
Who is writing the software for this? 512 kB is probably smaller than the smallest MIPS program I can easily write (eg, standard C). A HD (hierarchial deterministic) wallet is easily the ideal design for a device like this where you only have space for a single private key. You can build multiple chains of basically unlimited addresses from just that one key. BIP 32 is the specification.
bitsafe ay.
I trademarked that name a few months back !!
well.. not really
I trademarked that name a few months back !!
bitsafe or bit-safe etc
well.. not really
Hi allten, please contact Unthinking concerning your Devcoin listing.
https://bitcointalksearch.org/topic/m.1357529
https://bitcointalksearch.org/topic/m.1357529
want
Any anticipated date this will be ready for public consumption?
It has sufficient to store private keys and generate signatures. That's the important part.
Where will you store the private keys? The EEPROM says not there, and I presume the SoC flash is for code...For something like this, it really makes sense to use a HD wallet.
The EEPROM is an external chip. Not ideal for storing keys that are not encrypted. It's good for storing small chunks of data regarding addresses and transactions.
The Chip can self write to the Flash and is as good as EEPROM other than the write time is a little longer.
What's an HD Wallet?
It's my understanding that the GPU and bootloader were opened. Besides, this device doesn't need to use a GPU.
I'm sorry, but this is disinformation. I repeat: GPU boots first, then it starts the CPU. The "open source" driver is just a lean thunk layer to call back the real supervisor that runs on the GPU's undocumented instruction set. GPU also does things like power management.Broadcom guys are very smart and very cynical. Turning upside down the central processor vs. peripheral processor architecture was a very smart, forward looking move.
Edit: Before anyone quotes the above: the term GPU is also a disinformation. The main processing unit in the Broadcom VideoCore architecture is a systolic array of relatively slow-clocked DSP processors. It works as a GPU when the DSP chips are executing graphic pipeline code. The secret architecture of the VideoCore processors was a serious drawback... unitil they came with a bright idea of tackling an ARM CPU running as an attached processor. This allows Broadcom to claim some sort of openness to bait the uninformed. It also allows them to markets using Android on ARM.
A Raspberry Pi is cheaper and far more powerful.
In Raspbery Pi a closed source GPU boots and controls the CPU. It is going to be a new frontier for hacking the gullible. Score for Broadcom.A Raspberry Pi is cheaper and far more powerful.
In Raspbery Pi a closed source GPU boots and controls the CPU. It is going to be a new frontier for hacking the gullible. Score for Broadcom. It has sufficient to store private keys and generate signatures. That's the important part.
Where will you store the private keys? The EEPROM says not there, and I presume the SoC flash is for code...For something like this, it really makes sense to use a HD wallet.
Jump to: