Armory - Discussion Thread

[CHAOSiTEC]

Any eta on when you will be working on hardware wallets?

[1713897283]

1713897283

[1713897283]

1713897283

[1713897283]

1713897283

[goatpig]

Any eta on when you will be working on hardware wallets?

Trezor support at best in the next release, that's late October/early November if everything goes according to plan.

[jl2012]

Any eta on when you will be working on hardware wallets?

Trezor support at best in the next release, that's late October/early November if everything goes according to plan.

Does it mean Armory will support the long awaited BIP32 (deterministic wallet) and 39 (Mnemonic code)? I guess it has to or it won't work with Trezor.

[justusranvier]

Any eta on when you will be working on hardware wallets?

Trezor support at best in the next release, that's late October/early November if everything goes according to plan.

Does it mean Armory will support the long awaited BIP32 (deterministic wallet) and 39 (Mnemonic code)? I guess it has to or it won't work with Trezor.

Don't forget BIP43 and BIP44

[CHAOSiTEC]

Any eta on when you will be working on hardware wallets?

Trezor support at best in the next release, that's late October/early November if everything goes according to plan.

so im assuming that after trezor support is included in armory, its going to be easy to implement other hardware wallets, since the ground work has been done, am i correct?

[Ente]

Any eta on when you will be working on hardware wallets?

Trezor support at best in the next release, that's late October/early November if everything goes according to plan.

so im assuming that after trezor support is included in armory, its going to be easy to implement other hardware wallets, since the ground work has been done, am i correct?

BIP0032, 0038, 0039 are nice things. As we all are techies and most of us like it, those might become the "standard" fast. When several clients use them, other hardwarewallets likely will follow them too. Then Armory doesn't need any, or only small changes to support those future hardware-wallets.

I like!

Ente

[goatpig]

so im assuming that after trezor support is included in armory, its going to be easy to implement other hardware wallets, since the ground work has been done, am i correct?

Not necessarily. There are 4 steps to integrating a hardware wallet:

1) Implement the standard. That's a one time cost, but there's no knowing which BIPs future hardware wallets will require.
2) Communication layer. With Trezor that part is overly simple (for us, we use Python on the front end), but again, no guarantee other wallets will go down that path.
3) UI integration. A portion of the Trezor code can be recycled for new wallets, but maybe not as large as we hope.
4) Unit tests. Depending on how many features the hardware wallet supports and its API, this can take its sweet time.

The good side is that we will most likely release support for these devices in the form of plugins, so it won't have to wait for a major release.

[CHAOSiTEC]

so im assuming that after trezor support is included in armory, its going to be easy to implement other hardware wallets, since the ground work has been done, am i correct?

Not necessarily. There are 4 steps to integrating a hardware wallet:

1) Implement the standard. That's a one time cost, but there's no knowing which BIPs future hardware wallets will require.
2) Communication layer. With Trezor that part is overly simple (for us, we use Python on the front end), but again, no guarantee other wallets will go down that path.
3) UI integration. A portion of the Trezor code can be recycled for new wallets, but maybe not as large as we hope.
4) Unit tests. Depending on how many features the hardware wallet supports and its API, this can take its sweet time.

The good side is that we will most likely release support for these devices in the form of plugins, so it won't have to wait for a major release.

Nice, since ive been using armory for.. well ages, lol, and i have just recieved my HW.1 hardwarewallet (btcchip.com) and they use python, so that should make it easy to implement, since its python based pluginish :-p (electrum has support for it in dev version)

[Ente]

The good side is that we will most likely release support for these devices in the form of plugins, so it won't have to wait for a major release.

Plugins is my #1 wish functionality by now! :-)

Ente

[Newar]

I'm probably missing something... How can I change a label (comment) of an address after it has been created? I don't see any way in the Wallet Properties (right click, double click etc.)

[CHAOSiTEC]

I'm probably missing something... How can I change a label (comment) of an address after it has been created? I don't see any way in the Wallet Properties (right click, double click etc.)

Addresses -> View Address Book

;-)

[TimS]

I'm probably missing something... How can I change a label (comment) of an address after it has been created? I don't see any way in the Wallet Properties (right click, double click etc.)

I think that every comment can be changed if you double click the comment itself (not just its line, but the comment cell).

[Newar]

I think that every comment can be changed if you double click the comment itself (not just its line, but the comment cell).[/quote]

That will only change the comment for that particular tx.

Comments in the transaction view are created from the comment you give it when generating the address. I was looking for a way to change that "permanent" comment. CHAOSiTEC's hint worked fine.

[pitiflin]

I'm using Armory 0.90-beta

Should I update my version?

I have all my BTC in Armory and I'm afraid to update

[etotheipi]

I'm using Armory 0.90-beta

Should I update my version?

I have all my BTC in Armory and I'm afraid to update

We do recommend you update anything before 0.91.  And 0.92.1 is a solid release.

[pitiflin]

I'm using Armory 0.90-beta

Should I update my version?

I have all my BTC in Armory and I'm afraid to update

We do recommend you update anything before 0.91.  And 0.92.1 is a solid release.

Ok, so I just download & install the 0.92.1 version and all my wallets will show up again? Do I have to do anything else besides download & install?

EDIT: I also have an offline wallet on an offline computer, should I update that version as well?

[etotheipi]

I'm using Armory 0.90-beta

Should I update my version?

I have all my BTC in Armory and I'm afraid to update

We do recommend you update anything before 0.91.  And 0.92.1 is a solid release.

Ok, so I just download & install the 0.92.1 version and all my wallets will show up again? Do I have to do anything else besides download & install?

EDIT: I also have an offline wallet on an offline computer, should I update that version as well?

You can update your online computer without touching the offline computer if you install 0.91.2 online. 

However, all the offline transaction formats changed to accommodate multisig with 0.92+, so if you upgrade your online computer to that, you'll have to do the same offline.

[bitpop]

No need to be afraid, we are here

[pitiflin]

I'm using Armory 0.90-beta

Should I update my version?

I have all my BTC in Armory and I'm afraid to update

We do recommend you update anything before 0.91.  And 0.92.1 is a solid release.

Ok, so I just download & install the 0.92.1 version and all my wallets will show up again? Do I have to do anything else besides download & install?

EDIT: I also have an offline wallet on an offline computer, should I update that version as well?

You can update your online computer without touching the offline computer if you install 0.91.2 online. 

However, all the offline transaction formats changed to accommodate multisig with 0.92+, so if you upgrade your online computer to that, you'll have to do the same offline.

Alright, I don't have to uninstall the old versión right? Just download the new one and install both on the online and offline computer. Am I right?

[bitpop]

Yes and your online one will authenticate the download