Will dxFeed depth be added later?

The 0.46.0 code deliberately requests no depth on this rail. Anything beyond that is not in the current version.

Which credentials does the dxFeed form ask for?

The dxLink address issued by your firm, an optional login, and the password or token. The login is optional because a direct dxFeed access may only have a token.

dxFeed source in Senzoukria: DOM and heatmap stay empty, demo feed 15 minutes behind

On the dxFeed source, Senzoukria receives trades only: no order book is requested, so the DOM and the heatmap stay empty by design. The dxFeed demo endpoint runs about 15 minutes behind the market, and the connection form says so.

Senzoukria · Troubleshooting · Updated September 2026

At a glance

Source hint: “Trades only: no order book, so DOM and heatmap stay empty.”
Demo warning: “Demo endpoint: this feed runs 15 minutes behind the market”
Credentials: dxLink address issued by your firm, login (optional) and password or token
Applies to: Senzoukria desktop 0.46.0

What you see

The dxFeed entry of the Chart data source selector reads “dxFeed — futures on the dxLink address and token your firm issued. Data goes straight from dxFeed to your machine. Trades only: no order book, so DOM and heatmap stay empty.” The footprint fills with trades while the DOM and the heatmap show nothing.

When the dxLink address is the dxFeed demo server, the form warns that this feed runs 15 minutes behind the market.

Why it happens

The dxFeed rail subscribes to trades without depth on purpose. The code records a measurement from 22 September 2026: dxLink’s DOM service answers and returns its configuration, but serves zero orders when the token does not carry the entitlement, without any error. Requesting depth would paint an empty DOM that looks like a software fault, so the app does not request it.

The demo endpoint is offered so the rail can be tried without an account. Measured delays between trade time and reception were regular at about 900 seconds, which is a deliberate delay, not network latency.

How to fix it

For depth, the DOM and the heatmap, use a source that carries an order book: a Rithmic connection, a NinjaTrader or Quantower bridge, Databento CME live with the proper licence, or the crypto feeds.
For live data on dxFeed, enter the dxLink address your firm issued. There is no universal address, which is why the app cannot fill it for you.
Keep the demo address for trying the rail only, and never read its prices as the current market.

What it is not

Not a broken heatmap: no depth is requested on this rail.
Not latency on your connection when the demo address is used: the demo feed is delayed by design.

When to contact support

If the steps above do not change anything, send the case from Menu → Report a problem, or ask on the Senzoukria Discord. The code notes that the dxFeed authentication path has not yet been checked against a real prop-firm account; if your firm’s login is refused, the exact message is valuable.

In the same section

This page in other languages

Frequently asked questions

Will dxFeed depth be added later?: The 0.46.0 code deliberately requests no depth on this rail. Anything beyond that is not in the current version.
Which credentials does the dxFeed form ask for?: The dxLink address issued by your firm, an optional login, and the password or token. The login is optional because a direct dxFeed access may only have a token.

Keep reading

Strategy researchTest a trading strategy, from observation to challenge rulesDefine an observation, question it with the copilot, write a rule and explore costs, drawdown and fictional challenge limits in an interactive example.Quant · Start hereQuant trading for beginners: from idea to backtestDefine a testable rule, choose suitable data and evaluate later periods after costs.Order flow · HubOrder flow trading: the complete guideThe hub. What order flow is, what it shows — aggression, delta, imbalance, absorption, liquidity — and the tools that read it, each linked to a full guide.