> 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-wallet-kind.md).

# EVM Wallet kind

This document explains what EVM wallet kind means on EVM chains and why it matters for Omniston integrators.

## What is wallet kind

In this context, wallet kind means the type of EVM account that owns the order and produces signatures in the swap flow.

This matters because EVM accounts are not all validated in the same way:

* some accounts are regular user accounts controlled directly by a private key
* some accounts still behave like user accounts for signing purposes, but the signing is routed through delegation infrastructure
* some accounts are smart contracts, so signature validation follows contract-wallet rules

For Omniston, wallet kind affects:

* which allowance methods are compatible with the wallet
* how the final order signature must be encoded

## Supported wallet kinds

### EOA (Externally owned account)

This is a regular externally owned account.

Typical properties:

* controlled by a private key
* signs messages directly
* behaves like the standard EVM user wallet case

### Delegated EOA

This is still EOA-like from Omniston’s point of view, but signing is mediated by delegation or wallet infrastructure.

Typical properties:

* still treated as an EOA-style signer for order signing
* may have product or wallet-level restrictions that differ from plain EOA behavior
* should not be assumed to support every allowance method just because it is EOA-like for signature encoding

### Contract wallet

This is a smart contract wallet.

Typical properties:

* the account is a contract, not a plain private-key account
* signature validation follows contract-wallet rules
* some allowance methods that depend on EOA-style signing are not available

## Related docs

Use [EVM Wallet kind](/developer-section/omniston/sdk/evm/evm-wallet-kind.md) to understand:

* which allowance methods are available
* how allowance-method compatibility depends on wallet kind

Use [EVM Signature](/developer-section/omniston/sdk/evm/evm-signature.md) to understand:

* how wallet kind affects permit signature handling
* how wallet kind affects final order signature encoding


---

# 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-wallet-kind.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.