You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the HF has a plugin system in the form of bfx-hf-models adapters, which abstract Trade and Candle sync logic. There is however a secondary system used within bfx-hf-server which cannot be easily removed (individual exchange connection classes).
As a note, bfx-hf-server relies on the bfx-hf-models adapters for all algo order execution and trade/candle syncing, not the internal exchange connection classes.
TODO
decide on plugin architecture
technically half of a plugin is in bfx-hf-server and half in bfx-hf-ext-plugin-EXCHANGE
refactor existing plugins if needed
design plugin UI
implement plugin system
The text was updated successfully, but these errors were encountered:
Currently the HF has a plugin system in the form of
bfx-hf-models
adapters, which abstract Trade and Candle sync logic. There is however a secondary system used withinbfx-hf-server
which cannot be easily removed (individual exchange connection classes).As a note,
bfx-hf-server
relies on thebfx-hf-models
adapters for all algo order execution and trade/candle syncing, not the internal exchange connection classes.TODO
bfx-hf-server
and half inbfx-hf-ext-plugin-EXCHANGE
The text was updated successfully, but these errors were encountered: