# 3.8 Fragmentation

Fragmentation can also occur within the BRC20 ecosystem itself, particularly in relation to the ordinals (unique identifiers) assigned to BRC20 tokens. As the number of BRC20 tokens increases, the ordinal space may become fragmented, leading to challenges in token identification and compatibility.

1. <mark style="color:purple;">**Ordinal Space Limitations:**</mark> The BRC20 protocol assigns unique ordinals to each token to ensure their distinct identification. However, there is a finite space for ordinals, and as more tokens are created, the available space can become fragmented. This fragmentation can make it challenging to maintain a standardized and consistent identification system for all BRC20 tokens.
2. <mark style="color:purple;">**Token Compatibility:**</mark> Fragmentation in the ordinal space can result in compatibility issues between different platforms and applications that support BRC20 tokens. For example, if two platforms use different ordinal ranges or have overlapping ordinals, it may cause conflicts when attempting to interact with tokens across these platforms. This fragmentation hampers interoperability and smooth token transfers between different ecosystems.
3. <mark style="color:purple;">**Addressing Fragmentation:**</mark> To address fragmentation on the BRC20 ordinals, it is crucial to establish coordination and standardization efforts within the BRC20 ecosystem. Collaboration among token issuers, developers, and platform providers can help establish best practices and guidelines to ensure efficient use of the ordinal space and minimize fragmentation.
4. <mark style="color:purple;">**Upgrading the Protocol:**</mark> Another approach to mitigate fragmentation is through upgrades to the BRC20 protocol itself. By introducing enhancements to the token identification and management system, the protocol can accommodate a larger number of tokens and reduce the potential for fragmentation in the ordinal space. However, protocol upgrades must be carefully implemented to maintain backward compatibility and avoid disruptions to existing token ecosystems.


---

# Agent Instructions: 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:

```
GET https://brc-20-dex.gitbook.io/brc-20dex/3.8-fragmentation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.