> For the complete documentation index, see [llms.txt](https://docs.ston.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ston.fi/developer-section/omniston/sdk/evm/evm-signature.md).

# EVM Signature

This document explains how to choose the correct EVM signature format when sending signed data to Omniston.

In the EVM flow, signatures are passed to Omniston in two places:

* as the permit signature inside allowance data
* as the final order signature

For the explanation of wallet kinds themselves, see [EVM Wallet kind](/developer-section/omniston/sdk/evm/evm-wallet-kind.md).

## Why wallet kind matters

Different EVM wallet kinds do not always use the same signature representation for the final order signature.

Because of that, the signature bytes sent to Omniston for the order must be formatted according to the wallet kind that produced the signature.

## Signature formats used by Omniston

Omniston uses two signature shapes:

* compact 64-byte signature
* raw 65-byte signature

The correct one must be chosen based on where the signature is used.

## Where Signatures Are Sent To Omniston

### Permit signature

This is used only when the allowance method includes an off-chain permit, such as:

* `EIP-2612`
* `Permit2`

For permit signatures, the signature sent to Omniston must always be raw 65-byte.

This does not change based on wallet kind.

### Order signature

This is the final signature of the EVM order itself.

For order signatures, the required signature format depends on wallet kind.

| Wallet kind     | Order signature format to send to Omniston |
| --------------- | ------------------------------------------ |
| EOA             | compact 64-byte                            |
| Delegated EOA   | compact 64-byte                            |
| Contract wallet | raw 65-byte                                |


---

# 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.ston.fi/developer-section/omniston/sdk/evm/evm-signature.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.