> For the complete documentation index, see [llms.txt](https://blockgram.gitbook.io/blockgram-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://blockgram.gitbook.io/blockgram-docs/about-blockgram/core-features/use-nft-avatars.md). # Use NFT Avatars **Web3 identity inside Telegram chats through verifiable digital ownership.**\ BlockGram enables users to set, display, and interact with NFT-based avatars directly within the Telegram interface. These avatars go beyond traditional profile images by embedding ownership, interactivity, and metadata on-chain, allowing users to bring their Web3 identity into everyday conversations. #### 1. Overview: What Are NFT Avatars in BlockGram? NFT avatars in BlockGram are tokenized digital identity representations stored on supported blockchains. Unlike static images, NFT avatars are: * Verifiably owned through blockchain token standards (ERC-721 or ERC-1155) * Capable of embedding metadata, animation, and interactivity * Used as visual identity, status symbols, or access tokens across different use cases Users can configure NFT avatars to replace or augment their Telegram profile pictures. Display is opt-in and visible to participants in chats and groups that support the feature. #### 2. Avatar NFT Integration Pipeline | Layer | Function | | ------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | | Ownership Verification | BlockGram scans connected wallets for eligible NFTs via on-chain indexing protocols such as The Graph | | Media Rendering | Supports formats including PNG, GIF, SVG, and 3D (GLTF). NFT metadata is resolved through IPFS, Arweave, or contract-hosted URIs | | Identity Binding | Users link their Telegram ID to a wallet address using EIP-4361 signature or a zk-based identity proof | | Real-Time Synchronization | Changes in NFT ownership or metadata are reflected in real time using caching, polling, or bot-based updates | #### 3. Standards and Compatibility **Supported Blockchains:** * Ethereum Mainnet * Polygon * Arbitrum * BNB Smart Chain * Solana (via bridge and metadata wrapper) **Supported Token Standards:** * ERC-721 * ERC-1155 * Custom metadata formats with animation\_url, external\_url, and attributes fields **Avatar Collections:** * Official collections are curated and verified by the BlockGram team * Community collections can be proposed and approved through token governance mechanisms #### 4. Technical Architecture **Avatar Rendering Flow:** 1. User connects a wallet via the BlockGram interface 2. NFTs are queried using a subgraph or direct RPC call 3. Metadata is fetched and decoded from the tokenURI field 4. Media is rendered either client-side or via a CDN-based preview renderer 5. The Telegram profile is updated using inline bot overlay features or custom extensions **Rendering Modes:** * Static image overlay for profile thumbnails * Animated previews (GIF, WebM) displayed in chat windows * Planned support for embedded 3D or interactive avatars using Telegram WebView components #### 5. Use Cases and Identity Layer Integration BlockGram leverages NFT avatars to enable programmable identity and access features: | Use Case | Implementation Details | | --------------------------- | -------------------------------------------------------------------------- | | DAO-Restricted Chats | Only wallets holding specified NFTs can join certain Telegram groups | | Status Tiers and Flair | Avatar frames or effects change based on rarity or staking level | | Event Credentials and POAPs | Special NFTs act as passes for group access or event verification | | Group Identity Badges | Members of NFT-based communities can wear group-specific avatars or badges | Users can manage multiple NFT avatars and switch between them using an avatar selector in the BlockGram wallet interface. #### 6. Security and Privacy Considerations * Displaying NFT avatars is fully optional and user-controlled * No public wallet address is shared unless explicitly authorized by the user * Media is served through access-controlled endpoints or local caching * Users may disable or revert to the default Telegram profile at any time #### 7. Key Benefits * Connects Web3 identity to everyday messaging * Enables visual self-expression backed by verifiable ownership * Supports social signaling, gated access, and NFT-powered community interactions * Enhances Telegram’s static identity layer with dynamic, on-chain personalization --- # 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, and the optional `goal` query parameter: ``` GET https://blockgram.gitbook.io/blockgram-docs/about-blockgram/core-features/use-nft-avatars.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.