# ERC721Permit

## ERC721Permit

ERC721 with permit Nonfungible tokens that support an approve via signature, i.e. permit

### Variables

#### bytes32 PERMIT\_TYPEHASH constant

The permit typehash used in the permit signature

*Developer note: Value is equal to keccak256("Permit(address spender,uint256 tokenId,uint256 nonce,uint256 deadline)");*

### Functions

#### DOMAIN\_SEPARATOR

`DOMAIN_SEPARATOR()` view public

The domain separator used in the permit signature

**Returns:**

| Name | Type    | Description |
| ---- | ------- | ----------- |
| \[0] | bytes32 |             |

#### permit

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

Approve of a specific token ID for spending by spender via signature

| Name     | Type    | Description                                                                       |
| -------- | ------- | --------------------------------------------------------------------------------- |
| spender  | address | The account that is being approved                                                |
| tokenId  | uint256 | The ID of the token that is being approved for spending                           |
| deadline | uint256 | The deadline timestamp by which the call must be mined for the approve to work    |
| 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\` |

***

## ERC721Permit

ERC721 with permit Nonfungible tokens that support an approve via signature, i.e. permit

### Variables

#### bytes32 PERMIT\_TYPEHASH constant

The permit typehash used in the permit signature

*Developer note: Value is equal to keccak256("Permit(address spender,uint256 tokenId,uint256 nonce,uint256 deadline)");*

### Functions

#### DOMAIN\_SEPARATOR

`DOMAIN_SEPARATOR()` view public

The domain separator used in the permit signature

**Returns:**

| Name | Type    | Description |
| ---- | ------- | ----------- |
| \[0] | bytes32 |             |

#### permit

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

Approve of a specific token ID for spending by spender via signature

| Name     | Type    | Description                                                                       |
| -------- | ------- | --------------------------------------------------------------------------------- |
| spender  | address | The account that is being approved                                                |
| tokenId  | uint256 | The ID of the token that is being approved for spending                           |
| deadline | uint256 | The deadline timestamp by which the call must be mined for the approve to work    |
| 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: 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.algebra.finance/algebra-integral-documentation/algebra-v1-technical-reference/contracts/api-reference-v1.0/v1.0-periphery/erc721permit.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.