.

[jim618]

The Model B 512 MB version.

Pretty decent spec I think. You can squeeze quite a lot into that. (a basic MultiBit uses around 100 MB so plenty of headroom).

[1714109582]

1714109582

[mila]

lucky you. enjoy.
i'd like more memory, simply because more memory kicks ass. i'm afraid the ofic client won't run on rpi (my guess, not even tried yet)

I'd love to see on the raspberry thing
1) the ofic client (to relay network data and maintain connections to other nodes in the network)
2) whole bunch of alt clients, especially the light ones, to be able to deal with btc from raspberry pi
3) mining/getwork service for fpga miners
4) p2pool node maybe

[gmaxwell]

If you're looking for a cheap sbc to play around with I'd strongly suggesting going for something like a http://armdevices.net/2012/07/12/129-exynos4412-quad-core-arm-cortex-a9-development-board/  or a pandaboard instead.

The rpi is astonishingly slow compared to more modern arm systems far more so than just the clock speed suggests.

[mila]

The rpi is astonishingly slow ...

it's good enough to run screen, samba, web server with little traffic
i was wondering if it can also run some bitcoin related apps.
but even response times for trivial tasks observed in shell take quite some time, i did not dare to start programs that would need more then ~200 mb of memory and then all cpu for swapping. a more powerful hardware might be the way to go. thanks for the link.
however it should be low power consumption pc but with some more computing power.
i like my raspberry pi very much but i could use also a dev board 'with muscles' the final price (with cables & co) is 4-5 times the price of the raspberry pi though. sorry for off topic post

[FLHippy]

The rpi is astonishingly slow ...

it's good enough to run screen, samba, web server with little traffic
i was wondering if it can also run some bitcoin related apps.
but even response times for trivial tasks observed in shell take quite some time, i did not dare to start programs that would need more then ~200 mb of memory and then all cpu for swapping. a more powerful hardware might be the way to go. thanks for the link.
however it should be low power consumption pc but with some more computing power.
i like my raspberry pi very much but i could use also a dev board 'with muscles' the final price (with cables & co) is 4-5 times the price of the raspberry pi though. sorry for off topic post

I haven't had any problem running lots of bitcoin related apps on the rpi. apache runs fine. php, vanitygen, all run fine. print server, gui desktop, all work fine and I don't have the 512MB model. You're going to wait for a lot of stuff to happen but it's to be expected. the RPI is a wonderful online or offline bitcoin tool. Are there better ones? Probably but not for the price... $35 goes a LONG way with the rpi.

[Fcx35x10]

I'm also currently waiting to order the new 512mb rpi 

[aneutronic]

If you're looking for a cheap sbc to play around with I'd strongly suggesting going for something like a http://armdevices.net/2012/07/12/129-exynos4412-quad-core-arm-cortex-a9-development-board/  or a pandaboard instead.

The rpi is astonishingly slow compared to more modern arm systems far more so than just the clock speed suggests.

Not really a fair comparison considering price but this is awesome.

Thanks for the link.

[Deafboy]

I got my Pi yesterday. 2 months since I ordered.
However, I'm thinking of getting this http://cubieboard.org/ instead of 2nd rPi.
More powerfull, incl. SATA port.

[Icoin]

DVB presents: Bitcoin-qt@rpi.


http://92.105.105.155/rpibtc/bitcoin-qt


The building process for bitcoin-qt is the same as for devcoin-qt:
https://bitcointalk.org/index.php?topic=101559.msg1308072#msg1308072

RPI BTC Address:
16qDGUUhyF2ttEbu2NXCUd4b8xQGYGz7pV

[The 4ner]

Let me know when one of you built a vending machine or something cool.

On an off-topic thought. Could this run a PirateBox?

Yupp: http://piratebox.aod-rpg.de/dokuwiki/doku.php?id=raspberry

[Stephen Gornick]

Incidentally, there are now similar gadgets used for offline hardware wallets:

Piper - A hardware-based paper wallet printer and so much more
 - http://bitcointalk.org/index.php?topic=194635.0

New Version of my Offline Paper Wallet Generator
 - http://bitcointalk.org/index.php?topic=202133.0

And continued interest in this topic:

Raspberry Pi as an offline wallet?
 - http://www.reddit.com/r/Bitcoin/comments/1glxfw

[The 4ner]

I recently bought my RPi recently and am awaiting it's arrival. Using it to cold store my coins is exactly what I had in mind for them. Because the RPi has only been on the market for such a short period of time I think it's safe to say that the RPi can be considered a safe place to store bitcoin.

[knowitnothing]

Hey there, this is pretty cool. I'm using a Raspberry Pi as a cold storage for a service of mine (mostly in test mode for now).

For those interested in cross-compiling for the rPi, but that still do not have a working crosstool-ng, I recommend first following the steps at https://trac.ffmpeg.org/wiki/How%20to%20compile%20FFmpeg%20for%20Raspberry%20Pi%20%28Raspbian%29 or http://xathrya.web.id/blog/2013/08/30/building-cross-compiler-for-raspberry-pi-using-crosstool-ng/ (also take care to pick a proper eglibc version for you rPi, mine is running with 2.13).

Then the following rough shell script compiles everything you need for getting a working bitcoind 0.8.5 cross-compiled. This is similar to https://bitcointalk.org/index.php?topic=119614.msg1290289#msg1290289, but there are some modifications necessary to get it properly compiled (like compiling zlib and linking bitcoind with -lrt). You can restrict which boost libraries are compiled, but the following code just tries to compile everything (some will fail, like boost-python, but that is ok since they are not needed for compiling bitcoind). The following code assumes the toolchain has been built at /opt/cross/x-tools/arm-unknown-linux-gnueabi, you can modify that as needed by changing the CROSS_PREFIX and CROSS_PATH variables.

