I have a wallet that was created via the vcx provisioning process.
libindy v1.6.2
libvcx off the master branch of evernym.
Protocol-version 1
Using the Sovrin test Network with the genesis file for it
The correct key is being used.
vcx uses a default storage type

As long as compatible versions of libindy and libvcx are used, the wallets are compatible. In fact, libvcx interactions are handled by calls to libindy library calls.

There are some things to know before using both libraries on the same wallet. The first is that libvcx is higher-level, so it abstracts and simplifies, making assumptions about things that are configurable in libindy. For example, the pool name is always pool1 in libvcx, so if you want to access the same pool with its corresponding wallets using libindy, you use that name.

By the way, for faster and probably better responses as questions get more technical, please post them in the Hyperledger RocketChat. Many of the devs that work on this stuff contribute. This question would have been appropriate in the indy-sdk channel there.

The problem I have is that I can provision a vcx agent with an older yet stable version but that is all I can do because I don’t have the necessary code and tools to continue from that point. So I thought that I could setup everything again with the later version of the code - which I could do but there were item not found errors in the creation of a connection.
That is why I hoped to use the older wallet.
Provisioning with the newer code to the vcx agency is not an option because of some or other fundamental messaging difference does not work with it’s endpoints.