The incorporates an entirely blockchain-based framework for the generation and lifecycle management of.
Instead of relying on IPFS or centralized servers for metadata storage and retrieval, XTBTA stores all relevant information — including the token’s visual representation — entirely within the Ethereum blockchain.
TBTs are visually rendered using SVG (Scalable Vector Graphics), encoded in Base64, and embedded in the smart contract’s metadata delivery. As a result, this ensures each token is fully self-contained, tamper-proof, and persistently accessible.
Key Features
Base64-Encoded SVG Outputs
TBTs utilize SVG to represent token visuals in a scalable, resolution-independent manner.
These SVG documents are programmatically generated and encoded in Base64. XTBTA proposes the encoding of each TBT's SVG output into a Base64 string that is embedded in a JSON object, which is itself Base64-encoded and returned as a tokenURI.
On-Chain Data Delivery
Each TBT implements the tokenURI() function as defined by the ERC-721 standard. However, unlike conventional implementations that return a pointer to external JSON metadata, TBTs contracts return a fully self-contained, Base64-encoded metadata object. This object includes the encoded SVG visual and any relevant descriptive fields — delivered entirely from within the smart contract; without the need for off-chain servers.
As a result, XTBTA ensures that front-ends, indexers, and explorers can interpret and render the token without accessing any external infrastructure.
Functionality
Through XTBTA, each token’s metadata is programmatically constructed and encoded directly within the smart contract. This approach ensures that all descriptive and visual elements — such as the token’s name, description, and image — are embedded on-chain in a self-contained format.
The following example illustrates the step-by-step process through which a token’s metadata is constructed, encoded, and prepared for delivery via the tokenURI function:
When the Base64-encoded JSON object is decoded, it reveals a JSON structure in which the "image" field contains another Base64-encoded string — representing an embedded SVG image.
Decoding the Base64 string found in the "image" field of the JSON metadata produces the XML markup that renders the SVG graphic associated with the token.
SVG Output
The XML code, once decoded, generates the final SVG output — a visual representation embedded in the token metadata.
Fundamentals
Immutability
All metadata, visuals, and descriptive content related to TBTs are embedded in Ethereum’s state at the time of contract deployment or token minting. This guarantees the permanence and non-repudiation of each token’s identity and attributes.
Reliability
By eliminating external storage endpoints, XTBTA avoids common points of failure such as broken links, misconfigured servers, or expired hosting plans. The on-chain-only model substantially reduces operational risk.
Transparency
TBTs are fully observable on-chain. Developers and end users can inspect all token attributes, metadata, and rendering logic directly via smart contract interfaces — enabling frictionless auditing and trustless attesting.
Censorship Resistance
TBTs access and visibility cannot be obstructed by third-party services or centralized infrastructure providers.
Data Longevity
As long as the Ethereum network persists, all TBTs data remains accessible and verifiable, ensuring digital persistence without reliance on third-party hosting or re-indexing services.
Auditability
All state changes, token interactions, and logic executions are recorded immutably on-chain. This enables verifiable and reproducible audits by any third party without requiring privileged access.
Attestability
Users and systems can cryptographically attest to the authenticity and provenance of TBTs based solely on their on-chain presence. This trustless verification model removes reliance on off-chain registries or authorities.
Composability
TBTs are designed to be both immutable blockchain records and highly composable data files. Their SVG-based structure allows them to be easily accessed and integrated into other applications or systems, facilitating seamless interoperability and reuse in various contexts.
On-Chain Data Storage
Through XTBTA, 100% of each token’s data is stored fully on-chain, ensuring immutability, transparency, and complete independence from external, off-chain data storage systems such as IPFS.
Below we provide a comparison table between on-chain vs. off-chain data storage:
Criteria
On-Chain Data Storage
Off-Chain Data Storage
Immutability
Fully immutable once minted; embedded in Ethereum state
Content is immutable (via content hash), but links can be changed by referencing new hashes
Availability
Guaranteed as long as the Ethereum network exists
Requires external pinning to ensure persistent availability
Censorship Resistance
Cannot be removed or blocked
Resistant to censorship, but depends on gateway access or node hosting
Reliability
No external dependencies or servers needed
Relies on external nodes and pinning services
Transparency
100% transparent and queryable via smart contracts
Metadata is viewable if hash is known, but less transparent in contract context
Performance
Fast read access on-chain; no external lookups
Requires external fetch, which may introduce latency
Auditability
Fully auditable and verifiable on-chain
Auditable if hash is on-chain, but file contents need off-chain verification
Data Longevity
Data lives as long as Ethereum does
Data longevity depends on pinning and external upkeep
