Geen omschrijving

Berke 11fe61600b chore: move some layout configs to the main state, `State` 10 maanden geleden
.cargo 5aa31fbefe simpler websocket & parser implementation (#9) 1 jaar geleden
src 11fe61600b chore: move some layout configs to the main state, `State` 10 maanden geleden
.gitignore 375e497aa3 Visible range trades fetch(Binance) (#20) 10 maanden geleden
Cargo.lock 9db4fed853 Improved chart panels (#24) 10 maanden geleden
Cargo.toml 9db4fed853 Improved chart panels (#24) 10 maanden geleden
LICENSE c378397c75 initial commit 1 jaar geleden
README.md 375e497aa3 Visible range trades fetch(Binance) (#20) 10 maanden geleden

README.md

iced-trade iced-trade

Some of the features:

  • Customizable and savable grid layouts, selectable themes
  • Supports most of spot(USDT) & linear perp pairs from Binance & Bybit
  • Orderbook total bid/ask levels: 1000 for Binance Perp/Spot; 500 for Bybit Perps, 200 for Bybit Spot
  • Binance perp/spot & Bybit perp streams @100ms; Bybit spot pairs streams @200ms
  • Tick size multipliers for price grouping on footprint and heatmap charts
iced-trade iced-trade
User receives market data directly from exchange APIs.
  • As historical data, it can fetch OHLCV, open interest and partially, trades:

Historical trades on footprint chart:

Optionally, you can enable trade fetching from settings menu, experimental because of unreliability:

  • Binance connector supports downloading historical trades from data.binance.vision, fast and easy way to get trades, but they dont support intraday data. Intraday trades fetched by pagination using Binance's public REST APIs: /fapi/v1/aggTrades & api/v3/aggTrades, it might be slow because of rate-limits

  • Bybit itself doesnt have a similar purpose public API

Flowsurface tries to leverage this via Binance tickers, to visualize historical public trades while being independent of a 'middleman' database between exchange and the user. So, when a chart instance signal the exchange connector after a data integrity check, about missing trades in the visible range; it tries via fetching, downloading and/or loading from cache, whichever suitable, to ensure this integrity

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: