Author

Topic: New wallet format (Read 489 times)

legendary
Activity: 2126
Merit: 1001
April 15, 2014, 03:49:20 PM
#3
Hah.  It wasn't so much "maybe later, leave us alone", but more like:  "yes!  when this reaches high priority, this is exactly what we're going to do!"

The answer to this is:  new wallet format is highest priority, especially now that we have all the multi-sig hooks in place.  And we fixed the RAM issues... and we have resources to handle other things!

To address your points directly:  we will have support for both compressed and uncompressed.  Along with the ability to migrate old wallets.  Compressed will be default,  but have the capability to handle uncompressed.

Standard usermode, will by default, derive all wallets from the same seed, thus requiring one backup per user, not per wallet.  But in Adv and Expert, you will have the option to create different seeds which spawn wallets with different backups, encryption passwords and security profiles.  This is exceptionally important when it comes to offline wallets and multi-sig, having this flexibility.

The new wallet format will also have a much-more-flexible encryption scheme.  It will allow for arbitrary data to be stored from set of different encryption and key-stretching options.  It would technically allow the user to do very complex things, though none of those complexities will be default.  But it allows us to build cool things into it -- like the ability to encrypt comments&labels with your publickey&chaincode, thus all your watching-only wallets can decrypt the data, and thus that data can be backed up and synchronized between devices (as long as you don't store the WO wallet with it!)  Or multiple people in an organization can easily synchonize meta-data just by having the WO wallet.

There's a lot of cool things we can do with it.  This only scratches the surface Smiley  Stay tuned! 

---
P.S. - When I said this was high-priority, it was originally because we were really anxious to get some multi-sig features implemented, and we thought that we would have to wait for the new wallet format to do it.  With the availability of lockboxes right now we are actually going to prioritize that first, and then work on the new wallet which will provide much more flexible multi-sig.  Because, we want to take our time with the new wallets, and if there's already a usable multi-sig solution out there, then we won't be as rushed.

Oh my gosh! That sounds fabulous! :-)
"Stay tuned"? I feel like shortly before christmas here!
Oh boy oh boy! I really am happy with all that! :-)

Ente
legendary
Activity: 1428
Merit: 1093
Core Armory Developer
April 15, 2014, 03:14:11 PM
#2
Hah.  It wasn't so much "maybe later, leave us alone", but more like:  "yes!  when this reaches high priority, this is exactly what we're going to do!"

The answer to this is:  new wallet format is highest priority, especially now that we have all the multi-sig hooks in place.  And we fixed the RAM issues... and we have resources to handle other things!

To address your points directly:  we will have support for both compressed and uncompressed.  Along with the ability to migrate old wallets.  Compressed will be default,  but have the capability to handle uncompressed.

Standard usermode, will by default, derive all wallets from the same seed, thus requiring one backup per user, not per wallet.  But in Adv and Expert, you will have the option to create different seeds which spawn wallets with different backups, encryption passwords and security profiles.  This is exceptionally important when it comes to offline wallets and multi-sig, having this flexibility.

The new wallet format will also have a much-more-flexible encryption scheme.  It will allow for arbitrary data to be stored from set of different encryption and key-stretching options.  It would technically allow the user to do very complex things, though none of those complexities will be default.  But it allows us to build cool things into it -- like the ability to encrypt comments&labels with your publickey&chaincode, thus all your watching-only wallets can decrypt the data, and thus that data can be backed up and synchronized between devices (as long as you don't store the WO wallet with it!)  Or multiple people in an organization can easily synchonize meta-data just by having the WO wallet.

There's a lot of cool things we can do with it.  This only scratches the surface Smiley  Stay tuned! 

---
P.S. - When I said this was high-priority, it was originally because we were really anxious to get some multi-sig features implemented, and we thought that we would have to wait for the new wallet format to do it.  With the availability of lockboxes right now we are actually going to prioritize that first, and then work on the new wallet which will provide much more flexible multi-sig.  Because, we want to take our time with the new wallets, and if there's already a usable multi-sig solution out there, then we won't be as rushed.
legendary
Activity: 2126
Merit: 1001
April 15, 2014, 02:59:47 PM
#1
Dear Armory devs,

(I take great pleasure in seeing you devs are too many to address individually now!)

any news on the new wallet format?

I have two requests in mind:

1) It would be great to have support for both "uncompressed" and "compressed" addresses and private keys. As it is now, I can't export my compressed privkeys from my android Schildbach wallet to Armory (as a backup, for watching transactions and having quick access).

2) The new deterministic wallet "standard" defines a tree, where each branch can be an address or another fork (which then has more branches, addresses, or a whole new "tree").
Right now I have several wallets in Armory, for security, privacy and accounting reasons.
I would absolutely *love* it to have one meta-wallet-tree (with one file, one seed and one backup), and have the GUI seperate this into several "wallets" the way I have it now.
Important would be that no inputs/outputs are mixed in between the "wallets". Also, we would need some clever way to have different passwords for the "wallets" and support for mixed online and offline "wallets" in one meta-wallet-tree.

This would be a killer feature for me, I'll gladly do a bounty for this if it helps.
I suggested this like half a year ago, back then it was "interesting, maybe later".

What do you think?
What can I do to make this happen?

Ente
Jump to: