There is something weird when I start a grid and set buy price (of base) at the range high price.
I do that coz base was existing and re used, counting gain of first sells by using bought price is incorrect in this case, and to avoid counting ‘fake gains’, I started setting the buy price with price of the top of the grid.
With this, first sells count for 0 gains which is fine to me.
Then I can’t understand the transaction list, it’s incorrect where completed list is OK.
To easy spot, look at those 3 sell at 11.77 : that’s incorrect. And so there is a matching buy / sell that is weird.
So because you have set top and initial price to 12.53 and the current price was 11.7730 you would have expected the grid to start with buy orders on the way down and sell orders on the way up?
I mean it is showing sell not at correct price in transactions.
Of course, first order was a sell of existing base (coz going up).
I found that as a workaround, coz else, first buy could be considered very low (Entry price) where it’s not true as already bought the base before start of the bot.
With tests and by looking at gain count, setting high entry price is making original buy inexistant. It means that first sell of any of the initial sell order at startup would be 0 gain (I was expecting to have a negative gain but instead, it’s ignored and gain go to 0 and the transaction contains no buy but a sell with 0 gain (there is gain but not counted…).
This is fine for me but when you look at pictures, you can see than it sold 3 times at 11.77 where it was 2 at that price. It recorded 4 sells where only 3. It’s no more clear as if Entry price stay set as default. It’s not matching what you really see (I mean, the transactions list looks weird).
It sell as expected (no buy as skipped as price higher and negative gains), then second is a buy turn a sell at same price as just before. It should be a second buy.
Well, I can’t explain. It’s like when setting that price higher, there is a fallback that prevent something but without fully implementing a correct solution.
The main point is that I can read the chart and completed list, but the transaction list looks corrupted.
Edit : the last line in last Pic, it should had been a sell coupled with a real buy (coz buy had to buy again after selling before). But it’s not : it’s just a sell without gain and without buy. It’s weird, something has moved somewhere…
Lowest is first sell order. Before that order there was no buy match, so its empty
Second is the buy at 6551. For that buy we have found corresponding sell at 7762, so profit calculates between them
Next buy at 5352, there was no sell match, sell column is empty
Next sell at 6552, we have found a amtch form previous filled orders at 6551
And so on. Order could appear in transactions list multiple time. First when no match, second time if the order if the match of corresponding filled.
If its the only problem, so its not a bug. This transactions logic was almost from the beginning
Transaction order : last on top.
Two sell without buy price : OK
Then come the buy, and it associates it with the previous sell to make first gain.
In my opinion, this is incorrect, irrealistic and impossible.
You can’t do this association coz you have to buy first then sell, not the opposite.
I would not expect gain yet, only if the next order is a sell at the same level as the second transaction (for example).
This is what I called weird I guess.
Shouldn’t that receive a fix?
This is a long bot, there are no sells without a previous buy. Because when you start the bot you make a purchase. All the sell orders that have no buy are matched to the initial purchase. It’s working as it should.
OK so this is my last try, no worries.
Coz this continue to be a problem for me.
I’ve tried to use a weird workaround but, it’s putting things on an even weirder path.
Thus I just thought I need to get one step back and retry an explanation about the real problem I have.
Let’s split that in two main cases.
First case : this is the first time you start a bot. Gainium will buy the base (all at about a same price) and set the bought price. This is absolutely correct, but need to understand this : first sell (of the bought base, so at higher price than opening) of position of all levels will be collecting more and more gain. Coz it’s an amount bought at fixed same price but sold on a price higher and higher (the highest sold price, at top of the grid, will have the first biggest gain). At second sell of those level (after buy back), no more high gain (this is normal). You then continue with that same gain behavior : some percent (depending of your grid spacing) and a few amount (total divided by number of levels). Easy to understand, correct behavior with some magic at first sell.
Second case : you start a bot but you already have the base (that could come from anywhere, imagine you just transfered it and no idea of the buy price : don’t care, you just already have it). This is where the bought price is a real problem for me. Without manually setting bought price, Gainium will use start price, even if not buying anything. This made gains calculation wrong as on the first sell, it will calculate gains from start price (and says that you got plenty gains while reaching the top of the grid). This is my problem : how to avoid that? The above workaround is not a real solution (and causing trouble in reading transactions, coz binding orders together where it should not in my opinion). I need to tell Gainium to not count first gains (from base used at startup) like it usually does.
That’s where is heading this last try : I think Gainium needs a checkbox, just near this buy price box, that will tell Gainium that no : that base for the bot doesn’t have any buy price : just skip it, avoid counting first gains of base (where sell positions have been placed at startup). This way, no more fake gain count, just skip gains on first time sell of those levels (at higher price than startup) OR just count expected gain like for second and all next gains for those positions / levels. This would definitely be a fix for my problem. You can’t always ask user for a buy price, sometimes it’s just not possible, Gainium need to also be OK with that scenario.
Hope it was understandable, let me know what you think about that. The checkbox would gray the buy price coz useless.
After you start the bot, I believe you can modify the buy price by editing the bot.
I understand what you are trying to say, but I don’t see the utility. Even if you bought that base at another price, you need a reference price to properly calculate your profit. Ignoring the first base sells and calculating profit only on the matching pairs is just as inaccurate profit reporting as using a wrong initial buy price.
I see that feature as a more clean way than setting an arbitrary price. I guess it all depends on how you manage the whole things. On my side, I don’t have an unique grid on one market but several, stacked on top of each other. In fact, see it as two stacks of Grids, where the the second stack’s Grids got their bottom / top price in the middle of the first stack’s grid. Easily said, it’s like two stacks of boxes (box of same size for the sake of the explanation) where the second stack start at the middle of the first box high of first stack.
It’s not easy but allows me to prepare plenty grids to be used later (and more…). Meaning that once you go down in price, I need to lock the base amount stuck in an above grid (else, you sell your base at lower price and kill your previous profits, which is dumb). And so, because of my way to manage things, this makes that scenario existing and requiring something to better correctly track my own gains over time (speaking about just grid profits overall coz some other profits can be done aside that, due to my management way, and that can’t be counted in Gainium gains coz can’t be aware). When reusing those locked base, it’s a problem.
That’ are my final words on the why it would be interesting to me that Gainium could provide that option . At the end, up to you .
I started it and forgot to set buy price at top grid price before startup. So I did edit the bot to fix, but despite that, there were 2 sell orders after the update (not yet any order when I updated) and it says buy price around 12 where my update set it at 15. It just skipped my update.
Whenever you start deals with existing currencies that aren’t any stable coins and if you also don’t exactly know the average price of the existing currencies all calculations based on that will always be inaccurate.
,
.
