Topic: wanting to use segwit (Read 279 times)
Thank you much, I'll continue reading up on the information provided.
Will armory be usable in the future with "payment protocol"?
Goatpig doesn't seem to be keen on Armory talking to various servers (he's removed all the "phone home" code that existed in previous versions), so I would doubt this.
See: https://bitcointalksearch.org/topic/m.27449925
I started looking into electrum, but noticed today the warning on the top of page to "SHUT DOWN ELECTRUM IMMEDIATELY"
Yes, there was a security issue and it was patched. I certainly don't recommend Electrum for savings, only for spending. Treat it like putting cash in your wallet when heading out to the grocery store. (Yes, this means paying an extra transaction fee for some number of future transactions. Actually, if you want to use segwit with Electrum, you will have to first fund a normal address, then use Electrum itself to transfer to its bech32 segwit addresses. If you do this intelligently, you can still save on those future segwit transactions, but it is certainly a lot of hoop jumping. I suspect Armory will eventually support bech32 and there will be one less hoop.)
User achow101 (https://bitcointalksearch.org/user/achow101-290195) has created a small program for interacting with the payment protocol and providing the user with the information required to do a typical Bitcoin transaction. I have not yet used this solution myself, perhaps he will respond here (if he reads this thread) and provide further information.
Here is the reddit thread: https://www.reddit.com/r/Bitcoin/comments/7n6oaa/annoyed_by_bitpays_exclusive_use_of_the_payment/
Edit: Please read this thread: https://www.reddit.com/r/Bitcoin/comments/7ntfv6/psa_how_to_get_address_from_bitpay_uri_now/
I was able to use core for some last minute Christmas purchases via the "payment protocol" didn't much care for that because had to uninstall armory because, well I don't know, couldn't make armory not my default client. Every time I'd try bitpay it would open armory. That was a mess and is over with now so back to using armory.
With the premium bitpay is charging to use the "payment protocol" on top of backlog of bitcoin network I'm just going to populate some segwit addresses and hodl. After I set up new wallets for segwit use, if I delete older wallets from armory does that merely make them paper wallets for cold storage, or is it acceptable to delete the keys and make a watch only wallet for monitoring purposes?
[/quote]
If you want to use a wallet that is compatible with both the payment protocol and segwit, electrum is your best option.
[/quote]
Will armory be usable in the future with "payment protocol"? I started looking into electrum, but noticed today the warning on the top of page to "SHUT DOWN ELECTRUM IMMEDIATELY"
With the premium bitpay is charging to use the "payment protocol" on top of backlog of bitcoin network I'm just going to populate some segwit addresses and hodl. After I set up new wallets for segwit use, if I delete older wallets from armory does that merely make them paper wallets for cold storage, or is it acceptable to delete the keys and make a watch only wallet for monitoring purposes?
[/quote]
If you want to use a wallet that is compatible with both the payment protocol and segwit, electrum is your best option.
[/quote]
Will armory be usable in the future with "payment protocol"? I started looking into electrum, but noticed today the warning on the top of page to "SHUT DOWN ELECTRUM IMMEDIATELY"
Doesn't make alot of sense to use the "protocol" at this point to ease pressure on the network, I see it as only adding to the congestion if you have to move funds before being able to spend. To me that is double downing on the backlog unless they are hoping peoples will export wallets. I did go ahead and and generate a couple addresses in core, but notice there is no option, that i can see to create segwit? Kind of self defeating when I was wanting to start using segwit, and wasn't that the point of the hardfork that spawned bch?
If you want to use a wallet that is compatible with both the payment protocol and segwit, electrum is your best option.
I did go ahead and and generate a couple addresses in core, but notice there is no option, that i can see to create segwit? Kind of self defeating when I was wanting to start using segwit, and wasn't that the point of the hardfork that spawned bch?
Core is enabling SegWit in their wallets starting in 0.16. There's a subtle difference between what Core enables on the network and what Core's wallet does. Honestly, Core's wallet has been subpar for awhile. They're working on getting it up to snuff. This includes enabling SegWit in their own proverbial backyard.
Thank you Holliday, for confirming it is incompatible and not issue elsewhere.
I agree, have no interest in using the wallets they suggest...also notice that trezor and ledger are not exactly compatible either.
Doesn't make alot of sense to use the "protocol" at this point to ease pressure on the network, I see it as only adding to the congestion if you have to move funds before being able to spend. To me that is double downing on the backlog unless they are hoping peoples will export wallets. I did go ahead and and generate a couple addresses in core, but notice there is no option, that i can see to create segwit? Kind of self defeating when I was wanting to start using segwit, and wasn't that the point of the hardfork that spawned bch?
I agree, have no interest in using the wallets they suggest...also notice that trezor and ledger are not exactly compatible either.
Doesn't make alot of sense to use the "protocol" at this point to ease pressure on the network, I see it as only adding to the congestion if you have to move funds before being able to spend. To me that is double downing on the backlog unless they are hoping peoples will export wallets. I did go ahead and and generate a couple addresses in core, but notice there is no option, that i can see to create segwit? Kind of self defeating when I was wanting to start using segwit, and wasn't that the point of the hardfork that spawned bch?
i've upgraded core and armory to 0.15.1 and 0.96.4 RC1. Up until yesterday haven't had any issues, what is up with bitpays "payment protocol" When I click on the "open in wallet" to make a bitpay bitcoin payment it acts like it opens but then disappears. I've tried the manual enter of url, but doesn't seem to work either. I've shut down armory and the "open in wallet" link will launch armory, but thats it won't fill out the address? Is armory not compatible with this protocol or do I have a problem with my install or window10?
BitPay has decided to enforce the "Bitcoin Payment Protocol" on all their invoices. You need a wallet which supports it, Armory does not. You can use Core, Electrum, Mycelium, or Copay.
I think using any of these wallets as your main wallet is a mistake, so I've created a "spending wallet" for myself which I will fund with Armory when I need to make a payment on a vendor which uses BitPay. I think it was a mistake on BitPay's part, yet their service has been going to shit lately anyway so I expect their competitors are fine with it. I will be sending emails to the vendor with every purchase complaining about the requirement.
i've upgraded core and armory to 0.15.1 and 0.96.4 RC1. Up until yesterday haven't had any issues, what is up with bitpays "payment protocol" When I click on the "open in wallet" to make a bitpay bitcoin payment it acts like it opens but then disappears. I've tried the manual enter of url, but doesn't seem to work either. I've shut down armory and the "open in wallet" link will launch armory, but thats it won't fill out the address? Is armory not compatible with this protocol or do I have a problem with my install or window10?
Thanks, I just read through the 0.96.3.99/0.96.4 RC1 thread and sounds like a new release is soon, so i'll wait before upgrading. In meantime i'll create a couple P2SH-P2WPKH address just to test out.
Unless you are worried it is compromised, you can continue to use your current wallet for segwit.
Ideally, you'll want Armory 0.96.3.99/0.96.4 RC1 and then change your preferences to use P2SH-P2WPKH (Segwit) in Armory. Change address too, perhaps but that is up to you regarding privacy.
I don't think upgrading Core is required, but the node rpc does need to be running on your full node. Offline machines with 0.96.4 RC1 can force segwit availability with --force-enable-segwit.
Ideally, you'll want Armory 0.96.3.99/0.96.4 RC1 and then change your preferences to use P2SH-P2WPKH (Segwit) in Armory. Change address too, perhaps but that is up to you regarding privacy.
I don't think upgrading Core is required, but the node rpc does need to be running on your full node. Offline machines with 0.96.4 RC1 can force segwit availability with --force-enable-segwit.
Everything is running smoothly for me. I'm running Armory 0.96.1 with bitcoin 0.14.2. I want to create a new wallet to start using segwit. All my bitcoin are in P2PKH addresses, so to use segwit which addresses should I create to receive in Armory: P2SH-P2PK or P2SH-P2WPKH. I am also wondering to use segwit if I should upgrade core to 0.15.1 and Armory to which version???
Jump to: