create account

OpenLedger trade engine bug or ..? by skriptroid

View this thread on: hive.blogpeakd.comecency.com
· @skriptroid ·
OpenLedger trade engine bug or ..?
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.
👍  ,
properties (23)
authorskriptroid
permlinkopenledger-trade-engine-bug-or
categorybitshares
json_metadata{"tags":["bitshares"]}
created2016-07-28 08:15:54
last_update2016-07-28 08:15:54
depth0
children9
last_payout2016-08-27 23:34:09
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length434
author_reputation563,630,330,217
root_title"OpenLedger trade engine bug or ..?"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id429,228
net_rshares1,197,771,366
author_curate_reward""
vote details (2)
@cyrano.witness ·
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.
👍  
properties (23)
authorcyrano.witness
permlinkre-skriptroid-openledger-trade-engine-bug-or-20160729t095720645z
categorybitshares
json_metadata{"tags":["bitshares"],"links":["https://bitsharestalk.org/index.php/topic,22851.msg296530.html#msg296530"]}
created2016-07-29 09:57:21
last_update2016-07-29 09:57:21
depth1
children4
last_payout2016-08-27 23:34:09
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length477
author_reputation4,484,166,969,124
root_title"OpenLedger trade engine bug or ..?"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id459,623
net_rshares3,813,400,371
author_curate_reward""
vote details (1)
@skriptroid ·
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.
properties (22)
authorskriptroid
permlinkre-cyranowitness-re-skriptroid-openledger-trade-engine-bug-or-20160729t190008178z
categorybitshares
json_metadata{"tags":["bitshares"]}
created2016-07-29 19:00:15
last_update2016-07-29 19:00:15
depth2
children3
last_payout2016-08-27 23:34:09
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length481
author_reputation563,630,330,217
root_title"OpenLedger trade engine bug or ..?"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id471,852
net_rshares0
@cyrano.witness ·
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.
properties (22)
authorcyrano.witness
permlinkre-skriptroid-re-cyranowitness-re-skriptroid-openledger-trade-engine-bug-or-20160729t201138108z
categorybitshares
json_metadata{"tags":["bitshares"]}
created2016-07-29 20:11:36
last_update2016-07-29 20:11:36
depth3
children2
last_payout2016-08-27 23:34:09
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length658
author_reputation4,484,166,969,124
root_title"OpenLedger trade engine bug or ..?"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id473,382
net_rshares0
@xeroc ·
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
👍  ,
properties (23)
authorxeroc
permlinkre-skriptroid-openledger-trade-engine-bug-or-20160728t083254400z
categorybitshares
json_metadata{"tags":["bitshares"],"links":["https://github.com/cryptonomex/graphene/issues/460"]}
created2016-07-28 08:32:54
last_update2016-07-28 08:32:54
depth1
children3
last_payout2016-08-27 23:34:09
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length193
author_reputation118,819,064,085,695
root_title"OpenLedger trade engine bug or ..?"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id429,540
net_rshares4,552,114,450
author_curate_reward""
vote details (2)
@skriptroid ·
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.
properties (22)
authorskriptroid
permlinkre-xeroc-re-skriptroid-openledger-trade-engine-bug-or-20160728t180149219z
categorybitshares
json_metadata{"tags":["bitshares"]}
created2016-07-28 18:01:54
last_update2016-07-28 18:01:54
depth2
children2
last_payout2016-08-27 23:34:09
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length264
author_reputation563,630,330,217
root_title"OpenLedger trade engine bug or ..?"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id441,876
net_rshares0
@xeroc ·
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.
properties (22)
authorxeroc
permlinkre-skriptroid-re-xeroc-re-skriptroid-openledger-trade-engine-bug-or-20160728t182904996z
categorybitshares
json_metadata{"tags":["bitshares"]}
created2016-07-28 18:29:03
last_update2016-07-28 18:29:03
depth3
children1
last_payout2016-08-27 23:34:09
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length137
author_reputation118,819,064,085,695
root_title"OpenLedger trade engine bug or ..?"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id442,545
net_rshares0