<blockquote>
<p>Use case to fill would be: &quot;I receive an NFT (a long time after his mint) and I really want to verify that I am the issuer&quot;.</p>
</blockquote>
<p>This is not a realistic use case. If the policy ID listed when you query a Cardano wallet matches the string of a policy ID that you minted in the past, then it is verified. There's no way to send someone a token that has a policy ID without being signed by your skey, so there would be no possible way to spoof it, and therefore no need to 'verify' it using a key in the future.</p>
<p>EDIT: In re-reading your post, maybe I am misunderstanding.. Are you saying you'd prefer to not keep a record of the policy ID strings you've minted in the past? It seems like just creating a text file that stores all of your policy IDs would be the same effort as keeping the .vkey or .skey's from past policies..</p>

CC BY-SA 4.0
2022-03-06T22:44:16.063Z
Yes, your Edit is correct. we do not want to keep track of any policy ID we generated. In our mind, if our pub key was public anyone could verify the policy on their own without us involved. It is more for others than us. You know we had in mind the very similar way people are verifying today jwt with jwks/well-known open to anyone (oauth2). Anyway you seem to confirm that there is no way unfortunately to avoid storing them which is a bit sad. Thanks.
Ben Wolf
CC BY-SA 4.0
2022-03-01T13:11:48.857Z
2022-03-01T13:17:46.133Z
2022-03-01T13:17:46.133Z
Tygar Pool
<p>Is there any way to verify a policy against a policy.vkey (or even policy.skey in my case).</p>
<p>Thing is we would prefer to not store on external backend all of our NFT policies.</p>
<p>Use case to fill would be: &quot;I receive an NFT (a long time after his mint) and I really want to verify that I am the issuer&quot;.</p>
<p>Thanks!</p>

<policy><mint>
Verifying policy id from pub key
# Verifying policy id from pub key

(Asked by: username_0 on 2022-03-01)

Is there any way to verify a policy against a policy.vkey (or even policy.skey in my case).

Thing is we would prefer to not store on external backend all of our NFT policies.

Use case to fill would be: "I receive an NFT (a long time after his mint) and I really want to verify that I am the issuer".

Thanks!

**Tags:** policy, mint

---

## 1 answers

### Answer by username_1 on 2022-03-01. Score: 0

> Use case to fill would be: "I receive an NFT (a long time after his mint) and I really want to verify that I am the issuer".

This is not a realistic use case. If the policy ID listed when you query a Cardano wallet matches the string of a policy ID that you minted in the past, then it is verified. There's no way to send someone a token that has a policy ID without being signed by your skey, so there would be no possible way to spoof it, and therefore no need to 'verify' it using a key in the future.

EDIT: In re-reading your post, maybe I am misunderstanding.. Are you saying you'd prefer to not keep a record of the policy ID strings you've minted in the past? It seems like just creating a text file that stores all of your policy IDs would be the same effort as keeping the .vkey or .skey's from past policies..

> **Comments:**
> **username_0**: Yes, your Edit is correct. we do not want to keep track of any policy ID we generated. In our mind, if our pub key was public anyone could verify the policy on their own without us involved. It is more for others than us. You know we had in mind the very similar way people are verifying today jwt with jwks/well-known open to anyone (oauth2). Anyway you seem to confirm that there is no way unfortunately to avoid storing them which is a bit sad. Thanks.  

---

