I haven't the need, so didn't bother. What types of things would you want to do? So I know what facts to extract for reasoning and what actions to support.
You are viewing a single comment's thread from:
I haven't the need, so didn't bother. What types of things would you want to do? So I know what facts to extract for reasoning and what actions to support.
The basic ones are:
Most if not all will be in
contracts/marketpools.js
Quite more advanced (this will go in the direction of "trading" automation most likely, so not sure if that's your idea):
You are already doing something within the lines with the Oracles feature... =)
I would be a frequent tester with this one for sure. Pools are quite "better" positioned against the markets in many cases. Meaning that most of the time you get better prices via pools.
Thanks. I'll add all that to my list. I was trying to avoid making a trading bot. I'll see what info I can pull from the pools then, most of what you want can be done with a few pool / liquidity "facts" and some commands to handle liquidity. Might take me awhile though.
Yeah, I figured. No rush on this... I think providing the basic functions (swap, add, remove liquidity) is probably already a huge help for many.
Until we are on the other side of the HF26 without any sorts of things to sort out, any new stuff is just secondary for me. First stability and HA, etc..
Right now I am busy with the HE stuff and Hive, but later would like to see your code better. I feel from the diagonal read that I have something to learn about on those facts collections. Looks nice... Also feels this is going on somewhere nice as a tool. =)