Text-Based Tokens (TBTs)

Overview

Text-Based Tokens (TBTs) are tokens with an embedded text record.

Every text-based token has a bonded Base64-encoded SVG output, which is embedded in the token’s metadata and stored entirely on blockchain rails. As a result, text-based tokens offer a fully blockchain-based solution for text records storage, eliminating the need for off-chain hosting services like IPFS.

• Data Encoding

• Data Architecture

---

Key Features

On-Chain Data Storage

Text-based tokens are generated, rendered, and stored entirely on-chain, ensuring the highest level of data integrity and provenance (i.e., immutability and permanence).

---

Composability

Composability is a key feature of text-based tokens.

On the one hand, the data of each text-based token is cryptographically stored on Ethereum, while on the other, it can be effortlessly accessed at any time and managed as an SVG file. This duality allows text-based tokens to serve as both immutable, permanent blockchain records and highly composable data files.

---

Multilingual

Text-based tokens support the use of text from all of the world's digitized writing systems, whether it’s Japanese, Arabic, Russian, Korean, or Chinese.

---

Input Functions

Text-based tokens contain two input text functions: Token Text and Metadata Text.

For a deeper understanding of Input Functions, refer to Data Layering and Data Structure.

Token Text

The text record inserted into the token SVG output.

The Token Text input function allows the insertion of a text record into a token's SVG output.

---

Metadata Text

The text record inserted into the token metadata, stored within its SVG file.

The Metadata Text input function allows the insertion of a text record bonded to a token's metadata, which is stored within its SVG file.

Text records entered through the Token Text input function are encapsulated within the token's tokenURI metadata and encoded in Base64. In contrast, text records inserted via the Metadata Text input function are stored in the token's tokenURI metadata as plain text. This enables, for example, the inclusion of a JSON file within the token's metadata, which is stored inside its SVG file. Since JSON is a universal format, users can leverage the Metadata Text function to add structured attributes and properties, facilitating composability with non-blockchain (or "off-chain") systems.

Example

{
  "name": "Token 7632",
  "symbol": "D7632",
  "text": "Token 7632 - 2025-01-10\n  - \n  Lorem ipsum dolor sit amet. Et ipsa \n  dolores cum suscipit dolorum est \n  quaerat laudantium eos dolor labore\n  ut perspiciatis reprehenderit ab \n  accusamus dolor. Et cupiditate\n  accusantium sed aliquam numquam\n  et maiores unde." 
}