> For the complete documentation index, see [llms.txt](https://docs.decentraland.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decentraland.org/contributor/contributor-zh/nei-rong/file-system.md).
# 文件系统
Decentraland 协议中不同内容 API 的底层是一个分布式文件系统的实现。每个内容服务器都保存整个存储的一份副本，并将其接收到的更新与其他实例同步。
上传到系统的文件是 **不可变的**。一旦部署，它们的标识符和内容都不会改变。它们只能以这样的方式“更新”：上传一个新版本，由应用选择使用它，而旧版本可以被丢弃。
你可以在 [实践](https://github.com/decentraland/docs/tree/main/contributor/content/practice/README.md) 部分。
### 文件标识符
Decentraland 的文件系统组织为一个扁平索引（即不存在自然的目录层级），其中每个文件都由一个唯一字符串标识。
标识符字符串以前缀开头 [base32](https://en.wikipedia.org/wiki/Base32) 编码的文件内容 SHA-256 哈希，使用 [IPFS CID v1](https://docs.ipfs.tech/concepts/content-addressing/) 算法。它们看起来像这样：
```
bafybeicgclohdfaccu2sqqkzrzuenjxzcry3m5vcb4mpxgucjl3oheq5tq
```
前几个字节中的前缀指示标识符本身的编码、版本和哈希类型。
{% hint style="info" %}
出于历史原因，某些 API 将文件标识符称为 *哈希* 而不是 *id*，但它们指的是同一事物。你也可能在旧内容中找到看起来稍有不同的旧版标识符。
{% endhint %}
实际上，发现和下载内容并不需要这些细节。该协议的大多数客户端都可以把标识符视为不透明字符串，而不会失去任何功能。
请注意，现代 CIDv1 标识符与 IPFS 兼容，同一文件会得到相同的 CID，因此可以将 IPFS 作为文件提供方。
### 所有权与持久性
除 [快照](https://github.com/decentraland/docs/tree/main/contributor/content/snapshots/README.md)之外，存储在网络中的文件都关联到一个 [实体](https://github.com/decentraland/docs/tree/main/contributor/content/entities/README.md) ，该实体由一个以太坊账户拥有。只有所有者才被允许更新该实体及其相关文件。
协议要求内容服务器始终存储实体及其文件的最新版本，但可根据各自的配置选择是否保留旧版本。
### 下载文件
该 [`/contents/`](https://decentraland.github.io/catalyst-api-specs/#tag/Content-Server/operation/getContentFile) 内容服务器的端点可用于下载任何文件。它们的标识符位于父级 [实体的](https://github.com/decentraland/docs/tree/main/contributor/content/entities/README.md)清单。
### 上传文件
文件不能单独上传。相反，它们被打包在实体中，并在将实体部署到内容服务器时上传。
请参阅 [内容创建者文档](https://github.com/decentraland/docs/tree/main/creator/README.md) 了解更多详情。
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.decentraland.org/contributor/contributor-zh/nei-rong/file-system.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.