EIP-712 Signing

Senticore uses wallet signatures to authorize trading actions.

Signing model

User actions follow a deterministic signing path:

1. The client constructs the canonical action payload.
2. The action is hashed through the canonical EIP-712 typed-data encoding.
3. The user's wallet or delegated trading credential signs the hash.
4. The signed action is submitted through the integration API.

Why typed data

EIP-712 typed-data signing produces readable wallet prompts. The user sees the actual action they are authorizing, such as market, side, price, quantity, and expiry, rather than an opaque hash.

Required client handling

Production-grade signing flows handle:

• wallet not connected,
• wrong chain,
• user signature rejection,
• stale or replayed nonce,
• expired delegated session,
• validation rejection,
• network retry uncertainty.

The SDK provides helpers for these cases.