Can I still use core v0.13.2 and Armory 0.95.1?

[mtx3298]

I have an obviously old setup that I have not used in many years.  Bitcoin Core 0.13.2 appears to sync the blockchain and is up to date.  Armory 0.95.1 starts and scans fine, shows a balance , past transactions, and says it is online.  Everything "looks" good.  The question is can I still reliably send bitcoins?  Are these core and Armory versions still compatible with todays blockchain and network?

I ask because I had a similar situation with Litecoin, although there I was running a much older version of Litecoin Core.  In that case I tried sending some litecoins and they got hung up and the transaction was never recognized and it messed up my core wallet.  I had to update to the newer core and use a backup of my wallet.

So I don't really want to "just try it".  Also with all the issue I read here regarding the latest core + Armory + offline issues, I don't want to fight an update unless I really have to.

So, will core v0.13.2 and Armory 0.95.1 still actually work and send/receive bitcoins o.k.?

Thanks

[mtx3298]

Still looking into this, but I suspect the answer is yes and no, and leaning mostly towards no.  I think the versions I have will work fine if I want to send to a legacy address (starting with 1).  I don't think either versions support SegWit.  If I understand that correctly, that means I can't send to a SegWit address (starting with either a 3 or bc1).  Since most receivers will likely want to use a SegWit address, that would mean I could not send to them.  I do believe I could still receive from a SegWit address to my legacy address.

So I suspect I have two choices.  Either update my core/Armory to support SegWit, or start a new wallet (say core 0.20.1) on another machine and send from my Armory legacy address to a legacy address on the core 0.20.1.  Although it seems that you can't easily generate a legacy receive address with the newer Bitcoin core...

[goatpig]

I can't send to a SegWit address (starting with either a 3 or bc1).

Armory detects this, it will grey out segwit addresses at creation. You cannot use Armory to create segwit addresses under these conditions, but you can send to nested segwit regardless (addy starting with 3).

Still looking into this, but I suspect the answer is yes and no,

The DB can handle it, the underlying file format and the P2P layer are compatible. RPC will be busted most likely, which degrades the utility somewhat, but it's not a deal breaker. You won't get fee estimates, Core status updates nor boardcast fallbacks.

[HCP]

Although it seems that you can't easily generate a legacy receive address with the newer Bitcoin core...

It's easy to generate any type of address in the latest version of Bitcoin Core... simply use the getnewaddress command in Bitcoin Core and use the "legacy" option for address_type

Code:

getnewaddress ( "label" "address_type" )

Returns a new Bitcoin address for receiving payments.
If 'label' is specified, it is added to the address book 
so payments received with the address will be associated with 'label'.

Arguments:
1. label           (string, optional, default="") The label name for the address to be linked to. It can also be set to the empty string "" to represent the default label. The label does not need to exist, it will be created if there is no label by the given name.
2. address_type    (string, optional, default=set by -addresstype) The address type to use. Options are "legacy", "p2sh-segwit", and "bech32".

Result:
"str"    (string) The new bitcoin address

Note that to provide the 2nd option (address_type), you must provide the 1st option (label), but it can be empty... so you can use:

Code:

getnewaddress "" "legacy"

And lastly, you can also set the "default" address type that Bitcoin Core will generate by using the -addresstype commandline parameter (or setting it in bitcoin.conf).