Or rather, is this a problem with the system as deployed or with a particular node not doing the job it's supposed to? Because if it's a problem with just the node, that can be fixed pretty easily and worked around in the meantime. If it's a problem with the system as a whole as deployed, and you can't really depend on the history account index for new account transactions on any node other than API.Steemit.com – that's an entirely different problem.
This is the fundamental problem of developers that do not document their code. To make my own thoughts clear, this is an issue with the Steem blockchain developers not with Beem or its developer. There is no promise that things should work this way and no warning that it doesn't but we naturally assume they should, and then we have angst when they do not work a certain way.
This problem involving history indexes should be mentioned to the Beem documentation. Although we don't know if it is a permanent problem or considered a bug by the Steem team.
You are right, I will add this to the beem docu. I think the solution is to use an index which is calculated from the block number, trx index, the operation index and an virtual op index.
complete. We hope to see all the ops that are going to the blockchain.
sequential: That is operation n+1 never happens before operation n. Although n+1 and n may happen at the same time. And if n+1 exists then n should exist. Things happen at the same time when they are part of the same transaction and may happen at the same time when they are in the same block.
consistent. We should get the same values and order no matter which host we use (at least within the context of the same blockchain).
Now, #3 is broken because of something outside of scope of Beem. I don't think you should put too much time into working around something that is probably a bug. Documenting that this natural assumption (#3) is wrong (hopefully temporarily), is a good idea, though.
If you are going to give the API users #1 #2 #3 by calculating and deciding on a order in a way that is independent of the Steem RPC node, then we could continue to use the history index number as a key to our transactions we store in our app's database's.
Your post was upvoted by @steem-ua, new Steem dApp, using UserAuthority for algorithmic post curation!
Your UA account score is currently 7.278 which ranks you at #65 across all Steem accounts.
Your rank has improved 1 places in the last three days (old rank 66).
In our last Algorithmic Curation Round, consisting of 391 contributions, your post is ranked at #12.
Good to know!
By the way...It shouldn't be "Be careful with account history index, it is not reliable" instead of "By carefull with account history index, it is not reliable" ? :D
Thank you so much for participating the Partiko Delegation Plan Round 1! We really appreciate your support! As part of the delegation benefits, we just gave you a 3.00% upvote! Together, let’s change the world!
You just got a 2.79% upvote from SteemPlus!
To get higher upvotes, earn more SteemPlus Points (SPP). On your Steemit wallet, check your SPP balance and click on "How to earn SPP?" to find out all the ways to earn.
If you're not using SteemPlus yet, please check our last posts in here to see the many ways in which SteemPlus can improve your Steem experience on Steemit and Busy.
This story was recommended by Steeve to its users and upvoted by one or more of them.
Check @steeveapp to learn more about Steeve, an AI-powered Steem interface.
Here's an important follow-up question:
Is it supposed to be?
Or rather, is this a problem with the system as deployed or with a particular node not doing the job it's supposed to? Because if it's a problem with just the node, that can be fixed pretty easily and worked around in the meantime. If it's a problem with the system as a whole as deployed, and you can't really depend on the history account index for new account transactions on any node other than API.Steemit.com – that's an entirely different problem.
This is the fundamental problem of developers that do not document their code. To make my own thoughts clear, this is an issue with the Steem blockchain developers not with Beem or its developer. There is no promise that things should work this way and no warning that it doesn't but we naturally assume they should, and then we have angst when they do not work a certain way.
This problem involving history indexes should be mentioned to the Beem documentation. Although we don't know if it is a permanent problem or considered a bug by the Steem team.
You are right, I will add this to the beem docu. I think the solution is to use an index which is calculated from the block number, trx index, the operation index and an virtual op index.
Posted using Partiko Android
We expect index numbers to be:
Now, #3 is broken because of something outside of scope of Beem. I don't think you should put too much time into working around something that is probably a bug. Documenting that this natural assumption (#3) is wrong (hopefully temporarily), is a good idea, though.
If you are going to give the API users #1 #2 #3 by calculating and deciding on a order in a way that is independent of the Steem RPC node, then we could continue to use the history index number as a key to our transactions we store in our app's database's.
Hi @holger80!
Your post was upvoted by @steem-ua, new Steem dApp, using UserAuthority for algorithmic post curation!
Your UA account score is currently 7.278 which ranks you at #65 across all Steem accounts.
Your rank has improved 1 places in the last three days (old rank 66).
In our last Algorithmic Curation Round, consisting of 391 contributions, your post is ranked at #12.
Evaluation of your UA score:
Feel free to join our @steem-ua Discord server
Useful information good job
Good to know!
By the way...It shouldn't be "Be careful with account history index, it is not reliable" instead of "By carefull with account history index, it is not reliable" ? :D
Lol! There's me!
This post has been included in today's SOS Daily News - a digest of all you need to know about the State of Steem.
Promoter of The SOS Forums : Weekly Discussion Forums on the State of Steem.
Co-ordinator of SteemClub-UK.
Editor of the weekly listing of steem radio shows, podcasts & social broadcasts.
Founder of the A Dollar A Day charitable giving project.
This post has been just added as new item to timeline of beem on Steem Projects.
If you want to be notified about new updates from this project, register on Steem Projects and add beem to your favorite projects.
Thank you so much for participating the Partiko Delegation Plan Round 1! We really appreciate your support! As part of the delegation benefits, we just gave you a 3.00% upvote! Together, let’s change the world!
Hi, @holger80!
You just got a 2.79% upvote from SteemPlus!
To get higher upvotes, earn more SteemPlus Points (SPP). On your Steemit wallet, check your SPP balance and click on "How to earn SPP?" to find out all the ways to earn.
If you're not using SteemPlus yet, please check our last posts in here to see the many ways in which SteemPlus can improve your Steem experience on Steemit and Busy.