SoSoFlows.envelope

EIP-712 envelope preview

The SoDEX REST v1 spec signs orders as EIP-712 typed-data. This page shows the exact payload, canonical serialization, payloadHash, and typed-data structure that would be signed for any intent the agent layer produces. No wallet needed to inspect.

loading ValueChain testnet chainId 138565 SoDEX gateway unavailable, envelope is still cryptographically valid
loading envelope...

How the envelope reaches SoDEX

  1. Agents produce an intent: {ticker, verdict, score, rationale}
  2. ExecutionAgent maps it to a SoDEX payload: {action, symbol, side, type, qty, price, reduceOnly, nonce}
  3. Payload is canonicalized (alpha-sorted JSON, no whitespace) for determinism
  4. Canonical bytes are keccak256-hashed → payloadHash
  5. Wallet signs the EIP-712 typed-data {payloadHash, nonce} with the SoDEX domain
  6. Resulting signature is 0x01-prefixed (SoDEX wraps EIP-712 with a version byte)
  7. POST to testnet-api.sodex.com/v1/order/new with headers X-API-Key: <signer addr>, X-Sign: <0x01-prefixed sig>, X-Nonce: <ms nonce>, body is the original payload