Sometime ago I read a post where a user of OpenLedger complained about the trade engine not matching the trades properly. In specific, higher "Ask" trades were executed before his lower ones, if I remember well. I did check out his claims and they are true. Though, I would like to point out that it might be a bug, or that someone is trying to inflate the price of an asset by selectively trading between or among different accounts.
author | skriptroid |
---|---|
permlink | openledger-trade-engine-bug-or |
category | bitshares |
json_metadata | {"tags":["bitshares"]} |
created | 2016-07-28 08:15:54 |
last_update | 2016-07-28 08:15:54 |
depth | 0 |
children | 9 |
last_payout | 2016-08-27 23:34:09 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 434 |
author_reputation | 563,630,330,217 |
root_title | "OpenLedger trade engine bug or ..?" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 429,228 |
net_rshares | 1,197,771,366 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
skriptroid | 0 | 1,192,751,666 | 100% | ||
cire81 | 0 | 5,019,700 | 100% |
See https://bitsharestalk.org/index.php/topic,22851.msg296530.html#msg296530 for an explanation. Basically, the skewed prices result from rounding errors on orders with very low volume. This is to be expected and not a bug. The resulting trade price is "opticallly" skewed in the sense that the price of a specific trade is off by a large factor. However, price comparisons should always be done on volume-weighted numbers, in which case these rounding errors will disappear.
author | cyrano.witness |
---|---|
permlink | re-skriptroid-openledger-trade-engine-bug-or-20160729t095720645z |
category | bitshares |
json_metadata | {"tags":["bitshares"],"links":["https://bitsharestalk.org/index.php/topic,22851.msg296530.html#msg296530"]} |
created | 2016-07-29 09:57:21 |
last_update | 2016-07-29 09:57:21 |
depth | 1 |
children | 4 |
last_payout | 2016-08-27 23:34:09 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 477 |
author_reputation | 4,484,166,969,124 |
root_title | "OpenLedger trade engine bug or ..?" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 459,623 |
net_rshares | 3,813,400,371 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
ppitonak | 0 | 3,813,400,371 | 100% |
I checked the link. The case I refer has nothing to do with this. I mentioned that I had the Lowest Ask trade set and instead the higher one was executed. I distinguished a couple events that reason with the facts. If you still insist that has something to do with rounding, then you should take rounding off the equation or find a way to execute trades properly if you decide to keep it. Do not expect widespread adoption if such behavior is continued, explained, expected or not.
author | skriptroid |
---|---|
permlink | re-cyranowitness-re-skriptroid-openledger-trade-engine-bug-or-20160729t190008178z |
category | bitshares |
json_metadata | {"tags":["bitshares"]} |
created | 2016-07-29 19:00:15 |
last_update | 2016-07-29 19:00:15 |
depth | 2 |
children | 3 |
last_payout | 2016-08-27 23:34:09 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 481 |
author_reputation | 563,630,330,217 |
root_title | "OpenLedger trade engine bug or ..?" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 471,852 |
net_rshares | 0 |
It would be helpful if you were more specific about your experiment. Any attempt to answer an unspecific question is only a shot in the dark. In the example I cited, the actual trade price as calculated from paid/received amounts was off from the price of the offers on the market. The point here is that the paid/received amounts are calculated by applying the price of the market offer to the amount available for paying, and rounding the result. The rounding is necessary due to lack of precision in the target asset. If that is not the problem that you verified in your experiment, again, please be more specific about what you perceive as the problem.
author | cyrano.witness |
---|---|
permlink | re-skriptroid-re-cyranowitness-re-skriptroid-openledger-trade-engine-bug-or-20160729t201138108z |
category | bitshares |
json_metadata | {"tags":["bitshares"]} |
created | 2016-07-29 20:11:36 |
last_update | 2016-07-29 20:11:36 |
depth | 3 |
children | 2 |
last_payout | 2016-08-27 23:34:09 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 658 |
author_reputation | 4,484,166,969,124 |
root_title | "OpenLedger trade engine bug or ..?" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 473,382 |
net_rshares | 0 |
That is a known issue that doesn't matter to 99.999% of the trades only affects so called "dust trades" .. so those are low volume anyways ... https://github.com/cryptonomex/graphene/issues/460
author | xeroc |
---|---|
permlink | re-skriptroid-openledger-trade-engine-bug-or-20160728t083254400z |
category | bitshares |
json_metadata | {"tags":["bitshares"],"links":["https://github.com/cryptonomex/graphene/issues/460"]} |
created | 2016-07-28 08:32:54 |
last_update | 2016-07-28 08:32:54 |
depth | 1 |
children | 3 |
last_payout | 2016-08-27 23:34:09 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 193 |
author_reputation | 118,819,064,085,695 |
root_title | "OpenLedger trade engine bug or ..?" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 429,540 |
net_rshares | 4,552,114,450 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
fractalnode | 0 | 659,268,238 | 100% | ||
ppitonak | 0 | 3,892,846,212 | 100% |
Excuse me. If you want to be taken seriously, as you intend to and advertise, you know that the above answer is not professional at all. Don't expect OpenLedger to gain support before you fix this bug, plus some others that you most probably have spotted already.
author | skriptroid |
---|---|
permlink | re-xeroc-re-skriptroid-openledger-trade-engine-bug-or-20160728t180149219z |
category | bitshares |
json_metadata | {"tags":["bitshares"]} |
created | 2016-07-28 18:01:54 |
last_update | 2016-07-28 18:01:54 |
depth | 2 |
children | 2 |
last_payout | 2016-08-27 23:34:09 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 264 |
author_reputation | 563,630,330,217 |
root_title | "OpenLedger trade engine bug or ..?" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 441,876 |
net_rshares | 0 |
I am not affiliated with Openledger and and as such don't intend anything, nor do I advertise anything but merely point you to the facts.
author | xeroc |
---|---|
permlink | re-skriptroid-re-xeroc-re-skriptroid-openledger-trade-engine-bug-or-20160728t182904996z |
category | bitshares |
json_metadata | {"tags":["bitshares"]} |
created | 2016-07-28 18:29:03 |
last_update | 2016-07-28 18:29:03 |
depth | 3 |
children | 1 |
last_payout | 2016-08-27 23:34:09 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 137 |
author_reputation | 118,819,064,085,695 |
root_title | "OpenLedger trade engine bug or ..?" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 442,545 |
net_rshares | 0 |