EVM Wallet kind
Understand EVM wallet kinds and how they affect Omniston integrations.
Last updated
⌘Ctrlk
Understand EVM wallet kinds and how they affect Omniston integrations.
This document explains what EVM wallet kind means on EVM chains and why it matters for Omniston integrators.
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
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
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
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
Use EVM Wallet kind to understand:
which allowance methods are available
how allowance-method compatibility depends on wallet kind
Use EVM Signature to understand:
how wallet kind affects permit signature handling
how wallet kind affects final order signature encoding
Last updated