|
Title: Armory 0.96.5 compatibility with SegWit-Bech32 or SegWit-P2SH Post by: kentbull on December 12, 2022, 05:36:21 PM Does Armory wallet support any type of SegWit?
One of my clients did a transaction and saw a BlockStream message indicating he could save 40%+ using Segwit-Bech32 or 30%+ using SegWit-P2SH. If there's a way to leverage SegWit with 0.96.5 then I'd like to direct him to do so. Title: Re: Armory 0.96.5 compatibility with SegWit-Bech32 or SegWit-P2SH Post by: hosseinimr93 on December 12, 2022, 05:47:33 PM Armory can generate nested segwit (p2wpkh-p2sh) addresses, but it can't generate native segwit (bech32) addresses.
For generating a nested segwit address in Armory, click on "Address Type" when generating a new receiving address and check "P2SH-P2WPKH address". If you want a bech32 address, you have to use another wallet. Title: Re: Armory 0.96.5 compatibility with SegWit-Bech32 or SegWit-P2SH Post by: goatpig on December 13, 2022, 10:33:01 AM Does Armory wallet support any type of SegWit? One of my clients did a transaction and saw a BlockStream message indicating he could save 40%+ using Segwit-Bech32 or 30%+ using SegWit-P2SH. If there's a way to leverage SegWit with 0.96.5 then I'd like to direct him to do so. 0.96.5 can: - generate and pay to P2SH-P2WPKH addresses (nested segwit). - pay to bech32 addresses (native segwit). Your client cannot choose what address type he pays to. The recipient generates the address, and therefor the recipient has control over the type, not the payer. It is the payer who covers the network fees however. If your client has to pay people and wants to cut on network fees, he has to ask the recipients to provide a bech32 or a P2SH-P2WPKH address instead of a legacy P2PKH. If you client is receiving payments, he can use Armory to generate P2SH-P2WPKH addresses to reduce the fees his counterparties have to pay. |