Sorry that was the situation before, where I couldn't get it to work. (neither with any other version for online)

So later I switched to using tails (or 3.0.1 on my normal Ubuntu install for testing)

I did try the export button and qr code, but those transactions could not be signed by the offline wallet.

I think maybe what happened had to do with the fact that I first tried to install 3.3.3 on the raspberry, which didn't work because of the correct python version being unavailable, which maybe created some stuff in the .electrum folder that didn't really work with the older versions. I am not sure.

I am not sure which version I used for the online side, because I just used the latest version of tails and didn't really check it. Come to think of it, I am not sure if I verified the image. I will sort that out. What is the overall opinion about tails around here? With electrum being preinstalled it makes verification a bit iffy.
I guess I could verify the transaction on my cold storage, and after signing an extra time on a different device, but I think it would be easier to be able trust a live-cd that I am running.

About the older versions: my reasoning was that many cold storages use older versions because of them often being as insulated as possible.

I am quite certain that I was not exporting received transactions; besides I have tried the process many times.

Anyway, I have reinstalled my raspberry and Installed electrum-3.0.1 now (which has the 'save' button for cold storage) and everything is working as it should.

I am aware of the vulnerability of these older versions, and on top of that I am using cold-storage anyways, but I was wondering if there is any other significant disadvantage to using an older version?

Okay I managed to install libsecp256k1-0 on my raspberry pi.

On my laptop I tried to run many different versions of electrum; the older ones dont seem to synchronize, and the newer ones all have the same 'issue'.

I am not even sure if this is really the problem, because when I hover over the greyed out 'save' button it says you need to sign the transaction before saving it.
which makes me think the instructions here http://docs.electrum.org/en/latest/coldstorage.html are wrong/outdated.

And all the versions I have tried on my laptop, after creating a new watch-only wallet from two different public master keys, from two different versions of electrum on my raspberry, have this 'save' button greyed out.

I have tried the 'export' and the QRcode options, but when I open these on my raspberry its gives 'status:signed' and transaction unrelated to your wallet.

It all seems very strange, and I will try to set up a cold wallet with tails or bitkey on my laptop  tomorrow. I hope to finally be able to set up a cold wallet. I have been struggling with this for a couple of days now; including the problems with python versions, installation, pgp verification etc. (

No I didn't yet manage to prepare or transfer the transaction, i get stuck at the greyed out 'save' button; the message appears in terminal every time i start electrum.

(edit) when I try 'sudo apt-get install libsecp256k1-0' It says 'unable to locate the package
(edit2) on laptop that is.

I set up a cold storage wallet on my raspberry pi (debian stretch with electrum-3.2.3) with a 12 word seed and some extra words of my own choosing.
Then, on my laptop, also running version 3.2.3, I set up a watch-only wallet with the master public key from my cold wallet. (transferred with QR code)

All seemed fine; I transferred some funds in there and they were received.

After this I wanted to test transferring funds out of the cold storage, but I got stuck when I wanted to create an unsigned transaction, as per the instructions.


After I go to the 'send' tab, fill it in, and press 'preview' the 'save' button in the popup window is greyed out. I was planning on using qr-codes, but my cold wallet wont let me sign this transaction either way.


When running electrum on the Raspberry form terminal i get the following messages:

[ecc] info: libsecp256k1 library not available, falling back to python-ecdsa. This means signing operations will be slower.
libEGL warning: DRI2: failed to authenticate
qt5ct: using qt5ct plugin
qt5ct: D-bus system tray: no
inotify_add_watch("/home/pi/.config/qt5ct failed: "no such file or directory")
qt5ct: D-bus global menu: no

When running electrum in Ubuntu I only get this message: [ecc] info: libsecp256k1 library not available, falling back to python-ecdsa. This means signing operations will be slower.