🟢Cardinal

Protocol on Solana that provides a tool belt smart contracts for conditional ownership of NFTs.

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

How:

• Wrapping traditional NFTs

• Mechanism for Revocation

• Time use

• Data-based expiry

• Explosion

• Selective

• Non-transferability

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

Identity UI

twitter.cardinal.so

Token manager UI (P2p rentals)

GitHub - solana-nft-programs/rental-ui: The UI deployment for rentals of NFTs on Solana. This interact directly with the token-manager protocolGitHub

Staking UI

GitHub - solana-nft-programs/staking-ui: The UI for staking NFTs on Solana.Staking UI can be treated as an admin interface for stake pools as well as a barebones end-user staking UIGitHub

https://www.cardinal.so/www.cardinal.so