Code:

# BUILD_OUTPUT_DIR must be an absolute directory
BUILD_OUTPUT_DIR=/change/this/path/

DL="curl -O"
GIT="git"

BTC_VERSION="0.8.5"
BTC_REPO="https://github.com/bitcoin/bitcoin"

ZLIB="zlib-1.2.8"
ZLIB_PKG="${ZLIB}.tar.gz"
ZLIB_SRC="http://zlib.net/${ZLIB_PKG}"
OPENSSL="openssl-1.0.1e"
OPENSSL_PKG="${OPENSSL}.tar.gz"
OPENSSL_SRC="https://www.openssl.org/source/${OPENSSL_PKG}"
BOOST="boost_1_54_0"
BOOST_PKG="${BOOST}.tar.bz2"
BOOST_SRC="http://softlayer-dal.dl.sourceforge.net/project/boost/boost/1.54.0/${BOOST_PKG}"
LIBDB="db-5.3.21"
LIBDB_PKG="${LIBDB}.tar.gz"
LIBDB_SRC="http://pkgs.fedoraproject.org/repo/pkgs/libdb/db-5.3.21.tar.gz/3fda0b004acdaa6fa350bfc41a3b95ca/${LIBDB_PKG}"

# Download packages as needed.
if [ ! -f ${OPENSSL_PKG} ]; then
    ${DL} ${OPENSSL_SRC}
fi
if [ ! -f ${BOOST_PKG} ]; then
    ${DL} ${BOOST_SRC}
fi
if [ ! -f ${LIBDB_PKG} ]; then
    ${DL} ${LIBDB_SRC}
fi

if [ ! -f ${ZLIB_PKG} ]; then
    ${DL} ${ZLIB_SRC}
fi

# Clone the bitcoin branch at version ${BTC_VERSION}.
if [ ! -d bitcoin ]; then
    ${GIT} clone -b ${BTC_VERSION} ${BTC_REPO}
fi

# Compile everything.
export CROSS_PREFIX=arm-unknown-linux-gnueabi
CROSS_PATH="/opt/cross/x-tools/${CROSS_PREFIX}"
export CC=${CROSS_PATH}/bin/${CROSS_PREFIX}-gcc
export CXX=${CROSS_PATH}/bin/${CROSS_PREFIX}-g++
export LD=${CROSS_PATH}/bin/${CROSS_PREFIX}-ld
export CFLAGS=-I${CROSS_PATH}/include
export LDFLAGS=-L${CROSS_PATH}/lib
export PATH=$PATH:${CROSS_PATH}/bin

if [ ! -d ${LIBDB} ]; then
    tar -xzvf ${LIBDB_PKG}
    cd ${LIBDB}/build_unix
    ../dist/configure --enable-cxx --host=${CROSS_PREFIX} --prefix=${BUILD_OUTPUT_DIR} && make && make install
    cd ../../
fi

if [ ! -d ${OPENSSL} ]; then
    tar -xzvf ${OPENSSL_PKG}
    cd ${OPENSSL}
    ./Configure --prefix=${BUILD_OUTPUT_DIR} dist && make && make install
    cd ..
fi

if [ ! -d ${BOOST} ]; then
    tar -xjvf ${BOOST_PKG}
    cd ${BOOST}
    echo "using gcc : arm : ${CXX} ;" >> tools/build/v2/user-config.jam
    ./bootstrap.sh
    ./bjam toolset=gcc-arm link=static
    ./bjam toolset=gcc-arm link=static --prefix=${BUILD_OUTPUT_DIR} install
    cd ..
fi

if [ ! -d ${ZLIB} ]; then
    tar -xzvf ${ZLIB_PKG}
    cd ${ZLIB}
    ./configure --prefix=${BUILD_OUTPUT_DIR} && make && make install
    cd ..
fi

export BOOST_INCLUDE_PATH=${BUILD_OUTPUT_DIR}/include
export BDB_INCLUDE_PATH=${BUILD_OUTPUT_DIR}/include
export OPENSSL_INCLUDE_PATH=${BUILD_OUTPUT_DIR}/include
export BOOST_LIB_PATH=${BUILD_OUTPUT_DIR}/lib
export BDB_LIB_PATH=${BUILD_OUTPUT_DIR}/lib
export OPENSSL_LIB_PATH=${BUILD_OUTPUT_DIR}/lib
 
cd ./bitcoin/src/ 
LDFLAGS=-lrt make STATIC=1 -f makefile.unix bitcoind USE_UPNP=
${CROSS_PREFIX}-strip bitcoind

[RaTTuS]

you can run cgminer and asic block eruptors on it no problem
[well apart from the you'll never make your investment back problem ]

but it runs OK - as long as you have a good powered USB hub

[gigatux]

If anyone wants precompiled .debs for bitcoind, including db4.8 dependencies, I've put them up at https://bittylicious.com/downloads/.

I've started a new thread at https://bitcointalk.org/index.php?topic=300721 for discussion on the .debs.

[Jonasch]

NOTE: I prefer to save these keys in plain text because if I die or get a serious brain injury, I want my family to be able to get the coins instead of burying them with my "brain wallet" or secret password.

I thought a lot about encryption and inheritance, not just encryption of BTC wallets, but also just general files, fotos, letters.
I have been using full disk encryption for a long time and also thought about ways to securely convey secret messages to family in case I die.

You could check if it is possible in your jurisdiction to leave behind with a lawfirm / notary a sealed letter that is only to be opened privately by your family or a specific family member.
It could contain just the passphrase to your encrypted volume, possibly contact details of a friend who can help family with decryption if needed.
The friend and your family could be told about this in advance. The passphrase could also be used to decrypt a password keeping software that contains other passwords that you would them to have access to.