In this thread Peter posted a link to some experimental pre-0.8 builds on his server. That's what I'm running. Block data files are now ~128MB, numbered blk000X.dat, and in the .bitcoin/blocks folder. Other than that, I'm not sure what changed.

Oh, and it looks like there is a problem where Armory doesn't see any new blocks coming in after it's caught up, when connected to a 0.8 client. I thought it was a permissions issue, but after fixing that I'm still seeing it. Nothing interesting in the log, either.

Sorry, I might not have been clear. It reads the files, but when it gets to the "end" of one, it throws this error a bunch (random amount?), before it starts reading the next.

Thanks! Yeah, I don't think this needs to be a core part of Armory, especially since there are so few changes necessary, and Armory is very easy to build (at least on Linux).

I've run into one strange issue though... the extra scripts work just fine on my online machine, but on the Pi they stopped working. It's not giving me an "unrecognized symbol: armoryengine error", it just doesn't recognize CLI_ARGS (or any other "constant" from armoryengine), even though I'm doing "from armoryengine import *". Oddly, running "python armoryengine.py" works just fine, and starting up a REPL and doing "from armoryengine import *" lets me "print CLI_ARGS" without issue. Any ideas?

edit... Hmm. It must be a path issue of some kind, because when I move the script out of the extras directory and remove the "sys.path.append('..')", it works.

Here is a diff of my changes: http://pastebin.com/A9x0grtz

There's probably a better way to do some of the threaded stuff for the listener, and I'll probably clone the Github project and submit a push request to make it easier for either etotheipi or others to fix it up, but right now it works pretty well!

Wouldn't you be supporting the bitcoin economy by exchanging your bitcoins for dollars, and buying two Pies instead of one?


True, but I can't imagine a scenario where those benefits of Bitcoin necessitate paying double the price for something like a Pi.

I'm really excited!

After considering the criticism of my Armory Pi setup, I spent the day learning serial ports, (more) python, and Armory. I'll release the codes tomorrow, but my solution is pretty sweet. I disabled the serial terminal and replaced it with a program that listens for unsigned transactions. When it sees one, it unlocks the wallet with the passphrase entered on the Pi's own keyboard, signs the transaction, and sends it back over the serial port. The other modification is to Armory, specifically the first offline transaction screen. Along with "Save as file" and "Copy to clipboard" options, there is now a "Transmit over serial" button, which does just what it seems. When it receives the signed transaction back, it automatically advances to and fills the text box on the transaction broadcast screen.

All this required surprisingly little code, but I need some sleep right now!

edit... I found a bug (or two). If you're running the LevelDB version of Bitcoin, Armory won't go online if the blk00*.dat files don't exist, even if the blocks/blk000*.dat files do. Also, I saw a lot of this


at what I am assuming is the end of a block data file, before the next one begins scanning. It can last for quite a few seconds sometimes, churning those out 10 per seconds or so.

That would be awesome, but I'm not sure how to do this over a serial connection, since I'm not using ssh, but screen.

I don't know, this guy doesn't seem very trustworthy...

So I'm finally quite happy with my offline wallet setup, and I wanted to share it with others.

I have been using a Rapsberry Pi to run the offline instance of Armory. It was hooked up to my monitor through HDMI, and I had an extra keyboard around. When I wanted to perform an offline transaction, I would create it on my main computer, put it on a USB drive, plug the keyboard and USB drive into the Pi, run Armory, sign the transaction, transfer it back to the main computer, and broadcast it.

Last week, I purchased a USB to TTL, and that whole process changed for the better. The cable provides power to the Pi and allows for a terminal login to the device, so I no longer need an HDMI cable, power cable, or keyboard. I merely keep it unplugged, and plug it in when I want to perform a transaction. I log in using screen (screen /dev/ttyUSB0 115200), then run this script which does the following...

Opens a new file called armory.unsigned.tx in Nano, allowing me to paste in the ascii-serialized transaction
Runs this script against the unsigned file
If the file was signed, then display it using Less (at which point I copy it and paste into the broadcast transaction form)
Shutdown the Pi

I'm pretty sure that the TTY device only allows for a single login at a time, so I don't think it would be possible, and certainly not feasible, for an attacker to steal bitcoins from the Pi during the short time that it's connected to my computer. Any thoughts?

Just ran into an issue with a few transactions which have been included in a block being stuck at 0 confirmations. I renamed mempool.bin, restarted, and then they weren't in the transaction list at all. What can I give you that would help you figure out the cause?

edit... I'll email you the log, a watching only copy of the wallet, and mempool.bin

Ok, will do! Thanks for being awesome!

That's awesome, I didn't see that documented anywhere.

Is 14B8Zb94ypK7R11UV1RAojJkeSmpCHZfKJ still your donation address? I'd like to show my appreciation for your service.

I know I've bugged you a bit with feature requests, but I thought of another that would be nice.

When creating a custom dynamic price, it would be nice to have min() and max() functions. For instance, if I'm selling I might want to sell at USD_24h or mtgoxUSD_ask, whichever is higher.

Is 14B8Zb94ypK7R11UV1RAojJkeSmpCHZfKJ still your donation address? I don't see it on the site anymore.

As etotheipi obersved, I based it off of his cli_sign_txdp.py script.


Thanks! The page that describes their mixer, along with an HTML interface to it is here. Yeah, you give them a destination address, and they give you an anonymous forwarding address. They only keep the association in their database for 8 hours, unless the forwarding address receives funds, then the association is kept until 6 confirmations. When an anonymous transaction is queued, blockchain.info wallet users that create transactions will have their funds routed to your destination address, and your funds will be routed to their destination. They use their taint analysis tools to guarantee that the input and output are not linked through the block chain in any way.

The time varies, depending on how much you need mixed. I've had it take as little as half an hour, as long as two days (but that was for quite a large amount).

Great, I switched branches and used the coin control dialog once without issue. It is slick, nice job.

In case anyone else created their savings to Armory in one massive transaction like I did, and now are bothered that the entire amount is linked (if you spend 1 BTC to someone, they can trivially see how many coins you own), here's the script I used. It asks how much you want to anonymize, and the min and max amount you would want in each address. It creates addresses in your selected wallet, uses blockchain.info's API to create an anonymous forwarding address, and selects a random amount between the min and max. It builds a transaction with as many outputs as needed to hit the total, and then saves it to a file. This can then be imported into Armory, inspected, signed, and broadcast.

I used blockchain.info for this because I trust them, they have an API, and they charge a (IMO) reasonable 1.5 % fee.

http://pastebin.com/XLT5FgdB

That's awesome news. Question: has the threading branch been merged to master, or do I have to manually merge the two branches to test this?

That looks excellent! Perfect timing too, since I just used armoryengine and blockchain.info's anonymous forwarding API to split the one huge output I've had in my offline wallet since I switched to armory into a bunch of unconnected outputs. With this, I'll be able to ensure that there is as little tainting as possible.

Theft deprives someone use of the thing. Copying test scores or an mp3 file doesn't deprive the rightful owner use of it, thus, it is not theft. Spending someone else's bitcoins does deprive them use of it, thus it is theft.

I agree that it wasn't the place for asking for upvotes, and that the title of this thread is exaggerated. However, after the warning, the topic changed to new translations of the Bitcoin software. I think it is completely unreasonable for Jeremias to have been banned for that.

Armory's not very good at "drinking from the firehose", as I've heard it described.