# DLT Token Standard (ERC-6960)

<mark style="color:purple;">**Enter ERC-6960.**</mark> A token standard designed by our team at Polytrade to represent Real-World Assets (RWAs) and support fractional ownership.

{% embed url="<https://eips.ethereum.org/EIPS/eip-6960>" fullWidth="false" %}
DLT Standard Proposal
{% endembed %}

{% embed url="<https://github.com/polytrade-finance/dual-layer-token>" %}
DLT Standard Implementation
{% endembed %}

The existing token standards lack the ability to support fractional ownership of both fungible and non-fungible tokens. While ERC-6150 is an extension of ERC-721 that standardizes an interface for the hierarchical representation of NFTs in a tree-like structure, its implementation is limited to NFTs only. This highlights the need for a more comprehensive standard that provides the same features as ERC-1155 but with added flexibility and support for hierarchical representation and fractional ownership.

<figure><img src="/files/9fG2VaLYir1sAJjFRxfB" alt=""><figcaption></figcaption></figure>

If we take an invoice as an example, in a token-based economy, it can be tokenized and fractionalized for investors to own. By implementing the dual-layer token standard, a `mint` function assigns an owner to a fraction worth a certain amount by taking the following values:

* wallet address of buyer or investor&#x20;
* main Id of invoice&#x20;
* sub Id of the invoice fraction&#x20;
* amount of the invoice fraction&#x20;

**The standard can be implemented in many more cases and on many different kinds of real-world assets which reflects its flexibility and robust design.**


---

# 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://polytrade.gitbook.io/rwa-marketplace/features/dlt-token-standard-erc-6960.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.