# Data Storage

The following built-in RPC functions are used to interact with the data storage mechanism of Lynx Core. These functions are built into the daemon and don't require any third party software or modules. All functions listed are supported by the Enterprise version of Lynx. The Professional version of Lynx will only support the fetch() function.&#x20;

For convenience, when interacting with the Lynx daemon, the help() command will provide additional detailed documentation for each storage related function. The included documentation is respective to the version of Lynx running.

## Definitions

<details>

<summary>Tenant</summary>

A user of data storage routines. In most cases, a tenant can be thought of as a traditional user account.

</details>

<details>

<summary>Asset</summary>

A digital file. While there may be file size, type, content, and format constraints on an asset, an asset is no more and no less than a digital file.

</details>

<details>

<summary>Store</summary>

[Copy an asset](/lynx-core/data-storage/store.md) to the Lynx blockchain. Storage is permanent. The file can not be edited or deleted after it has been placed. If uploading encrypted assets, the tenant is responsible for the retention of decryption keys.

</details>

<details>

<summary>Fetch</summary>

[Copy an asset](#fetch) from the Lynx blockchain to the hard drive. Their is no fee to copy an asset from the blockchain. A unique identifier is required to find the requested asset.

</details>

<details>

<summary>Authorize</summary>

Make it such that a tenant, when authenticated, can perform operations allowed for that tenant.

</details>

<details>

<summary>Authenticate</summary>

Authorized tenants [authenticate](/lynx-core/data-storage/auth.md) by providing appropriate credentials.

</details>


---

# 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://docs.getlynx.io/lynx-core/data-storage.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.
