# Wallets support v3

**URL:** https://community.blockcerts.org/t/wallets-support-v3/3057
**Category:** Support
**Created:** [January 21, 2022, 5:20pm UTC](https://community.blockcerts.org/t/wallets-support-v3/3057 "2022-01-21T17:20:12Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![6eer](https://sea2.discourse-cdn.com/flex016/user_avatar/community.blockcerts.org/6eer/32/786_2.png) [@6eer](https://community.blockcerts.org/u/6eer)
#### Post date: [January 21, 2022, 5:20pm UTC](https://community.blockcerts.org/t/wallets-support-v3/3057/1 "2022-01-21T17:20:13Z")

</div>

Hi, 6eer here.

I have been using and exploring blockcerts v3 these past two week and i could issue a couple of certificates and verify them without problem.

Now im triying to use the wallets, i could add an issuer but im having troubles to add the v3 credentials, it gives me an invalid credential error. Are the wallets v3 compatible? and if not, are u planing to do so?

thanks,  
6eer.

PS: almost forgot it, in the verification process it is not verificated that the holder is the real ownership of the cert (aka that if he/she owns the private key associated with the pubkey on the cert), is this verificated at some point?

thanks again,  
6eer.

---

<div class="post-metadata">

### Author: ![lemoustachiste](https://avatars.discourse-cdn.com/v4/letter/l/7c8e57/32.png) [@lemoustachiste](https://community.blockcerts.org/u/lemoustachiste)
#### Post date: [January 24, 2022, 8:11am UTC](https://community.blockcerts.org/t/wallets-support-v3/3057/2 "2022-01-24T08:11:26Z")

</div>

Hi 6eer,

thanks for your feedback.

I think you should be able to hold the v3 certs in the wallet, but indeed I am not sure the verification code is up to date in the wallet apps, which may be why you are seeing this error. Just for my own knowledge, are you using DIDs with the certs?

The process to update the wallets at this moment is a bit convoluted and requires a third party to publish the app to the different stores. Again, for my own knowledge, which version are you running (Android or iOS)?

You are correct that at this point the wallet does not check identity/ownership of the holder. It’s something that’s on our roadmap to improve and I believe we should have something this year. As part of the next update I will try and push for a temporary fix, making sure the public key of the recipient is matching the wallet’s key, but further down the line I think using did:key might be a better approach.

I am happy to assist you in successfully setting up blockcerts v3. At this moment it has been developed with our use case in mind, but the more use cases are brought, the better we can define the standard and toolings, so please don’t hesitate if you find other friction points.

---

<div class="post-metadata">

### Author: ![6eer](https://sea2.discourse-cdn.com/flex016/user_avatar/community.blockcerts.org/6eer/32/786_2.png) [@6eer](https://community.blockcerts.org/u/6eer)
#### Post date: [January 24, 2022, 10:35am UTC](https://community.blockcerts.org/t/wallets-support-v3/3057/3 "2022-01-24T10:35:34Z")

</div>

lemoustachiste,

thanks to you for your reply.

No, currently im using the url method but i wanna switch to the did (probably this week ill make the try).

And Im using the iOS wallet.

Here is a copy of the issuer profile that currently i have hosted.

> <https://github.com/6eer/stunning-chainsaw/blob/main/issuer.json>

And this is the cert that im trying to import to the wallet

> <https://github.com/6eer/stunning-chainsaw/blob/main/88006ca1-4591-4c95-9d00-82bdeeaacee7.json>

Do u see something wrong or missing?

thanks,  
6eer.

update: in android wallet have the same issue (can import the issuer but not the cred.).

---

<div class="post-metadata">

### Author: ![lemoustachiste](https://avatars.discourse-cdn.com/v4/letter/l/7c8e57/32.png) [@lemoustachiste](https://community.blockcerts.org/u/lemoustachiste)
#### Post date: [January 24, 2022, 1:10pm UTC](https://community.blockcerts.org/t/wallets-support-v3/3057/4 "2022-01-24T13:10:59Z")

</div>

is this the error message you are seeing?

 ![Screenshot_20220124-140902](https://us1.discourse-cdn.com/flex016/uploads/blockcerts/original/1X/5d68bcc5b7cab538c750e6e1482b859784d1f7ec.jpeg)

---

<div class="post-metadata">

### Author: ![lemoustachiste](https://avatars.discourse-cdn.com/v4/letter/l/7c8e57/32.png) [@lemoustachiste](https://community.blockcerts.org/u/lemoustachiste)
#### Post date: [January 24, 2022, 1:14pm UTC](https://community.blockcerts.org/t/wallets-support-v3/3057/5 "2022-01-24T13:14:14Z")

</div>

I have tested with another v3 cert and still getting an error, I’ll investigate

---

<div class="post-metadata">

### Author: ![6eer](https://sea2.discourse-cdn.com/flex016/user_avatar/community.blockcerts.org/6eer/32/786_2.png) [@6eer](https://community.blockcerts.org/u/6eer)
#### Post date: [January 24, 2022, 1:20pm UTC](https://community.blockcerts.org/t/wallets-support-v3/3057/6 "2022-01-24T13:20:28Z")

</div>

yes! (and importing with url gives me an error too)

---

<div class="post-metadata">

### Author: ![lemoustachiste](https://avatars.discourse-cdn.com/v4/letter/l/7c8e57/32.png) [@lemoustachiste](https://community.blockcerts.org/u/lemoustachiste)
#### Post date: [January 25, 2022, 12:15pm UTC](https://community.blockcerts.org/t/wallets-support-v3/3057/7 "2022-01-25T12:15:36Z")

</div>

Ok so the wallet does not work with V3 at this moment. We’re going to fix this but like I said this goes through a third party (a dependency we’ll be working on removing), so I don’t have an ETA for the fix, but it has become a priority.

---

<div class="post-metadata">

### Author: ![lemoustachiste](https://avatars.discourse-cdn.com/v4/letter/l/7c8e57/32.png) [@lemoustachiste](https://community.blockcerts.org/u/lemoustachiste)
#### Post date: [January 25, 2022, 12:16pm UTC](https://community.blockcerts.org/t/wallets-support-v3/3057/8 "2022-01-25T12:16:18Z")

</div>

I hope to see this out before the end of february
