Is there any way to sweep a private key without typing in on a connected computer ?

Something like :- enter the bitcoin address on the connected computer in a watch only wallet- scan the blockchain for all funds on this address- create a raw transaction to move them to the armory wallet- move the transaction to the offline computer- enter the private key there, sign the transaction- broadcast the transaction back from the online computer ?

Is there any way to sweep a private key without typing in on a connected computer ?

Something like :- enter the bitcoin address on the connected computer in a watch only wallet- scan the blockchain for all funds on this address- create a raw transaction to move them to the armory wallet- move the transaction to the offline computer- enter the private key there, sign the transaction- broadcast the transaction back from the online computer ?

That would be a very handy feature!Sweeping brainwallets, coins, paperwallets and all.

Is there any way to sweep a private key without typing in on a connected computer ?

Something like :- enter the bitcoin address on the connected computer in a watch only wallet- scan the blockchain for all funds on this address- create a raw transaction to move them to the armory wallet- move the transaction to the offline computer- enter the private key there, sign the transaction- broadcast the transaction back from the online computer ?

That would be a very handy feature!Sweeping brainwallets, coins, paperwallets and all.

Ente

Had a lot of requests for this. Right now the only way to do it is to create a new wallet on the offline computer, import the keys, export the new watch-only wallet to the online computer, then perform an offline transaction to move all the coins. It's four steps... If you have the public key already it could theoretically be three steps, but Armory doesn't allow importing of public keys into WO wallets.

Anyone with a RaspberryPi try this out! I finally got my RPi up and working and was able to extract the dependency tree into an offline bundle. It seemed to work on mine, someone else please try it with a fresh raspbian install and let me know:

I have been cross-compiling it for Pi on one of my Ubuntu VMs. I downloaded crosstool-ng and built the armhf g++ from scratch, then used that to compile _CppBlockUtils.so. I had to make one small modification to the Armory Makefile to make sure it's linking against the armhf python, but it didn't need any further modification (and that can be easily removed as well). Once it's all setup, it actually compiles no differently than regular building. I didn't need to mess with the crypto++ libraries or makefiles at all.

It worked on my freshboot RPi with those dependencies, but I was also online so I wonder if it really got everything or if it silently installed some stuff in the background. That's why I wanted someone else to try it.

I compiled it using the pi itself. That is very slow , but less hassle than cross compiling.

Depends what you mean by "less hassle". Doing it my way requires more "down payment" to get it setup, but then it's trivial to compile new versions. Once I push my latest changes to the repo, I can just switch to the RPi directory, pull, and run "make CXX=<pathtocxcompile-g++>". 3 minutes later I have an RPi release

In fact, I think I don't even have to switch directories! But I do it anyway to be clean.

Depends what you mean by "less hassle". Doing it my way requires more "down payment" to get it setup, but then it's trivial to compile new versions. Once I push my latest changes to the repo, I can just switch to the RPi directory, pull, and run "make CXX=<pathtocxcompile-g++>". 3 minutes later I have an RPi release

In fact, I think I don't even have to switch directories! But I do it anyway to be clean.

Heh, true. I guess it is the difference between a user and a developer.

Being able to download the pre-compiled files is easier for everyone.

For multi-sig, are you planning to have watch only wallet capability?

This would be where you could have 3 watching only wallets installed and it would tell you that a multi-sig payment could be redeemed by 2 of 3 of them.

You could also allow creation of a spending transaction that each private key owner could sign in turn.

This is better for "boards" that have N of M spending requirements. Each member would have a watching-only wallet for all keys associated with the cold store and one set of private keys.

You could also create 2 level shamir sharing. For example, you could have 2 of 3 sharing, but each share is then split up into 2 of 3 as well. This means that each share is protected against loss too by sharing.

This would be where you could have 3 watching only wallets installed and it would tell you that a multi-sig payment could be redeemed by 2 of 3 of them.

You could also allow creation of a spending transaction that each private key owner could sign in turn.

This is better for "boards" that have N of M spending requirements. Each member would have a watching-only wallet for all keys associated with the cold store and one set of private keys.

You could also create 2 level shamir sharing. For example, you could have 2 of 3 sharing, but each share is then split up into 2 of 3 as well. This means that each share is protected against loss too by sharing.

This is already supported by the lockboxes! All parties in a lockbox can be offline keys, created separately and independently. Each party individually manages their own wallet holding that key, including all the regular methods we have backups... yes you can do a 2-of-4 lockbox between 4 parties, and each party can do a 3-of-5 fragmented backup of their individual wallets (which hold the key).

Speaking of that, we're working on multisig lockboxes on the "devel" branch -- anyone can check it out and play with it. It's actually looking really good. Got P2SH working, so you should be able to go above 3-of-3 on mainnet now... but of course I don't recommend using any money you can't afford to lose (yet)!

The lockboxes and all the data passed between devices/parties assumes that all keys are offline, and thus always contain all information needed to sign offline. The downside to this is that all these message formats have changed, even for regular offline transactions, so all online & offline devices will need to be updated to use this. But once you do, it does work!

Will have the last couple pieces of it implemented soon and put out an experimental build to get people playing with.

This is already supported by the lockboxes! All parties in a lockbox can be offline keys, created separately and independently. Each party individually manages their own wallet holding that key, including all the regular methods we have backups... yes you can do a 2-of-4 lockbox between 4 parties, and each party can do a 3-of-5 fragmented backup of their individual wallets (which hold the key).

This is already supported by the lockboxes! All parties in a lockbox can be offline keys, created separately and independently. Each party individually manages their own wallet holding that key, including all the regular methods we have backups... yes you can do a 2-of-4 lockbox between 4 parties, and each party can do a 3-of-5 fragmented backup of their individual wallets (which hold the key).

It is not necessary to upgrade any offline computers just to check wallet consistency.

How do we do that from the Armory menus? Or just restart Armory?

I have upgraded to 0.91.1 and it checked for my wallet consistency when i started it. Guess i don't have to do anything else.

Notice it says not necessary If all your hot wallets and watching-only wallets have been loaded on 0.91 or 0.91.1 before, and no notification popped up, no further action is required. I would guess that 99%+ users will pass this check without issue. And of those cases with consistency issues, the recovery tool can fix most of them.

Will post more information about this soon. Working on getting an announcement page up and distributing notifications to older versions.

It is not necessary to upgrade any offline computers just to check wallet consistency.

How do we do that from the Armory menus? Or just restart Armory?

I have upgraded to 0.91.1 and it checked for my wallet consistency when i started it. Guess i don't have to do anything else.

Notice it says not necessary If all your hot wallets and watching-only wallets have been loaded on 0.91 or 0.91.1 before, and no notification popped up, no further action is required. I would guess that 99%+ users will pass this check without issue. And of those cases with consistency issues, the recovery tool can fix most of them.

Will post more information about this soon. Working on getting an announcement page up and distributing notifications to older versions.

Somehow I understood that an upgrade isn't necessary, but we still needed to check the wallet consistency. I got it now. Thank you.