> For the complete documentation index, see [llms.txt](https://docs.algebra.finance/algebra-integral-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.algebra.finance/algebra-integral-documentation/algebra-v1-technical-reference/contracts/api-reference-v1.0/v1.0-periphery/ierc20permitallowed.md).

# IERC20PermitAllowed

## IERC20PermitAllowed

Interface for permit Interface used by DAI/CHAI for permit

### Functions

#### permit

`permit(address,address,uint256,uint256,bool,uint8,bytes32,bytes32)` external

Approve the spender to spend some tokens via the holder signature

| Name    | Type    | Description                                                                       |
| ------- | ------- | --------------------------------------------------------------------------------- |
| holder  | address | The address of the token holder, the token owner                                  |
| spender | address | The address of the token spender                                                  |
| nonce   | uint256 | The holder's nonce, increases at each call to permit                              |
| expiry  | uint256 | The timestamp at which the permit is no longer valid                              |
| allowed | bool    | Boolean that sets approval amount, true for type(uint256).max and false for 0     |
| v       | uint8   | Must produce valid secp256k1 signature from the holder along with \`r\` and \`s\` |
| r       | bytes32 | Must produce valid secp256k1 signature from the holder along with \`v\` and \`s\` |
| s       | bytes32 | Must produce valid secp256k1 signature from the holder along with \`r\` and \`v\` |

***

## IERC20PermitAllowed

Interface for permit Interface used by DAI/CHAI for permit

### Functions

#### permit

`permit(address,address,uint256,uint256,bool,uint8,bytes32,bytes32)` external

Approve the spender to spend some tokens via the holder signature

| Name    | Type    | Description                                                                       |
| ------- | ------- | --------------------------------------------------------------------------------- |
| holder  | address | The address of the token holder, the token owner                                  |
| spender | address | The address of the token spender                                                  |
| nonce   | uint256 | The holder's nonce, increases at each call to permit                              |
| expiry  | uint256 | The timestamp at which the permit is no longer valid                              |
| allowed | bool    | Boolean that sets approval amount, true for type(uint256).max and false for 0     |
| v       | uint8   | Must produce valid secp256k1 signature from the holder along with \`r\` and \`s\` |
| r       | bytes32 | Must produce valid secp256k1 signature from the holder along with \`v\` and \`s\` |
| s       | bytes32 | Must produce valid secp256k1 signature from the holder along with \`r\` and \`v\` |

***


---

# 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.algebra.finance/algebra-integral-documentation/algebra-v1-technical-reference/contracts/api-reference-v1.0/v1.0-periphery/ierc20permitallowed.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.
