Will the Armory Wallet be made compatible with the Trezor hardware wallet?

[Carlton Banks]

Yes, but we all are here because we insist on the very best bitcoin wallet. Armory. :-)
Trezor with a decentralized node is great and important too. And not everyone believes they need the whole Armory featureset.

Still, I'll be waiting for the Armory Trezor integration.

with HWI doing the hardware part (https://github.com/bitcoin-core/hwi), it should be pretty easy to achieve. Armory really just needs to start speaking BIP174, and that's more or less the whole thing.

I really hope Armory doesn't use boost process though, that's my least favorite aspect of Bitcoin Core's external signer implementation (coming in 22.0). I know, platform independent etc, but boost is usually over-baked for what is needed, plus quite buggy (and I just don't care whether Windows users get new features or not, to be quite honest)

[goatpig]

There is a PSBT implementation in the dev branch. It's about 95% compliant (doesn't really deal with custom fields yet).

[NotATether]

with HWI doing the hardware part (https://github.com/bitcoin-core/hwi), it should be pretty easy to achieve. Armory really just needs to start speaking BIP174, and that's more or less the whole thing.

Well, I'd be happier if Bitcoin Core was bundled with HWI and there was a special RPC command just for abstracting the wallet descriptors details. In other words, instead of importdescriptors followed by walletcreatefundedpsbt, we modify the PSBT RPCs to take parameters that dereference the specific hardware wallet in HWI, avoiding the importdescriptors call entirely.

[goatpig]

with HWI doing the hardware part (https://github.com/bitcoin-core/hwi), it should be pretty easy to achieve. Armory really just needs to start speaking BIP174, and that's more or less the whole thing.

Well, I'd be happier if Bitcoin Core was bundled with HWI and there was a special RPC command just for abstracting the wallet descriptors details. In other words, instead of importdescriptors followed by walletcreatefundedpsbt, we modify the PSBT RPCs to take parameters that dereference the specific hardware wallet in HWI, avoiding the importdescriptors call entirely.

HWI is in Python, Core is in C++. I don't see them bothering with this kind of a headache.

[HCP]

Well, I'd be happier if Bitcoin Core was bundled with HWI and there was a special RPC command just for abstracting the wallet descriptors details. In other words, instead of importdescriptors followed by walletcreatefundedpsbt, we modify the PSBT RPCs to take parameters that dereference the specific hardware wallet in HWI, avoiding the importdescriptors call entirely.

You may not have to wait much longer https://bitcointalk.org/index.php?topic=5347523.0

Seems that 0.22 will be including "External signer" functionality that is compatible with HWI: https://github.com/bitcoin/bitcoin/blob/master/doc/external-signer.md