BFX, you have to change something about the way swaps are taken. Since some time my "Swaps currently provided" list is cluttered up with dozens upon dozens of absolutely miniscule offers which guarranteedly nobody took out on their own but are part of some faulty matching algorithm. An offer of approx 6000 led to 3 swaps in the range of 2500, 1000, 1500 and then over thirty swaps at a dollar or even cents. The highlight is single swap undistinguishably from a single cent. Something like $0.01XXX3 Why is this happening? This is not only cluttering up the "swaps currently provided" list but also and much more importantly the "swap history" pages which get more and more inflated by the day.
Months ago, Giancarlo wrote about this when the behavior changed:
Lets assume I took five $10 swaps some time ago. You have a $100 offer up, which is the best offer, and with a better rate than my initial swaps. I close mine, and my position is refilled with $50 I borrow from you.
So far so good.
However, the engine makes me take five $10 swaps from you. Even though they are all from you, and opened at the same time.
Fast-forward a few months, where everyone has some position open, everyone has auto-lend active, and people replace old or expensive swaps with better ones: voila, the number of swaps grows infinite.
It is almost impossible to do anything against it, like "defragmenting", with the current engine behavior. Even when you wait until all your funds are returned, and then make one big offer again, people will come and take minuscule amounts because they replace minuscule amounts.
And with every "step" it all fragments more and more.
This behavior takes up a lot of my spare/bitcoin time, when I have to mark dozens, hundreds of tiny swaps to replace them. I do this for months now, and don't even want to know how many swaps I marked, replaced and fragmented since then.
And, that's why I asked for the feature of "combining swaps into one line with a +/- button" a few posts above.
Ultimately, I guess this exponential fragmentation will kill all servers where the engine works on, and maybe they change that behavior then ;-)
Ente