Cardinal
Search…
⌃K

Claiming a Token

Approval

When claiming a token, a user must present a valid claim receipt signed by the claim approver of the token (set by the issuer). A basic example of this is a paid claim approver that requires a one-time payment to claim the token.
Other types of claim approvers could involve more bespoke requirements such as approval from a KYC protocol, off-chain verification of a given user, or ownership of another NFT or utility token.
The token manager specifies a specific public key that can approve new claims, so new claim approvers can be built and customized as plugins to the Cardinal protocol. Please reach out if your use case requires a custom claim approver!
The protocol supports generating claim links of 3 types.
  • Public link
  • Permissioned link
  • Private link
Public/Permissionless links are the default for issuing tokens. When issued, it is posted on-chain, and anybody can subsequently view and claim it. Having permissionless links allows for building a rental marketplace where you can list a token for a given price and duration, and anybody can claim it provided they pay the listed fee.
Permissioned links are associated with a specific public key and can only be claimed by that wallet. This is a standard way to send a Cardinal-managed token to a specific person when you know their public key.
Private links, while similar to permissioned links, are different in the sense that the issuer does not know the recipient's public key beforehand. They allow the issuer to send a link to someone in a private context (i.e. over email) and be sure that only that desired recipient will be able to claim the token. This is useful for web2 integrations where the goal is to allow new users who may not yet have a wallet setup to claim these tokens.
Private links work by generating an ephemeral keypair that is embedded in the url and used as a one-time password to claim the token.