# EIP-6492 Compatible Signatures

We now support EIP-6492 for verifying signatures of pre-deployed smart accounts, as a dev, you have to generate a signature that is EIP-6492 compliant, which will be sent as a normal signature to APIs

Below are the steps to make your normal signature EIP-6492 compliant

### Steps

1. Sign the message from that pre-deployed smart account's owner EOA

2. We will need few data along with signature for signature generation
   1. **Deploy Calldata** - Transaction data for deploying the smart account
   2. **Factory Address** - Smart account factory contract
   3. **Magic Suffix** - `6492649264926492649264926492649264926492649264926492649264926492`

3. Use `AbiCoder` in `ethers` for encoding all of the data

4. ```
   const signature = coder.encode(['address', 'bytes', 'bytes'], [
   ```

   ```typescript
       factoryAddress,
       calldata,
       signature
   ]) + magicSuffix
   ```

5. Use the generate signature in Fetcch API to authenticate tasks

### Reference

* [EIP-6492](https://eips.ethereum.org/EIPS/eip-6492)


---

# 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.fetcch.xyz/how-to-integrate/guides/utility/how-to-sign-messages/eip-6492-compatible-signatures.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.