Starknet Tokenbound
  • Starknet Tokenbound
    • Introduction to Tokenbound
    • 📘Glossary
    • 💡Frequently Asked Questions
  • SDK
    • Installation
    • ⚡API Reference
  • Toolings
    • 🔗Tokenbound Connectkit
    • 🖼️Tokenbound iFrame
  • Contracts
    • AccountV3
    • Registry
    • Components
      • 📔Account
      • 🔒Lockable
      • Permissionable
      • ✍️Signatory
      • Upgradeable
    • 📔Deployed Addresses
Powered by GitBook
On this page
  1. Starknet Tokenbound

Glossary

PreviousIntroduction to TokenboundNextFrequently Asked Questions

Last updated 4 months ago

This page lists all of the terms and their definitions that are used in these docs. Consider these as the building blocks of the Tokenbound Accounts system.

TBA

Short for Tokenbound Account. This is the account associated with a particular NFT. An NFT on a particular chain is uniquely identified as a contract address and tokenId pair. For example, one ERC721 contract can have multiple unique token IDs associated with it, and each tokenId will have a unique account associated with it. A TBA isn't generated, it's calculated. The address is deterministic and is calculated based on the NFT contract, the ID of the token and the implementation

Registry Contract

The presence of a on a particular chain makes it possible for that chain to support TBAs. This contract holds the method to calculate the address of a given NFT (contract, tokenID pair)

Account

Implementation of the .

TBA Explorer

We built the to provide a way for anyone to view the wallet associated with any NFT.

📘
Account
registry contract
Tokenbound Account
tokenbound explorer