> For the complete documentation index, see [llms.txt](https://dealin-1.gitbook.io/dealin/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dealin-1.gitbook.io/dealin/protocol-layer/data-separation-of-assets-and-contracts.md).

# Data Separation of Assets and Contracts

The storage of homogeneous and non-homogeneous assets and smart contract data on the chain is separated.
\
Dealin There will be a large number of continuous transactions in the network, and the operation cost of asset analysis and circulation needs to be reduced as far as possible. The separation of assets and contracts can realize the separate analysis execution of contracts and the operation of necessary results.
\
Under the design of separating the asset and the contract data storage, the owner of the asset has all the licensing rights of the asset, and the operation of the asset can only be completed by the authorization of the owner. It can avoid the destruction of asset attributes or the calling of other assets by modifying the contract content of assets due to the non-separation of asset contract, and it is easier to realize the cross-chain acceptance of non-homogeneous assets without considering the restriction of contract factors. Therefore, the separation of assets and contract is a safer design.


---

# 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://dealin-1.gitbook.io/dealin/protocol-layer/data-separation-of-assets-and-contracts.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.