> For the complete documentation index, see [llms.txt](https://docs.escher.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.escher.finance/key-features/authz-paymaster.md).

# Authz (Paymaster)

Authz is a permission framework that we grant to the ICA account and the liquidity contract, enabling them to perform specific functions on behalf of the user.

* **ICA Account Permissions**:
  * **Stake**: Allows the ICA account to stake tokens securely on the user’s behalf.
  * **Unbond**: Enables the ICA account to unbond staked tokens as requested by the user.
* **Liquidity Contract Permissions**:
  * **Restake**: The liquidity contract is authorized to restake tokens automatically, optimizing yield without user intervention.

By granting these specific permissions, Authz ensures secure and efficient operations while maintaining control over defined actions. This structured approach enhances the user experience, allowing for automated staking processes and seamless asset management across various chains.\
\
Read more about Authz module [here](https://docs.cosmos.network/v0.46/modules/authz/).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.escher.finance/key-features/authz-paymaster.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.