> For the complete documentation index, see [llms.txt](https://doc.cryptostone.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.cryptostone.org/introduction/07_digital_implementation_of_gemstone_uniqueness.md).

# 07 Digital Uniqueness

CryptoStone can consider various technical options to express the uniqueness of each gemstone. Fungible token structures, semi-fungible token structures, and composite token structures may all be possible, but the core objective of CryptoStone is for each gemstone to have a unique attribute combination and tokenId.

Therefore, gemstones in CryptoStone are represented as Gem NFTs with unique tokenIds and attribute combinations. This choice is not intended to emphasize a specific technical standard, but is the result of implementing the following functions.

| Implementation Requirement                              | Reason for Adopting NFT Structure                                           |
| ------------------------------------------------------- | --------------------------------------------------------------------------- |
| Need for a unique tokenId for each gemstone             | NFT structure is suitable for representing assets based on unique tokenIds. |
| Storage of different attributes for each gemstone       | tokenId-specific metadata and on-chain attribute structures are possible.   |
| Need for ownership transfer records                     | Standard NFT transfer and ownership recording are possible.                 |
| Representation of multiple stones within one collection | 12 stones can be distinguished through the stoneType attribute.             |
| Tracking of rarity and transaction history              | Provenance and rarity tracking for each NFT are possible.                   |

In other words, the Gem NFT structure in CryptoStone is not a means of creating image NFTs. It is a technical container for expressing the uniqueness and attribute-based asset nature of digital gemstones.


---

# 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://doc.cryptostone.org/introduction/07_digital_implementation_of_gemstone_uniqueness.md?ask=<question>&goal=<endgoal>
```

`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.