출처 검증 리서치: dYdX Indexer Websocket Subaccount

Decision Matrix

Source Map

• dYdX Documentation: Indexer Client (dydx-indexer-client)
• dYdX Protocol GitHub: v4-chain Indexer README (dydx-v4-indexer-readme)
• dYdX Indexer: Indexer API OpenAPI documentation (dydx-indexer-api)

Control Notes

1. Endpoint selection

Endpoint selection is the decision point where public documentation must become an operating rule. In this package, it means client code must use the intended network endpoint rather than a stale testnet or staging URL. The practical action is to record HTTP and WebSocket base URLs before integration. The unresolved edge is future endpoint migration outside the local config, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

2. Subaccount identity

Subaccount identity is the decision point where public documentation must become an operating rule. In this package, it means subaccount data depends on address and subaccount number mapping. The practical action is to verify address, subaccountNumber and parentSubaccountNumber before display. The unresolved edge is wallets linked through a route not represented in the local model, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

3. WebSocket channels

WebSocket channels is the decision point where public documentation must become an operating rule. In this package, it means different channels answer market, orderbook and account questions. The practical action is to subscribe only to the channel needed for the decision. The unresolved edge is message gaps during reconnect, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

4. REST backfill

REST backfill is the decision point where public documentation must become an operating rule. In this package, it means REST routes can be used to check state after stream loss. The practical action is to backfill fills, positions and orderbook state after reconnect. The unresolved edge is whether historical windows cover the entire outage, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

5. Compliance screen

Compliance screen is the decision point where public documentation must become an operating rule. In this package, it means screening endpoints are decision inputs, not guarantees of permission. The practical action is to treat screen results as a stop/go evidence item. The unresolved edge is jurisdiction-specific account treatment, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

6. Evidence hygiene

Evidence hygiene is the decision point where public documentation must become an operating rule. In this package, it means public endpoint tests should not expose wallet private data. The practical action is to store route, network, channel and non-secret status labels. The unresolved edge is retention rules for account-level logs, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

Known Unknowns

• future endpoint migration outside the local config
• wallets linked through a route not represented in the local model
• message gaps during reconnect
• whether historical windows cover the entire outage
• jurisdiction-specific account treatment
• retention rules for account-level logs

Practical Takeaway

dYdX v4 indexer evidence should be treated as an application data-readiness question, not as proof that a wallet is approved or a trade is safe. Official dYdX client documentation shows how the IndexerClient is initialized against indexer HTTP and WebSocket endpoints, the v4-chain indexer README documents websocket channel examples such as v4_markets, v4_orderbook and v4_subaccounts, and the public Indexer API exposes account, market, fill and compliance-screen routes. The decision outcome is to test endpoint selection, subaccount identity, websocket subscription, REST backfill and compliance-screen handling before relying on indexer data in a trading workflow. The article stops at the evidence boundary. It helps the reader decide what to inspect next without converting public documentation into a promise that a private account, wallet, callback, policy framework, settlement route or liquidity position will work under every future condition.