Inconsistent DID format between connection events and records with didexchange/1.1
When creating a connection with handshake_protocols = ["https://didcomm.org/didexchange/1.1"], the events for the tenant that creates (initiates) the connection contain the "long-form" of the DIDs for the their_did and my_did fields.
However, the records from the GET /connections endpoint contain the "short-form" of the DIDs, and the events for the tenant that accepts the connection also contain the "short-form" of the DIDs.
The DIDs used for these connections default to did:peer:4.
Not sure if this is because of /didexchange/1.1 since /didexchange/1.0 used did:sov DIDs.
The expected behaviour from my point of view is that the DIDs in the events should be the same as the DIDs in the records.
Btw I noticed that the wallet lists the "long-form" and "short-form" DIDs as 2 different DIDS:
{
"did": "did:peer:4zQmQJczxttY1gn9nfnbotwQsqHDgFTQ2tSktRNRVcHx42Ts",
"key_type": "ed25519",
"metadata": {},
"method": "did:peer:4",
"posture": "wallet_only",
"verkey": "6TYzYJKM3QGVAtSxt8wt9oXGEFSTpvD8CqwAUNvTYs4y"
},
{
"did": "did:peer:4zQmQJczxttY1gn9nfnbotwQsqHDgFTQ2tSktRNRVcHx42Ts:z3qDm8hHPpgti6CKpyThg5iZH9rj7Z3Js6uCJpfmERaQ9ePKoNo5jgqEGLBeaT2bi6FtQUGYxxQUUWaygqhykrVcNDky4Gb5vwL7qap1BMqNvisEtEEUxdQDpZ2iTa2GWit9eLJZUXjA3cm2afTYNtyvaHYZnjMvKbWSfuiGRYBx3FhV8huVhDQ4t5phEXVqxaW9Rf7hU9nm1B4egNE4MrnTWthBqfm6nZQqQXPXBJyz9K8QBsdky8xDCv2Y5to1eVKr2bhDZCW1YuMXYNN9Jrfw3KMgXdnyYgf7JVXHwn66hbhUkuUT7z53zLpQsrfa5CxTpXfcraR2JjTGu8zywZ1eRkgMH2BhNq9frxAkzqqAXoN9oBpHLNZbh8DkXkqHwPu3PNcLpWQULbeNosFZAqPgYLKegGW9wqUjN6JSSy8Wmbhs8htNfQrc9TRq18oABNcMLfLQEr7VNxiKznf7Jm17um8BqZa1GFPn77bHS1Yu5FDj94ygZG7gXAKJGrQhNH34TSJbgA3kfS7qMs3T2UEKJjiyZpHSmPeFjuz1Ycbrenz3tYRuPgXJHX56f6xThr7TNTyHicU2oKYZZzzya",
"key_type": "ed25519",
"metadata": {},
"method": "did:peer:4",
"posture": "wallet_only",
"verkey": "6TYzYJKM3QGVAtSxt8wt9oXGEFSTpvD8CqwAUNvTYs4y"
}