Skip to content
This repository has been archived by the owner on Feb 15, 2022. It is now read-only.

Thoughts on backfills based on trade history #2746

Open
jorisw opened this issue Aug 15, 2021 · 0 comments
Open

Thoughts on backfills based on trade history #2746

jorisw opened this issue Aug 15, 2021 · 0 comments

Comments

@jorisw
Copy link
Contributor

jorisw commented Aug 15, 2021

System information

  • Have I written custom code (as opposed to using zenbot vanilla): Yes, lots
  • OS Platform and Distribution (e.g., Linux Ubuntu 16.04): macOS 11.5 + Ubuntu 20
  • Zenbot branch: Forked long ago from unstable
  • NodeJS version: 14

Describe the problem

Zenbot heavily relies on backfills, based on retrieving trade history from exchanges. Zenbot also heavily relies on ccxt, the library that unifies various crypto exchanges into a single unified API.

The manual of ccxt stresses that in general you should not rely on exchanges being able or willing to supply trade history far into the past. Exchanges that don't offer this, generally do offer long candlestick histories, that basically aggregate the same data into 1m to 1M periods.

Long story short, the reliance of Zenbot on trades, rather than candles for historical data, is probably a critical design flaw.

I'm curious to know if current maintainers (if any) of Zenbot concur.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants