# Human readable transactions

{% hint style="success" %}
Keeping **users informed.**
{% endhint %}

## How does it work?

A big part of Aragon is user-friendliness, and one of the most unfriendly things in the Ethereum world is transaction data.

Examine this screenshot of a transaction in MetaMask:

<figure><img src="/files/wvCfh2sspQFjgnlI1CMk" alt=""><figcaption><p>UTF8 string in MetaMask</p></figcaption></figure>

Would you know what this transaction does? Not even a developer could tell. This is why we created **Radspec**.

**Radspec is a secure alternative to Natspec**. Natspec was supposed to be a way to describe transactions from a Natspec *expression* and some transaction data.

The issue with Natspec, however, is that it is insecure. Any JavaScript can execute in Natspec which opens up a lot of potential attacks, like cross-site scripting, which might successfully phish users.

## How to use Radspec <a href="#how-to-use-radspec" id="how-to-use-radspec"></a>

It's as easy as adding `@notice` to functions in the smart contracts.

```solidity
contract Counter is AragonApp {
    /**
     * @notice Increment the counter by `step`
     */
    function increment(int step) auth(INCREMENT_ROLE) external {
        // ...
    }

    /**
     * @notice Decrement the counter by `step`
     */
    function decrement(int step) auth(DECREMENT_ROLE) external {
        // ...
    }
}
```

These Radspec expressions are **written in comments in your source code**, and they will be grabbed by `aragon` and bundled with your app.

The [Aragon client ](/developers/tools/the-basics/the-aragon-client.md)will display these *with* the transaction a user is about to perform so that they have a clear understanding of what they're about to sign.

<figure><img src="/files/eExX0wDMxouBg1YucROs" alt=""><figcaption><p>Screenshot of signer showing Radspec</p></figcaption></figure>

{% hint style="info" %}
Our Radspec expressions show up while signing a transaction.
{% endhint %}

Obviously, this is a super trivial example as we are not actually evaluating anything but we could instead write something more complex.


---

# 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://legacy-docs.aragon.org/developers/tools/the-basics/human-readable-transactions.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.