Topic: [ANN] BitSafe Hardware Wallet Now Shipping (Read 22152 times)

Still fabricating these Alten?

Dont associate yourselves with BFL at all if you want to keep your credibility

Inaba actually get your BFL products up and running and being sold to the masses who ordered before you offer any help or guidance to anyone else asshole

Bitsafe your product looks awesome

Hello all,

I just received the bitsafe device from alten. Fast shipping, device is working as expected. I got the basic test working with this firmware from alten https://www.dropbox.com/s/an5ej306snzbk51/bitsafe_tester.X.production.hex

With the first compilation I did (under ubuntu linux), the hex file failed to load properly with the PIC32 bootloader. I got the error message : "Verification failed". Alten then suggested I add a linker script called "app_32MX695F512H.ld" (it can be found in the bootloader source downloadable from Microchip). This linker
script will help the compiler to use the correct memory regions of the PIC32; otherwise, it will compile it to run in the same location where the bootloader resides in memory.

So I got my own bitsafe_tester firmware to work after that. Still trying to get the real firmware going.

I do not have a windows machine readily available, does anyone know of a good linux bootloader application?

Thanks!

Getting Started with Microchip's PIC32 IDE (MPLAB X)

If you want to develop, compile, or make small tweaks to the Bitsafe firmware,
you'll want to start by installing Microchip's latest IDE (MPLABX) They've made
considerably improvements over the last several months and it works really
good.

Download and install these two programs for your OS:
Windows:
       MPLABX: http://www.microchip.com/mplabx-ide-windows-installer
       X32C: http://www.microchip.com/mplabxc32windows
Linux:
       MPLABX: http://www.microchip.com/mplabx-ide-linux-installer
       X32C: http://www.microchip.com/mplabxc32linux
OSX:
       MPLABX: http://www.microchip.com/mplabx-ide-osx-installer
       X32C: http://www.microchip.com/mplabxc32osx

The 32 bit C compiler has 3 modes: Free, Standard, and Pro.
The Free edition will work just fine for our purposes. The binaries
will be slightly larger, but they work just the same.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Additional resources to learn about MPLABX

Main Page:
http://www.microchip.com/pagehandler/en-us/family/mplabx/

Great Intro:
http://ww1.microchip.com/downloads/en/Market_Communication/Getting_started_with_MPLAB-X.pdf

Wiki:
http://microchip.wikidot.com/mplab:_start

Forum:
http://www.microchip.com/forums/f238.aspx

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Opening Project

work n Progress

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Compiling Project and Downloading Firmware with the PICKIT3

work n Progress

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Compiling Project for the bootloader

work n Progress

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Finding the binaries for the bootloader

work n Progress

Open Source Hardware and Software Files (Bitsafe 1.0)

Note: The only difference between 1.0 and 1.1 is the later version has a 0.1uF
(100nF) capacitor soldered on top of R30 (750 Ohm resistor) to help provide a
more stable 4.05V source.

Firmware:
https://github.com/someone42/hardware-bitcoin-wallet
https://github.com/someone42/bitsafe-tester

Microchip's Bootloader:
http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1824&appnote=en554836
http://ww1.microchip.com/downloads/en/AppNotes/AN1388%20Source%20Code%202013_02_01.zip

There were edits made to Microchip's Bootloader for Bitsafe compatibility. Due to licensing,
it was felt that it would not be a good idea to publish their bootloader on Github until all
concerns are resolved.

Please email me if you would like a copy of the source with the Bitsafe edits.
_____________________________________________________________
Schematic:
https://www.dropbox.com/s/r0wlb2j80xwmmfd/Schematic.pdf

Schematic File - Requires Eagle CAD Tool:
https://www.dropbox.com/s/rab32936mwqe0ve/BitSafeDev.sch

Bill of Materials (BOM) - PDF Format:
https://www.dropbox.com/s/rclrxxhhhud5zwz/BOM.pdf

Bill of Materials (BOM) - Microsoft Excel Format:
https://www.dropbox.com/s/6czeygtv7i90ixk/BOM.xls

Top View of PCB Component Placement:
https://www.dropbox.com/s/bib6x9cicxtd212/Top.pdf

Bottom View of PCB Component Placement:
https://www.dropbox.com/s/khi322q14npnx9o/Bottom.pdf

PCB File - Requires Eagle CAD Tool:
https://www.dropbox.com/s/z2fy2shgx5kjn5p/BitSafeDev.brd

Fabrication Files:
https://www.dropbox.com/s/sfod6gk17ui1qvf/BitSafeDevA0_FabFiles.zip

It's ok, I'm happy to help out.

