# ERIP-6

```javascript
from: your wallet 
to: seller wallet 
value: sell price


interface Buy{
   p: string;
   op: string;
   tx: string;
}




```

<pre class="language-json"><code class="lang-json"><strong>//Example :
</strong>{
   "p": "era-20",
   "op": "buy",
   "tx": "7c0815f5b366e3d254fd9dfedf791e937512cd706bb8cf94f732c2616ebd8386",
}




</code></pre>

To list a token, the wallet must create an inscription transaction in accordance with the Buy interface .&#x20;

{% hint style="danger" %}
The amount sent (value) must be higher or equal to the price in the List inscripton code. Otherwise the transaction is considered failed.
{% endhint %}

{% hint style="danger" %}
In order for the protocol to work in a decentralized and free manner, the data is stored entirely on the blockchain. In buy operations, it is necessary to check whether a buy has been made before. If more than one buy operator is triggered for the same listing, the first incoming record is accepted. The values sent in subsequent requests cannot be reversed.
{% endhint %}

```javascript
// Types
"p" => Protocol
"op" => Operation
"tx" => List Transaction Id

```


---

# 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://bigint.gitbook.io/era-20/what-are-erips/erip-6.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.