create account

steem-engine api history order problem for multiple txs in one block by blockchainstudio

View this thread on: hive.blog |  peakd.com |  ecency.com
steemfinex · @blockchainstudio · (edited)
$2.84
steem-engine api history order problem for multiple txs in one block
I've been worrying about this edge case, and it turns out that it's actually random.

For instance, in block 1896844,
https://steem-engine.rocks/b/1896844

there are two txs of @steemfinex (this is a very rare case and thank you for using it :)

when history is called, it returns the order randomly.

Same block, so  timestamp is the same, so no way to distinguish. no tx order is returned, so no way to sort.

Any other way to resolve this than fetching the block?
=> my solution is adding txid as the second sorting key

Hopefully, the order will be fixed.

---

스팀엔진 api history가져올때 같은 블록에 한 계정 여러 트랜잭션이 있으면 history api로는 소팅할 방법이 없는 문제가 있습니다. 블록에는 순서가 할당되어있긴한데 history에서는 현재 해결이 안 됩니다.
👍  , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , and 85 others
properties (23)
authorblockchainstudio
permlinksteem-engine-api-history-order-problem-for-multiple-txs-in-one-block
categorysteemfinex
json_metadata"{"community": "busy", "app": "busy/2.5.6", "tags": ["steemfinex", "steemengine", "zzan", "palnet", "steemleo", "neoxian", "marlians", "actnearn", "sct", "liv", "busy"]}"
created2019-09-15 15:27:12
last_update2019-09-16 08:22:09
depth0
children6
last_payout2019-09-22 15:27:12
cashout_time1969-12-31 23:59:59
total_payout_value1.243 HBD
curator_payout_value1.596 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length690
author_reputation178,988,499,015,921
root_title"steem-engine api history order problem for multiple txs in one block"
beneficiaries
0.
accountfinex
weight2,500
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id90,601,938
net_rshares9,847,738,166,309
author_curate_reward""
vote details (149)
@crokkon · (edited)
$0.02
properties (23)
authorcrokkon
permlinkpxvteg
categorysteemfinex
json_metadata"{"app": ""}"
created2019-09-15 16:49:09
last_update2022-09-18 07:41:57
depth1
children2
last_payout2019-09-22 16:49:09
cashout_time1969-12-31 23:59:59
total_payout_value0.010 HBD
curator_payout_value0.010 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length1
author_reputation81,214,366,861,104
root_title"steem-engine api history order problem for multiple txs in one block"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id90,604,254
net_rshares97,595,648,115
author_curate_reward""
vote details (2)
@blockchainstudio · 
yes, of course i can detect the situation.

and one way to resolve this by using history only is adding more sort key (txid should be enough) which is the way i'm thinking of atm. But it'd be much better if the api itself returns them consistently. 

e.g., steem has `transaction_num` and based on https://steem-engine.rocks/b/1896844 steem-engine seems to have such a thing. then why not returning them consistently.
properties (22)
authorblockchainstudio
permlinkre-crokkon-pxvteg-20190915t170219825z
categorysteemfinex
json_metadata{"community":"busy","app":"busy/2.5.6","format":"markdown","tags":["steemfinex"],"users":[],"links":["https://steem-engine.rocks/b/1896844"],"image":[]}
created2019-09-15 17:02:24
last_update2019-09-15 17:02:24
depth2
children1
last_payout2019-09-22 17:02:24
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_length417
author_reputation178,988,499,015,921
root_title"steem-engine api history order problem for multiple txs in one block"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id90,604,619
net_rshares0
@crokkon · (edited)
.
.
👍  
properties (23)
authorcrokkon
permlinkpxvvfu
categorysteemfinex
json_metadata"{"app": ""}"
created2019-09-15 17:33:09
last_update2022-09-18 07:41:54
depth3
children0
last_payout2019-09-22 17:33: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_length1
author_reputation81,214,366,861,104
root_title"steem-engine api history order problem for multiple txs in one block"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id90,605,653
net_rshares4,743,346,702
author_curate_reward""
vote details (1)
@sct.notice · 
* 태그 작성 가이드라인 준수는 콘텐츠 관리와 글에 대한 접근성을 높이기 위해 반드시 필요한 절차입니다. ( It is an essential step to adhere tags guideline, manage content and make access better to your postings.)

* 스팀코인판에서 활용 가능한 태그는 크게 [보상태그 / 언어태그/ 주제태그]로 구분할 수 있습니다. 보상태그와 언어태그는 필수입니다.(Tags that can be largely grouped into [Main Community / Language / Topic] in community. The language and topic tags are required.)

(예) 한국어로 작성한 자유 주제 포스팅((E.g) Posting for free topic in English)
* 보상태그: #sct 필수 (Main Community: #sct (required))
* 언어태그: #sct-kr 필수(Language: #sct-en (required))
* 주제태그: #sct-freeboard 필수(Topic: #sct-freeboard(required))
* 아래 보기에 있는 태그들 중에서 선택

> 보상태그(Main) : #sct

> 언어태그(Language) : #sct-kr #sct-cn #sct-en #sct-fr #sct-deutsch #sct-polish #sct-jp

> 주제태그(Topic) : #sct-freeboard #sct-dev #sct-invest #sct-market #sct-game #sct-movie #sct-book #sct-mining #sct-sports #sct-cartoon #sct-meetup #sct-diary #sct-bitcoin #sct-altcoin #sct-alliance #sct-userguide #sct-otc #sct-prediction #sct-qna
(원하시는 추가 태그가 있으면 [여기](/@sct.hboy/notice-sct)에 댓글을 작성하여 주십시오.)
(If you want to add a tag, please comment [here](/@sct.hboy/notice-sct).)

* 태그 작성 가이드라인을 준수하는 것이 태그 사용을 규제하는 정책보다 스팀코인판의 가치를 높이는 길이라고 생각합니다.(We believe that adhering tags guideline is a way to increase the value of SteemCoinpan community than that of forcing tags limitations.)

---

<center>![KakaoTalk_20190607_112035846.png](https://steemitimages.com/150x0/https://cdn.steemitimages.com/DQmW4gUFWAS6baZ1kFRbonpVs6AoucNfmZQVctE7fLABiTq/KakaoTalk_20190607_112035846.png)
</center>

---
properties (22)
authorsct.notice
permlinkre-blockchainstu6392
categorysteemfinex
json_metadata"{"community": "busy", "app": "busy/2.5.6", "tags": ["steemfinex", "steemengine", "zzan", "palnet", "steemleo", "neoxian", "marlians", "actnearn", "sct", "liv", "busy"]}"
created2019-09-15 15:27:18
last_update2019-09-15 15:27:18
depth1
children0
last_payout2019-09-22 15:27:18
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_length1,523
author_reputation60,586,092,807
root_title"steem-engine api history order problem for multiple txs in one block"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id90,601,942
net_rshares0
@steem-ua · 
#### Hi @blockchainstudio!

Your post was upvoted by @steem-ua, new Steem dApp, using UserAuthority for algorithmic post curation!
Your **UA** account score is currently 6.405 which ranks you at **#193** across all Steem accounts.
Your rank has not changed in the last three days.

In our last Algorithmic Curation Round, consisting of 103 contributions, your post is ranked at **#16**.
##### Evaluation of your UA score:

* You've built up a nice network.
* The readers like your work!
* Try to work on user engagement: the more people that interact with you via the comments, the higher your UA score!


**Feel free to join our [@steem-ua Discord server](https://discord.gg/KpBNYGz)**
properties (22)
authorsteem-ua
permlinkre-steem-engine-api-history-order-problem-for-multiple-txs-in-one-block-20190916t084621z
categorysteemfinex
json_metadata"{"app": "beem/0.21.0"}"
created2019-09-16 08:46:24
last_update2019-09-16 08:46:24
depth1
children0
last_payout2019-09-23 08:46:24
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_length686
author_reputation23,214,230,978,060
root_title"steem-engine api history order problem for multiple txs in one block"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id90,624,248
net_rshares0
@steemitboard · 
Congratulations @blockchainstudio! You have completed the following achievement on the Steem blockchain and have been rewarded with new badge(s) :

<table><tr><td><img src="https://steemitimages.com/60x70/http://steemitboard.com/@blockchainstudio/comments.png?201909151642"></td><td>You made more than 5500 comments. Your next target is to reach 6000 comments.</td></tr>
</table>

<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@blockchainstudio) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=blockchainstudio)_</sub>
<sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub>


To support your work, I also upvoted your post!


> You can upvote this notification to help all Steem users. Learn how [here](https://steemit.com/steemitboard/@steemitboard/http-i-cubeupload-com-7ciqeo-png)!
properties (22)
authorsteemitboard
permlinksteemitboard-notify-blockchainstudio-20190915t171829000z
categorysteemfinex
json_metadata{"image":["https://steemitboard.com/img/notify.png"]}
created2019-09-15 17:18:30
last_update2019-09-15 17:18:30
depth1
children0
last_payout2019-09-22 17:18:30
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_length910
author_reputation38,975,615,169,260
root_title"steem-engine api history order problem for multiple txs in one block"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id90,605,196
net_rshares0
Help/Feedback