# Trails

{% hint style="warning" %}
The Trails feature has been updated after version 0.0.10 to use Arweave only. 

Previous versions use Harmony network to store Trails names. This is deprecated.
{% endhint %}

Ricadian Fabric provides an easy way to upload documents and link them to Trails, which are similar to threads.

Trails hold comments, which are Arweave Transactions.

Trails can be linked to Ricardian Contracts and with it, to smart contracts.

Trails are useful for Audit Trails, for creating Asset-Referenced Tokens.

### Creating a  Trail

![Navigate to Trails by clicking on this icon](/files/xGxNF5S8CbirUBS8dGPt)

To upload something to a trail, Click Permaweb and Add the Comment.

![](/files/ikmJWdKljGU3uBBgj6cV)

### Uploading A Comment Transaction

![](/files/sPot6mZt82J5THgAZqAq)

* First you must add the name of the trail you want to comment on
* You can link a transaction, if you add a comment here, it will appear as a reply, otherwise you can add uploaded files!
* Comment is the message that will appear on the trail
* Type your Arweave password
* Click add comment to upload it.

#### Linked transactions

You can link any transaction uploaded via Ricardian Fabric. For leaving an audit trail for a treasury, PDF format would be the best.

{% hint style="info" %}
You will find legal contract templates that you can use as Ricardian contracts in Trails.
{% endhint %}

### Search

![](/files/IfNIgZUpxxEWcIamRhPR)

#### Actions

![Refresh, copy link or add comment](/files/HVCHrCZYJd5OFo2ydmmG)

#### Trails can be attached to a Ricardian Contract:

![When the trail is attached to a Ricardian, a link will appear on the contract ](/files/RPnuRgkoLNrnwo35PuHS)


---

# 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.ricardianfabric.com/guides/trails.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.