Gavin is the one doing lobbying on big businesses, including miners. I have not heard that Blockstream have been doing any lobbying so far, but hopefully they will soon to bring some balance to the lobbying done by Gavin, Mike & co.

Anyone have any feedback for me on buying digital goods (games from gog.com) using brawker.com? Can someone order and pay for a game and have it sent to my email address for download?

Scott Adams, the man behind Dilbert, has released a partial Dilbert strip on his blog with the last panel missing, which will be published 2nd April.

http://www.dilbert.com/blog/entry/who_didnt_see_this_coming/

Anyone care to venture a guess on the what the last panel will include?

By the way, Scott calls Bitcoin for a magical form of money.... At least he can still make me laugh with his Dilbert strips.

Sometimes the easiest solution is the best  I completely agree.

Even if an attacker has access to my life I want to make it as difficult for them as possible. You have a lot of nifty solutions for paranoid users and I thought this would be a good complement.

In the meantime I suggest that users who want a little bit of extra security when it comes to the SecurePrint feature, to only write the code down on as many fragments as it is necessary, i.e. N - M + 1 fragments. For example in a 5-of-6 fragmented backup configuration you only need to put down the SecurePrint code on 2 (=6-5+1) fragments and then put these fragments in the locations you deem most secure.

Hi Rick, read about your problems with MtGox. Glad to see high-profile users such as yourself moving to more secure solutions for storing your coins. Hopefully you didn't have too many coins at gox.

Thought I would mention: in case you don't have an old computer and still want to run a cold wallet, a cheap solution would be to get yourself a raspberry pi and follow my guide at https://bitcointalk.org/index.php?topic=443173.0

In my opinion having to share the SecurePrint code among all fragments in an M-of-N fragmented backup scenario, is a security flaw. If an adversary manages to get access to all the fragments without the SecurePrint code (e.g by MITM the printer) he will only have to get a hold of one of the fragments to be able to get the SecurePrint code and restore the wallet.

I don't consider this to be a critical security flaw, but still something worth considering and maybe fixing for a future release.

Guide for getting the latest version of Armory running on the RPi: https://bitcointalk.org/index.php?topic=443173.0

I have finally managed to get the Raspberry Pi, with Arch Linux as the OS, and the latest version of Armory (0.90-beta) to work. I thought I would share the process of setting this up as the other guides I've seen didn't work for me (Raspbian or older version of Armory, and I definately want to do fragmented backups on my offline wallet! ).

Note that none of the files I provide for download are necessary for getting this to work. You only need the patches and they are just text files you can assess for yourself. The other files are just to make it easier for some of you.

1. First get yourself a cross compiler. A guide for setting one up can be found at https://bitcointalk.org/index.php?topic=156003.msg1691384#msg1691384

2. Download this file http://www9.zippyshare.com/v/58820498/file.html. It includes the static library libpython2.7.a and the directory /usr/include/python2.7 from the RPi.
 a. You can download the source code for python2.7 and compile it on your RPi and extract the necessary files yourselves. I found that installing python2 via pacman (Arch package manager) didn't provide me with libpython2.7.a.
 b. The directory /usr/include/python2.7 can be found on the RPi by installing python2 via pacman.

3. Create two subdirectories under your home directory:
and decompress and move libpython2.7.a to the lib directory and python2.7 to the include directory.

4. Get Armory:

5. Download this file, http://www30.zippyshare.com/v/67984125/file.html. It includes patches that will be used on some of the Makefiles and ArmoryQT.py and armoryengine.py.

6. Uncompress and move the patches to the BitcoinArmory directory and apply them.

7. Now everything should work. run:

8.Create a directory for the RPi Armory version and move the necessary files to it and compress that directory.
Now you have Armory compiled and ready to run on RPi with Arch Linux. First though, Arch must be setup properly. To get the necessary packages I found it easiest to use pacman and then save the downloaded packages to a USB stick for later installation on the offline system.

9. I have been using ArchLinuxARM-2014.01-rpi.img which can be downloaded from archlinuxarm.org/platforms/armv6/raspberry-pi. Install instructions are found there as well.

10. Some packages are necessary to get Armory up and running. Make sure you have an Internet connection and run
You may also download any additional packages you feel you may need on your offline wallet.

11. Download jsonrpc-1.2.tar.gz from https://pypi.python.org/pypi/jsonrpc/1.2 and
 a. Extract it
  b. Enter the decompressed directory and build it
  c. Install it
 
12. Try the system out so that everything works as expected.
 
13. Go to /var/cache/pacman/pkg and move all .xz files to a USB stick.

14. Reinstall Arch Linux on the SD-card. When running it this time around make sure it is completely offline.

15. Move the packages and armory-pi.tar.bz2 to the freshly installed system.

16. Install the packages on the system

17. Extract Armory

18. Start the desktop environment and run armory.

19. Done!

The one functionality I didn't get working was message signing. The problematic line is #43 in ArmoryQT.py. If anyone finds a solution, please post it here.

Some tips:

• Use an SD card of class 10. I used class 4 first and it was a pain.
• Try overclocking the RPi to get better performance. https://wiki.archlinux.org/index.php
  /Raspberry_Pi#Overclocking.2FUnderclocking
• Resize the SD card to get more space (Could be a good idea while installing all packages). A default installation only gives you 2GB, no matter what the size your card is. http://archlinuxarm.org/forum/viewtopic.php?f=31&t=3119&sid=aab76b8acc31aa97d2a82cca1188cd22&start=20#p33507
• Dont forget to install printer drivers and cups to be able to do paper backups.

Some tips for the paranoid user:

• Install truecrypt
• • Skip resizing the sd-card and use the free space to create an encrypted volume using truecrypt (if you wear a tinfoil hat, create a hidden truecrypt volume http://www.truecrypt.org/docs/hidden-volume#Y0)
  • Start Armory
  • Create an offline wallet as normal, to be given up if you are forced to one way or another. Fund it with an insignificant amount of coins.
  • Close Armory
  • Mount the (hidden) encrypted volume on $HOME/.armory
  • Start Armory
  • Create your true offline wallet now
  • Back-it-up!
• Dont use a printer with Internet connectivity in general and wireless in particular

Hope this guide is clear enough for everyone and that it works without problems. If you dont want to deal with cross compiling you can download a prepared version of Armory for RPi here. http://www49.zippyshare.com/v/20048910/file.html

A long weeks hard work has paid off! I think I deserve a nice cold beer this weekend. Wanna buy me one? My local bartender charges me 0.015BTC for a beer , 18cyBjhkBdD45amH3oW5yuFRYsm82QTSvi