> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tc.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# MakerStream

> How makers connect to TrueCurrent's MakerStream WebSocket, answer the EIP-712 auth challenge, receive RFQ requests, and send quotes.

MakerStream is the bidirectional stream used by whitelisted makers. You receive RFQ requests and send signed quotes on the same connection.

The connection is gRPC-web over WebSocket with protobuf payloads. Most integrations should use `MakerStreamClient` from `injective-rfq-toolkit` rather than hand-rolling framing.

***

## Endpoint

| Environment | MakerStream URL                                                                        |
| ----------- | -------------------------------------------------------------------------------------- |
| Testnet     | `wss://testnet.rfq.ws.injective.network/injective_rfq_rpc.InjectiveRfqRPC/MakerStream` |
| Mainnet     | Contact TrueCurrent for the current production endpoint                                |

Connection details:

| Property              | Value                                                 |
| --------------------- | ----------------------------------------------------- |
| Protocol              | gRPC-web over WebSocket                               |
| WebSocket subprotocol | `grpc-ws`                                             |
| Serialization         | Protobuf                                              |
| Framing               | `[1 byte flags][4 bytes length BE][protobuf payload]` |
| Keep-alive            | Send ping roughly every second                        |
| Service               | `injective_rfq_rpc.InjectiveRfqRPC`                   |
| Method                | `MakerStream`                                         |

<Info>
  The indexer's internal proto may use different package or method names. Public traffic uses the `injective_rfq_rpc.InjectiveRfqRPC/MakerStream` alias. Use the public alias shown above.
</Info>

***

## Connection sequence

```mermaid theme={null}
sequenceDiagram
    participant MM as Maker
    participant IDX as RFQ Indexer

    MM->>IDX: WebSocket connect with maker_address metadata
    IDX-->>MM: MakerChallenge
    MM->>MM: Sign StreamAuthChallenge (EIP-712 v2)
    MM->>IDX: MakerAuth{evm_chain_id, signature}
    loop every ~1s
        MM->>IDX: ping
        IDX-->>MM: pong
    end
    IDX-->>MM: request events
    MM->>IDX: signed quote events
    IDX-->>MM: quote_ack / quote_update / settlement_update
```

Until the auth challenge is answered successfully, the stream may remain open but no `request` events arrive.

***

## Message types

MakerStream responses are tagged by `message_type`.

| `message_type`      | Direction        | Meaning                                                                  |
| ------------------- | ---------------- | ------------------------------------------------------------------------ |
| `challenge`         | Indexer -> maker | One-shot `MakerChallenge`; must be answered before requests are streamed |
| `pong`              | Indexer -> maker | Response to maker ping                                                   |
| `request`           | Indexer -> maker | RFQ request broadcast                                                    |
| `quote_ack`         | Indexer -> maker | Indexer accepted or rejected the submitted quote payload                 |
| `quote_update`      | Indexer -> maker | Quote lifecycle update, when available                                   |
| `settlement_update` | Indexer -> maker | Settlement attempt or fill update, when available                        |
| `error`             | Indexer -> maker | Stream or payload error                                                  |

MakerStream requests you send are also tagged:

| `message_type` | Payload                               |
| -------------- | ------------------------------------- |
| `ping`         | Heartbeat                             |
| `auth`         | `MakerAuth` response to the challenge |
| `quote`        | Signed RFQ quote                      |

***

## Auth handshake

The indexer challenges the maker address announced in connection metadata. Sign the challenge with the same EIP-712 domain family used for quotes:

| Domain field        | Value                                             |
| ------------------- | ------------------------------------------------- |
| `name`              | `"RFQ"`                                           |
| `version`           | `"1"`                                             |
| `chainId`           | EVM chain ID (`1439` testnet, `1776` mainnet)     |
| `verifyingContract` | RFQ contract converted from bech32 to EVM address |

### `MakerChallenge`

| Field          | Type   | Meaning                                                                             |
| -------------- | ------ | ----------------------------------------------------------------------------------- |
| `nonce`        | string | Hex-encoded 32 bytes. Decode to raw bytes for signing; do not hash the nonce first. |
| `evm_chain_id` | uint64 | Chain ID for the EIP-712 domain.                                                    |
| `expires_at`   | sint64 | Unix milliseconds. Sign and reply before it expires.                                |

### `StreamAuthChallenge`

Type string:

```text theme={null}
StreamAuthChallenge(uint64 evmChainId,address maker,bytes32 nonce,uint64 expiresAt)
```

| Field        | Encoding                                         |
| ------------ | ------------------------------------------------ |
| `evmChainId` | Big-endian integer word                          |
| `maker`      | 20-byte EVM address derived from maker `inj1...` |
| `nonce`      | Raw 32 bytes from `MakerChallenge.nonce`         |
| `expiresAt`  | Big-endian integer word                          |

### `MakerAuth`

Send the response as:

| Field          | Meaning                                        |   |   |   |                       |
| -------------- | ---------------------------------------------- | - | - | - | --------------------- |
| `evm_chain_id` | Same value from the challenge                  |   |   |   |                       |
| `signature`    | `0x`-prefixed 65-byte secp256k1 signature (\`r |   | s |   | v`, compact `v=0/1\`) |

***

## Recommended client

`injective-rfq-toolkit` handles framing, pings, and MakerChallenge auth when configured with auth fields.

```python theme={null}
from rfq_test.clients.websocket import MakerStreamClient

mm_ws = MakerStreamClient(
    endpoint=env.indexer.ws_endpoint,
    maker_address=mm_wallet.inj_address,
    subscribe_to_quotes_updates=True,
    subscribe_to_settlement_updates=True,
    auth_private_key=MM_PRIVATE_KEY,
    auth_evm_chain_id=1439,
    auth_contract_address=env.contract.address,
    timeout=15.0,
)

await mm_ws.connect()
```

If the stream connects and pongs return, but no `request` events arrive, debug the auth challenge first: wrong `evm_chain_id`, wrong contract domain, stale challenge, or a signature over hashed nonce bytes instead of raw nonce bytes are common causes.

***

## Implementation checklist

* Use the `grpc-ws` WebSocket subprotocol.
* Send `maker_address` metadata on connect.
* Answer `MakerChallenge` before expecting requests.
* Start pinging immediately and continue roughly every second.
* Treat `rfq_id` from each request as the correlation key.
* Log every `quote_ack`, `quote_update`, `settlement_update`, and `error`.
* Reconnect with backoff and re-authenticate after reconnecting.

***

## ADL and position monitoring

MakerStream carries RFQ coordination events only. It does not replay every onchain position change.

Auto-deleveraging (ADL) is handled by Injective's exchange module through a position-offsetting mechanism. If one of your existing positions is offset by ADL, you will not receive an RFQ request or submit a quote for that close. Subscribe to the normal Injective derivative trade or position stream for your maker subaccounts and treat `execution_type = OffsettingPosition` as a real close event.

ADL selection happens outside MakerStream. After an ADL close lands, update your inventory and close or resize the external hedge according to your risk policy. See [Auto-deleveraging (ADL)](/trading/adl).

Next: [RFQ requests](/sdk-trading/rfq-requests) and [Sending quotes](/sdk-trading/sending-quotes).