Skip to main content
POST
Submits wallet.create_fok_swap_trigger when this method is enabled for the selected deployment. This is a slow operational method, not the low-latency trading path. Relay validates the typed request and signature where applicable, simulates the exact call against latest, and only then queues a sponsored transaction. See Operational methods for availability, gas, and latency rules.
The example uses testnet WETH/USDC where a market is required, but all identities, nonces, timestamps, hashes, and signatures are illustrative. Read current state and build a fresh valid signature for the selected network. Omit authorization7702 and makerSlotsPrimed; complete delegation first.
string
required
New lowercase UUIDv7 for request correlation.
string
default:"wallet.create_fok_swap_trigger"
required
Must be wallet.create_fok_swap_trigger.
string
required
Trading wallet matching the bearer JWT; for AccountCore operations this is the sponsoring frontend identity, not necessarily the signed authorizer.
object
required
Method-specific payload shown below; unknown fields are rejected.
Automated triggers, including TP/SL, are not implemented as a live feature and remain work in progress. This method only stores an instruction where enabled; it does not monitor or execute a trigger.
Storage only: this does not register a condition monitor, schedule execution, or perform the FOK swap. The condition starts with a four-byte big-endian schema prefix; Relay verifies its schema and hash, then discards the bytes. Persist the exact condition bytes yourself. Replace the illustrative condition and hash with a matching pair. Creation uses the wallet’s one-shot trigger/TWAP nonce namespace, not lastSeenOrderNonce; WebSocket submissions still follow connection-level increasing nonce ordering. Sign the exact EIP-712 type below using the KuruTradingWallet version 2, with the delegated trading wallet as verifyingContract and the selected chain ID (143 mainnet; 10143 testnet):
BROADCAST means scheduling for asynchronous RPC broadcast, not provider acceptance or successful execution. Check the receipt and expected events/state. A failed estimate returns an immediate error with no transaction signed or broadcast.