Skip to main content
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

FieldTypeValue
message_typestring"quote"
quote.chain_idstringCosmos chain ID for indexer compatibility, for example "injective-888" on testnet. Never send 1439 or 1776 here.
quote.contract_addressstringRFQ contract bech32 address
quote.rfq_iduint64Request rfq_id
quote.market_idstringRequest market ID
quote.taker_directionstringRequest direction, "long" or "short"
quote.marginstringMaker margin string, same value signed as makerMargin
quote.quantitystringMaker quantity string, same value signed as makerQuantity
quote.pricestringTick-quantized price string, exactly as signed
quote.expiryuint64Unix ms expiry for live quotes
quote.makerstringMaker inj1... address
quote.maker_subaccount_nonceuint32Maker subaccount nonce, same value signed
quote.takerstringTaker inj1... address from the request
quote.signaturestring0x-prefixed 65-byte signature
quote.sign_modestringRequired. Use "v2".
quote.evm_chain_iduint64Required for v2. Same EVM chain ID used in the EIP-712 domain (1439 testnet, 1776 mainnet).
quote.min_fill_quantitystringOptional in some helper paths. If present, match the signed value. Use "0" when absent.
quote.nonceuint64Reserved 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:
EventMeaning
quote_ackIndexer accepted the quote payload
quote_updateQuote lifecycle update, when emitted
settlement_updateTaker or executor attempted settlement
Chain transaction / position stateSource 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

SymptomLikely cause
sign_mode requiredQuote omitted sign_mode: "v2"
Wrong chain in signatureEVM 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 1776EVM chain ID was passed as the Cosmos chain ID. Use injective-888 or injective-1 in chain_id.
Signature verifies locally but fails remotelyDecimal string changed between signing and sending
Quote ACK succeeds but no fill happensTaker did not accept before expiry, another quote won, or settlement skipped this quote
Settlement skips maker quoteExpired quote, mark-band rejection, worst_price failure, insufficient maker margin, or min_fill_quantity mismatch
Next: Runbook.
Last modified on May 29, 2026