You are viewing a single comment's thread from:
RE: [recovered] steem-engine api is experiencing delays
If you're running some type of exchange using steem engine I would suggest you run your own node, or at least stream the blocks directly from a public node, rather than rely on the account history API service.
Hi @yabapmatt, thanks for your advice. Running a node may not be an option for me at this stage. I was actually considering block streaming, but isn't https://steem-engine.rocks/ using block streaming? I found that it also sometimes shows the transaction not in chronological order. Is it due to that explorer's implementation or even block information can be unreliable in some cases?
And could you let me know why account history api is so unreliable? Is it due to many requests or bugs?
ps. please don't hate my @steemfinex. I'll increase the fee after some testing, and you know it's good for users to use more steem-engine. As you know, steem-engine doesn't get any attention from outside til now, and actually this kind of attempt should be appreciated because it means there is someone who cares about it :) You guys can think like STEEMP is listed on another cool exchange :) and imho, steem-engine shouldn't rely on fee revenue too much. Ad is much more important. I'll keep contributing to keychain and others. Thanks!
The account history API is meant just for front-ends to be able to show account history to users, nothing more, and it's a separate service from the Steem Engine node software. By streaming blocks you're at least getting the data directly from the Steem Engine node itself rather than a secondary service. It's pretty easy to do using the sscjs
stream()method. Message me on discord if you need any help with it.Sure many thanks! But I also hope that api's more reliable since keychain is also using it.