Closed livinginformation closed 6 years ago
GUI needs this sooner rather than later so I can test how the data is ingested by the graph. This will also force us to "normalize" the formats/data-stuctures returned between exchanges so the GUI can expect the same data structure every time.
In fact, i think GUI is dependent on this. I can't reasonable test the interface with live money.
Ah, of course. Okay, we'll make this a requirement for beta then.
Alright, I'm going to settle into working on this for a couple hours. Need to nail down a sane structure. If anyone is around to talk high-level stuff, I'll be on Discord.
https://docs.google.com/document/d/1X0yDzu2xl3lEZh1SOIQSs7ey9NRHh5s5ZdRMjZvsBLY/edit?usp=sharing will contain a live view into the working specification, going to put anything that comes to mind there.
I had started an attempt a few weeks ago. Basically a copy paste of a tux exchange object with added machinery for generating new price, checking that against self order book. You'd just need to replace _buy _sell and generate some of the data asked for in some of the other methods. Also see Graph.fake_data() in simple app for a very dumb version. That is at the merkato level though, so too abstract
Nothing external calls signed request, I don't think we're simulating failed API calls, unless you wanna go full real life sim
[Project scope intensifies]
Yeah, lets keep it as lightweight as possible, we can nuke signed requests and stuff.
I'll eventually bolt on a price determination override to be able to back test bots of different parameters against same price action. Like a list of price/time tuples arg
Ive been thinking the same thing (passing in time-series data of price over a span, and calculating the expected profit).
Ill add it as its own issue.
is this complete @livinginformation @nasaWelder
Looks like it
For testing purposes, we'll want a mock exchange that can build an orderbook and execute orders.
Don't prioritize until after beta.