> For the complete documentation index, see [llms.txt](https://rhys-nemo.gitbook.io/tokenomics-bible/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rhys-nemo.gitbook.io/tokenomics-bible/protocols-and-utility/cardinal.md).

# Cardinal

![](/files/j2fjrpDkyP4SfCrKYTDK)

**Example use cases**

Revoking NFT ownership - specify a 'manual revocation authority' that can revoke an issued token (ie force a wallet to return an NFT)

Time-based expiry - Specify a duration/fixed expiration date after which an token can be revoked

Use-based expiry - Ticket like behaviour (specific number of uses before a token is revoked)

Data-based expiry - Revoke an NFT based on external data (ie reading from an oracle/external data)

Selective transferability - Token can only be transferred to specific wallets 

Non transferability - token is locked to a wallet & can not be traded via SPL token transfer 

**Facilitates:**

* rental agreements
* loans
* tickets
* domain names
* gaming items
* certifications
* credentials
* badges<br>

**How:**

* Wrapping traditional NFTs
* Mechanism for Revocation
* Time use
* Data-based expiry&#x20;
* Explosion
* Selective
* Non-transferability

The Data is stored in the account key - not the actual mint ID itself\
\
Utility - Rentals, subscriptions, staking, tickets ect<br>

### Identity UI

twitter.cardinal.so<br>

### Token manager UI (P2p rentals)

{% embed url="<https://github.com/cardinal-labs/cardinal-token-manager-ui>" %}

### Staking UI

{% embed url="<https://github.com/cardinal-labs/cardinal-staking-ui>" %}

{% embed url="<https://www.cardinal.so/>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://rhys-nemo.gitbook.io/tokenomics-bible/protocols-and-utility/cardinal.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.