Thanks for the suggestions. I'll do that.
Did I mention developing hardware is my strong point and PR is my weak point 

The one of this thread would make the most sense if you ask me.  

Thanks, but which one? the getting started thread?

Would be smart if you update your OP with that

Loading and Updating The Firmware

As firmware rolls out the door followed by updates, it is important to know how
to get those upgrades onto the Bitsafe. Here is a step by step process on how
to do just that.

1) First, plug the Bitsafe into the computer while holding down one of the
buttons. It doesn't matter which one. The Bitsafe will start flashing the green
LED and it will enumerate with the OS in a few seconds. You should always be
able to enter Bootloader mode this way. If the LED is not flashing then unplug
the Bitsafe and try it again.

2) The Bitsafe uses Microchip's Bootloader. The source code is freely
available for download. Here is the link to the PIC 32 Bootloader AP note:
http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1824&appnote=en554836

Download the PIC32 Bootloader Zip file:
http://ww1.microchip.com/downloads/en/AppNotes/AN1388%20Source%20Code%202013_02_01.zip

3) Extract the zip file and run the compressed executable. This will simply
extract all the source files and bootloader program to the C:\ directory. The
default path is "C:\AN1388_Source_Code_2013_02_01"

4) Run the PC Software: PIC32UBL.exe Here's the default location:
C:\AN1388_Source_Code_2013_02_01\PIC32_Bootloaders\PC application\PIC32UBL.exe



5) Click on the Enable Check box in the USB section Leave the
Vendor ID (VID) and Product ID (PID) numbers at their default values
(VID=0x4D8; PID=0x03C). This VID belongs to Microchip and they have
designated PID 0x03C for their HID bootloader.

6) Click "Connect". For successful connection with the Bitsafe, make sure
it is plugged in and running the bootloader firmware (Green LED should be
blinking). See step #1.



7) Click "Load Hex File" then find and select the firmware binaries of
interest. Binaries will have .hex file extension. Make sure the Binary file was
compiled for this hardware and this Bootloader (currently version 1.0). If it is
not then programming verification will fail.

8: Click "Erase-Program-Verify":


If all went well, you can now unplug it and plug it back in (avoid pushing any
buttons) and it should work. The "Run Application" button on the software
may not work if the newly loaded firmware does not yet support it. Just
use the unplug method.

[Important Update - Please Read]
All the Bitmit listings regarding the Bitsafe and Bitsafe development are now live!
https://www.bitmit.net/en/q/?q=bitsafe

There was also some changes to the description of the main Bitsafe listing. (i.e. Disclaimer now included)
https://www.bitmit.net/en/item/20780-bitsafe-1-1-hardware-wallet-firmware-now-upgradeable-via-usb

Please review these changes and the new listings to make sure you are happy with your order.
Gladly refund anyone in a heartbeat if there is any issue. Also, check if any of the development
accessories are something you are interested in. It would be nice to ship them together.

As mentioned in the OP, I want to support anyone that would like to develop for this open source
project but don't feel like they have the extra funds to purchase a Bitsafe at full price.
Development support from others is of utmost importance for the success of Hardware Wallets
in general. I've included a Bitmit listing just for you. Please purchase this one, and pay what
you feel is appropriate. Hopefully, no one will find this as a barrier to getting involved if they are
serious about improving this project:
https://www.bitmit.net/en/item/20786-bitsafe-1-1-donors-and-developers-version

There has been no Bitsafes shipped out the door yet. Thanks for your patience. I would like to
give everyone a chance to review these new Bitmit listings first and make any changes if needed.
The plan is to ship in mass this next weekend. With a full time job and family, mass shipping will
help me make best use of the extra time I find for this project.

Lastly, I've now included my email in my profile. I dislike the PM system. If you tried to contact me
through Bitcointalk's PM system, but I haven't responded then please try my email. That is still
no guarantee I will reply in a timely matter, but eventually, it will happen.

Thanks,
     Allten

Hardware Design Public License Version 0.04

? Graham Seaman 2000 ([email protected])
Preamble

