Hi @biophil
Can you confirm something for me.
The confirmer sends a confirmation comment but the pending confirmation stays in the DB until the comment is actually found inside the blockchain. That means if the RPC are delayed, the confirmer will re-attempt to send another confirmation comment because it is still returned by get_next_confirmation() call. But that is OK because you are using a custom permlink so steem should not allow you to create another comment with the same permlink. Am I right?
That's right, but it might be smart to include extra logic to prevent wasting time double-confirming. Keep track of which confirmations you've posted and make sure you don't re-post those. I can't remember if I did that or not in the Python implementation.
I'll do a first release with the initialof logic first.
Then I can use a local cache with a TTL of say one hour to keep track of already confirmed transactions.
I have a beta Pocket-JS running now with @pocketjs.
ULOG 018 - Pocket-JS test run
It's missing the following:
Cool! So it requires a post-genesis db file?
Currently yes.
But I made this little python script that exports your confirmer MistDB into a post-genesis db.json file that can be used as is with pocket-js
https://github.com/quochuy/pocketjs/blob/master/bot/utils/convertDb.py
Hello friend I see that your posts are very interesting I will be pending for when you upload any you do a good job greetings