Sending quotes - TrueCurrent Docs

After signing, send the quote over MakerStream as a MakerStreamStreamingRequest with message_type = "quote". Any field covered by the EIP-712 v2 signature must match exactly, or settlement will reject the quote even if the indexer accepts the payload.

Use snake_case for MakerStream quote payload fields. Do not confuse quote.chain_id with the EIP-712 domain chainId: quote.chain_id is the Cosmos chain ID (injective-888 testnet, injective-1 mainnet), while quote.evm_chain_id and the EIP-712 domain chainId use the numeric EVM chain ID (1439 testnet, 1776 mainnet).

Quote payload

{
  "message_type": "quote",
  "quote": {
    "chain_id": "injective-888",
    "contract_address": "inj1qw7jk82hjvf79tnjykux6zacuh9gl0z0wl3ruk",
    "rfq_id": 1770848375348,
    "market_id": "0xdc70164d7120529c3cd84278c98df4151210c0447a65a2aab03459cf328de41e",
    "taker_direction": "long",
    "margin": "100",
    "quantity": "10",
    "price": "14.85",
    "expiry": 1770848395000,
    "maker": "inj1maker...",
    "maker_subaccount_nonce": 0,
    "taker": "inj1taker...",
    "signature": "0x...",
    "sign_mode": "v2",
    "evm_chain_id": 1439,
    "min_fill_quantity": "0"
  }
}

Field reference

Field	Type	Value
`message_type`	string	`"quote"`
`quote.chain_id`	string	Cosmos chain ID for indexer compatibility, for example `"injective-888"` on testnet. Never send `1439` or `1776` here.
`quote.contract_address`	string	RFQ contract bech32 address
`quote.rfq_id`	uint64	Request `rfq_id`
`quote.market_id`	string	Request market ID
`quote.taker_direction`	string	Request direction, `"long"` or `"short"`
`quote.margin`	string	Maker margin string, same value signed as `makerMargin`
`quote.quantity`	string	Maker quantity string, same value signed as `makerQuantity`
`quote.price`	string	Tick-quantized price string, exactly as signed
`quote.expiry`	uint64	Unix ms expiry for live quotes
`quote.maker`	string	Maker `inj1...` address
`quote.maker_subaccount_nonce`	uint32	Maker subaccount nonce, same value signed
`quote.taker`	string	Taker `inj1...` address from the request
`quote.signature`	string	`0x`-prefixed 65-byte signature
`quote.sign_mode`	string	Required. Use `"v2"`.
`quote.evm_chain_id`	uint64	Required for v2. Same EVM chain ID used in the EIP-712 domain (`1439` testnet, `1776` mainnet).
`quote.min_fill_quantity`	string	Optional in some helper paths. If present, match the signed value. Use `"0"` when absent.
`quote.nonce`	uint64	Reserved for non-standard quote paths. Do not send for normal MakerStream RFQs.

The v2 signature binds chain and contract through the EIP-712 domain (evm_chain_id and verifying_contract_bech32). chain_id and contract_address are still sent for indexer compatibility. Raw MakerStream JSON examples use chain_id and evm_chain_id; generated clients may expose language-specific property names, but the wire/proto field names are snake_case.

Expiry

Live quotes should be short-lived, but they must give the taker enough time to collect, select, and settle. Submit live quotes with at least 1500 ms of validity. A common live expiry is:

expiry = int(time.time() * 1000) + 2_000

The contract checks expiry at settlement block time. Taker quote collection and transaction inclusion both consume the expiry window, so do not set live expiries too tight and do not do slow work after receiving an RFQ. A longer expiry increases the chance that your quote can be matched and settled, but it also increases stale-price exposure. TP/SL-triggered requests still use the normal live RFQ quote path from the maker’s perspective.

Quote ACK

After send_quote, the indexer may return:

{
  "message_type": "quote_ack",
  "quote_ack": {
    "rfq_id": 1770848375348,
    "status": "success"
  }
}

or an error:

{
  "message_type": "error",
  "error": {
    "code": "invalid_signature",
    "message": "..."
  }
}

quote_ack.status="success" means the indexer accepted and routed the quote. It does not mean the taker accepted it and it does not mean settlement succeeded.

Fill and settlement state

Subscribe to quote and settlement updates when your client supports them. Track these separately:

Event	Meaning
`quote_ack`	Indexer accepted the quote payload
`quote_update`	Quote lifecycle update, when emitted
`settlement_update`	Taker or executor attempted settlement
Chain transaction / position state	Source of truth for actual fills

If no quote or settlement update arrives before your quote expiry, treat the quote as not accepted. After a settlement attempt, reconcile:

rfq_id
quoted price
executed quantity
executed margin
taker and maker addresses
maker subaccount nonce
transaction hash
any skipped-quote reason

Common mistakes

Symptom	Likely cause
`sign_mode required`	Quote omitted `sign_mode: "v2"`
Wrong chain in signature	EVM chain ID placed in `chain_id` instead of `evm_chain_id`, or Cosmos chain ID used in the EIP-712 domain
`quote.chain_id` is `1439` or `1776`	EVM chain ID was passed as the Cosmos chain ID. Use `injective-888` or `injective-1` in `chain_id`.
Signature verifies locally but fails remotely	Decimal string changed between signing and sending
Quote ACK succeeds but no fill happens	Taker did not accept before expiry, another quote won, or settlement skipped this quote
Settlement skips maker quote	Expired quote, mark-band rejection, `worst_price` failure, insufficient maker margin, or `min_fill_quantity` mismatch

Next: Runbook.

​Quote payload

​Field reference

​Expiry

​Quote ACK

​Fill and settlement state

​Common mistakes

Quote payload

Field reference

Expiry

Quote ACK

Fill and settlement state

Common mistakes