[meta]This license contains three parts: the license proper; comments, explaining the intent of the license proper, and separated from it by [comment]...[/comment], and meta-comments, which will be removed from the license once it has been completed. Meta-comments are separated by [meta]...[/meta]. All comments are in italics. [/meta]
[comment]This license is intended to achieve similar goals to those of the GPL (http://www.gnu.org/copyleft/gpl.html) in the context of hardware designs. It is not intended to achieve all the different goals those working on free hardware designs may have, some of which may require radically different licenses. However, it is intended to cover hardware designs of all types, including designs for PCBs, ICs, and Programmable Logic Devices. [/comment]

[meta] Trying to keep it this general has made the current version sound horribly long-winded. It is more of an exercise in finding out what the problems are in developing this kind of license, and what the goals should be, than a practical license, since there is no organization behind it. [/meta]

Any version of this license with version number greater than or equal to 1.0 may be copied and used verbatim. For versions before 1.0, the license may not be used; however, it may be copied, and meta-comments may be changed or added at will.

[meta]This license is incomplete, and has never been looked at by a lawyer. Maybe one day there will be a final valid version 1.0. In the mean time, you're welcome to use any useful ideas in it (as I have also borrowed ideas), just not to use the whole thing under this name. The main sources of the ideas (and parts of the text) in the license are:

Ian Carr de Avelon
Reinoud Lambert
And above all, the FSF
[/meta]
DEFINITIONS

"Manufacturing files" include any files which can be used as direct input to a process the purpose of which is to permanently change the electrical or electronic properties of an object. This includes, but is not limited to, gerber or other files for PCB manufacture; mask works for IC manufacture.
"Programming files" include any files which can be used as direct input to a process the purpose of which is to temporarily change the electrical or electronic properties of an object. This includes, but is not limited to, programmable logic device configuration data for FPGAs or PLDs; executable files for processors.
The "hardware design" (or simply "the Design") is the set of files associated with this license by being placed in the same directory as the license, or subdirectories of the directory containing the license, including but not limited to manufacturing files and programming files. Where these files have a textual format, they should contain a reference to this license (or in the case of software or documentation any license recognised by the Free Software Foundation as compatible with licenses issued by the Free Software Foundation).
[meta]This is the key to the whole license; it avoids the almost impossible to task of finding a completely general definition of a hardware design. Note that the legality of covering binary files with a copyright license is not settled, but that this has become current practice (eg. Xilinx uses this for FPGA bitstreams)[/meta]
A "readable" file must be in a format which can be read by software available to the general public, whether free or for a fee, with the exception that it must not be encrypted, obfuscated, or have its readability in any way artifically obstructed.
"Hardware Design Public License" (abbreviated to "HDPL") refers to this or later versions of this license.
Terms And Conditions

The HDPL covers all files included in the hardware design, except the license itself. You may not impose any further restrictions on use or distribution of the hardware design than those contained in the HDPL.
You may copy and distribute verbatim copies of the hardware design in any medium. You may charge a fee for the physical act of transferring a copy via a non-networked medium (such as a CDROM), and you may offer warranty protection, instructional support, or other services in exchange for a fee. You may not charge a fee for the sole purpose of providing access to the hardware design via a network.
[comment]"Verbatim" implies the inclusion of ALL files making up the hardware design, including the license file itself.[/comment]
You may freely modify this hardware design (with the exception of the HDPL file itself), thus forming a work based on the hardware design, and copy and distribute such modifications under the terms of section 2 above, provided that you also meet all these conditions:
You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.
You must in no way alter any copyright or mask work right symbols and information contained in the design
You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the hardware design or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this license
You must ensure that all files in the modified design are readable in the sense defined above.
[comment]Clause 3.3 implies that you may not include in your modification any work covered by patent or other rights which would invalidate this license[/comment]
[meta]Clause 3.4 is not in the spirit of the gpl. It would be desirable, but not practical to insist that only free software formats can be used. As it is, this clause leaves it open to a company to use a proprietary and secret format only usable by in-house software, and then to offer that software for sale at a ridiculous price, in order to satisfy the letter of this clause. This clause may change in future versions.[/meta]
The requirements of section 3 apply to the modified work as a whole. If identifiable sections of that work are not derived from the hardware design, and can reasonably be considered independent and separate works in themselves, then this license, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on this hardware design, the distribution of the whole must be on the terms of this license, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.
[comment]For example, say the design is a System-On-Chip computer. A person who adds a UART to this system may distribute the UART design separately under a different license. But if that person wishes to distribute the SOC computer design with the inclusion of the UART, the UART design must fall under the original license[/comment]
You may copy and distribute the manufacturing and programming files contained within the hardware design (or a work based on it, under sections 3,4) separately from the remainder of the hardware design, provided that you also do one of the following:
Accompany them with a prominently displayed URL for a network site available to the general public for a period of at least 3 years and with no access restrictions from which the complete hardware design (or the work based on it, as appropriate) may be downloaded in readable form.
Accompany them with the information you received as to the offer to distribute the corresponding complete hardware design (this alternative is allowed only if you received the manufacturing and programming files with such an offer, and have not subsequently modified these files).
[comment]This section has 4 principal purposes:

To apply similar conditions to those of the gpl to any software included in the hardware design
To apply similar conditions to those of the gpl to any programming information such as fpga bitstreams included in the design
To prevent users under section 6 from taking the design and modifying it by adding secret interfaces so that the manufactured design becomes effectively unusable.
To enforce the availability of documentation for any manufactured version of the design, via the following clause.
[/comment]
You may use manufacturing files contained in the hardware design for the purpose for which they were intended as defined above (definition 1).
For the purposes of this license, such use is to be considered as a form of distribution of the manufacturing files, and hence falls under section 5, with the same requirements.
[meta]The remainder of this license is copied almost word for word from the GPL. It is likely that extra clauses will have to be added to deal with potential patent violations and lack of implied warranty[/meta]

You may not copy, modify, sublicense, or distribute the Design except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Design is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the design or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the hardware design (or any work based on the Design), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the design or works based on it.
Each time you redistribute the Design (or any work based on the Design), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Design subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.
If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the design at all. For example, if a patent license would not permit royalty-free redistribution of the design by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Design.
If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free hardware design distribution system, which is implemented by public license practices. Many people have made generous contributions to the growing range of hardware designs distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute a design through any other system and a licensee cannot impose that choice.

This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.

If the distribution and/or use of the Design is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Design under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.
Each version of the HDPL is given a distinguishing version number. If the Design specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version.
If you wish to incorporate parts of the Design into other free designs whose distribution conditions are different, you may write to the author to ask for permission.hello

Thanks for the interest and enthusiasm.
I really don't know squat about licensing.
The way I view open source projects or community projects: when you see something lacking or something that needs to be done then that is your call to make it happen.
Are you up to it? That is, take care of all the licensing?

Between Family and work, like many here, I can only do so much. Hopefully, I can help foster an atmosphere where people feel welcome to jump right in and be part of this
in anyway they feel useful. No permission needed. I hope I'm not perceived as the owner of this initiative;
I'm just the guy who was passionate enough to dump a couple thousand (wife wasn't too happy) to make some prototypes after I saw the proof of concept and all the work
Someone42 had done.

