The crypto futures terminaltrained to be honest.
Every signal is rule-bound. Every outcome is logged. Every metric is post-fee. ByKaranteli publishes its live track record, not a backtest, not marketing copy.
Real signal results, not a backtest
Every metric below comes from signals produced live by our deterministic engine. Net of fees, slippage, and funding. Tie-break: TP and SL same candle resolves to SL.
Signal stream right now
Every closed signal across the universe in the last 24 hours, freshest first. Each row is a closed trade, with side, outcome, and net basis points. Click through for the full symbol history.
Recent Closed Signals
Where the leverage actually sits
Liquidation pressure heatmap with bias and trigger context. Public preview shows the 24-hour BTC slice. Members see all symbols and timeframes.
Built for operators who want their signals honest
Six layers, all designed around the same rule: nothing is allowed in the production pipeline that cannot be explained, reproduced, and audited later.
Deterministic engine
Same inputs always produce the same outcome. Tie-break codified, no discretion.
Net of costs
Every PnL number includes fees, slippage, and funding. No gross-only headlines.
Snapshot evaluation
Live first, evaluation snapshot-based. History is never quietly rewritten.
Auditable decision log
Every signal carries the rule, threshold, and policy hash that produced it.
Symmetric LONG and SHORT
Same scoring weights, same gates, same thresholds. Bias is measured, not designed.
Operator-first cockpit
Live signal stream, candle context, scanner, technicals, all in one workspace.
Four deterministic stages, end to end
What happens between Binance pushing a tick and you seeing a signal in the terminal.
Ingest
Binance USDT-M futures market data + indicator features streamed continuously into our worker.
Score
Deterministic engine evaluates 9 voting indicators × 3 timeframes plus an ML calibrator.
Gate
MTF alignment, quality floor, EV gate, and risk pressure each have to pass for a signal to publish.
Publish
Signal opens with entry / TP1 / SL. Live outcomes evaluated snapshot-based, recorded forever.
Six rules that make outcomes verifiable
The only way to trust a signal stream is to see the rules that produced it. These are ours, and they are enforced in code.
Incident log, in public
Outages, methodology adjustments, and recompute events that touched the public record. The full ops log lives in the admin console; this is the public window.
If you are not sure yet
Six honest answers about what this platform does, how it produces signals, and where the numbers come from.
What is ByKaranteli?
How is this different from a copy-trading bot?
What does deterministic actually mean here?
How are LONG and SHORT signals scored?
Where do the metrics on the homepage come from?
Is there a free tier?
Ready to operate?
Open the terminal workspace, watch the live signal stream, and decide for yourself. No account needed to browse public performance and signals.