Нет описания

Berke 0ce407333a Revert "fix platform specific window configs `settings()` " 10 месяцев назад
.cargo 5aa31fbefe simpler websocket & parser implementation (#9) 1 год назад
src 0ce407333a Revert "fix platform specific window configs `settings()` " 10 месяцев назад
.gitignore 58eb2dd111 logger setup 1 год назад
Cargo.lock e1a73e2f8a v0.5 10 месяцев назад
Cargo.toml e1a73e2f8a v0.5 10 месяцев назад
LICENSE c378397c75 initial commit 1 год назад
README.md 40e562ef47 Update README.md 1 год назад

README.md

iced-trade iced-trade

Currently features:

  • Customizable and savable grid layouts
  • 4 crypto tickers, from Binance and Bybit; BTCUSDT, ETHUSDT, SOLUSDT, LTCUSDT (perpetual swaps)
  • 1m, 3m, 5m, 15m and 30m timeframe selections for candlestick and footprint charts. Tick based "timeframe" selections is planned
  • Tick size multipliers for price grouping on footprint and heatmap charts
  • Size filtering for trades showing up in time&sales tables and heatmap charts
  • Each grid (pane) can have its own ticker/exchange pair of streams. You can open up however many panes you want. Though, if for example the layout is filled with more than a reasonable amount of heatmap charts, via the most cpu time demanding chart instance between renders, then performance/resource usage might become a slight concern. But there is no limit to it yet to test out the boundries
iced-trade iced-trade
There is no server-side yet. User receives market data directly from exchange APIs
  • As historical data, currently it can only fetch OHLCV. So, the footprint chart gets populated via candlesticks but not historical trades. Trades gets inserted to the latest candlestick as we receive them from related websocket stream in real-time

Build from source

The releases might not be up-to-date with newest features.or bugs :)

  • For that, you could clone the repository into a directory of your choice and build with cargo.

Requirements: