RE: Duplicate account history entries on STEEM: How to detect and fix them

[mintrawa]

Interesting discovery, does each node server return the same replication pairs?

At first glance, the core seems to be correct since the error only appears at the API level and and does not seem to be present on the Hive API? A problem occurred since they changed some things to control the data displayed on third party's frontend?

---

Witness FR - Gen X - Geek 🤓 Gamer 🎮 Traveler ⛩️

Comments

[holger80]

I checked the results on several nodes and the results for my account were the same. I think the error can also appear on Hive. It just did not happen currently for my account.

The error is on the API level, the balances that are returned for an account are correct.

[mintrawa]

Thanks for the information, I just made the test via Postman with the function get_ops_in_block and all the transactions of the block 41868606 are duplicated in the answer

{
    "jsonrpc":"2.0", 
    "method":"account_history_api.get_ops_in_block", 
    "params":{"block_num":41868606,"only_virtual":false}, 
    "id":1
}

So after some cross-checking I went back up to block 41868590 to finally have a block where the transactions inside are not duplicated. In the other direction, I had to get to block 41868612 for it to finally stop.

---

Witness FR - Gen X - Geek 🤓 Gamer 🎮 Traveler ⛩️

[holger80]

What do you mean by duplicate?
https://hiveblocks.com/b/41868606
shows no duplicate entries.

[mintrawa]

I don't mean inside the blockchain but in response to an API call account_history_api.get_ops_in_block.

Problem in the range of 20 blocks 41868591 -> 41868611 (1 blocks/3 seconds mean 1 minute)

---

Witness FR - Gen X - Geek 🤓 Gamer 🎮 Traveler ⛩️