Today, I received two messages from two different people that are taking the initiative to build a case for this first version. With a 3D printer, I believe.
That was great news!

This has encouraged me to start and manage some bounties. I would like to start with these two: one for case or enclosure and another for the licensing to be taken care of.

Open Source Licensing Bounty: 1DVXwuBuR4qLyW7axAq8tuTxPnTiGyvk5P
Case/enclosure Bounty: 1Jj3RkgLydBef2jpUrAUDxDYf1A5wvLsU

What amazes me about your add is that you took the time to get the LED colors correct. To my knowledge, no photos have been posted with the LEDs on.

For reference:
https://bitcointalksearch.org/topic/m.1621501

The device doesn't store blocks, block headers, or any transaction data. This makes it somewhat difficult to use in a POS situation. It's still possible: there is a "get master public key" command which allows the POS terminal to derive every address in a wallet. From there, the POS terminal can scan the blockchain and build a transaction. This is a lot of legwork for the POS terminal. Another disadvantage is that the user sacrifices privacy, since the POS terminal knows every address in the wallet.

A description of the wire protocol can be found at https://github.com/someone42/hardware-bitcoin-wallet/blob/master/PROTOCOL. I'm trying to make it like the one described here: https://bitcointalksearch.org/topic/hardware-wallet-wire-protocol-125383.

You would need to have the correct encryption key in order to initiate a backup, but once you do, the paper backup can be encrypted or unencrypted. Encrypted paper backups can buy you time if the paper is compromised, whereas unencrypted paper backups protect you against you forgetting the wallet passphrase .

I was going to have one encrusted in gold and gems with a USB cable disguised as a gold rope chain, but I didn't have the money. ;-)

SOON.

https://i.imgur.com/XYktA8R.jpg

This is a wonderful idea. I've wanted something like this for a long time.

Does the device store transaction data, or does it just look at transactions given to it by the PC to determine how many bitcoins the transaction is sending?

Kudos for someone42 for this post. This is exactly what I was coming onto this thread to write.

Especially the part where he says, "[then] a light flashes on the BitSafe and "Send 1.815 BTC to www.bitmit.net?" appears on the OLED display."

This is exactly what I need for Open-Transactions.

We have now gotten OT to where it installs on 64bit Linux through apt-get (using custom repo).

What do I need to make happen, in order to test OT on your device? Is there any comparable hardware I can buy now at home, which I can use to simulate running OT on your device? (So I can prepare OT to run on your device...)

This project is very interesting and important, especially the open-source aspect of it. May I recommend also that you choose an open-source license with patent protections built in so that your work doesn't later become subject to patent trolling. That will impact companies who try to use your hardware designs.

I am available [email protected] for any discussion. Great work!