You already missed mining the HBIT token yesterday (UTC), but you still have about 8 hours to mine the token today! 🤗 !HOPE !INDEED !WEIRD !PIZZA !ALIVE
You are viewing a single comment's thread from:
Sort: Trending
When one window closes, another window opens. Or something. :D
!HBIT !ALIVE !BBH !LADY
You tried to mine HBIT with more than 2 other bot commands on the same comment, which would cause the HBIT bot to not process the HBIT token mining command on your comment there. 🤯😅
I hope that you can fix your HBIT token mining bot quickly! 🤗 Nevertheless, just in case that you want to disable automated comments from your HBIT bot (like what most Hive token tipping bots now do), you should remove the code where the bot attempts to publish comments (using the private active key which will continue to fail because of the 28th Hive Hard Fork). 🧘♂️
Anyway, there seems to be troubles using the private active key too to send tokens, both manually by Hive users using #HiveKeychain, #Hivesigner, and other signing apps/extensions for Hive, and automatically through Hive bots/scripts. 🤯🤓
This is likely on the right track. I'm seeing an error regarding keys. Haven't been able to look closely yet though. Jelpful info here, thanks.
You should just insert the private posting key on the code responsible for publishing comments on your !HBIT bot to fix the commenting problem, while keeping the private active key there for sending the HBIT and BLAQ-based tokens. 🤓 !HOPE !INDEED
I !HOPE that you are not trying too hard to reply to my comments while you are very busy in real life! 🤗
Anyway, here's my !HBIT (not just WUSANG) token mining attempt !INDEED for today (UTC)! 😎
Well I'll try it again with just the one !HBIT command and see what happens.
While we're testing things, if you see this in the next few minutes could you pop on over to https://peakd.com/ktest/@ktest/tokenfaucet-command-bot-version-v1b71120251-test-1 and test that? Thx! :)
Your HBIT token mining command there !INDEED worked according to #HiveEngineExplorer, though the HBIT bot just didn't publish a comment regarding your successful mining. 🤔🤯 !HOPE that you don't forget to mine the HBIT token today! 🤗😏 !INDEED !WEIRD !HUG
Your HBIT token mining command there yesterday (UTC) is successful according to #HiveEngineExplorer! 🤔😎 Don't forget to mine HBIT today! 🤗😏 !HOPE !INDEED !WEIRD !PIZZA
Your HBIT token mining command yesterday (UTC) was successful according to #HiveEngineExplorer! 😎😏 !WEIRD !INDEED
The HBIT token mining bot has resumed publishing automated comments since about 29 hours ago. 🤔😎 Don't forget to mine HBIT within the next 8 hours! 🤗😏 !HUG !HOPE
I just told @savvytester to test your #tokenfaucet test bot on the test post, though I don't know when they would be online on Hive to perform the testing. 🤗 They could be online anywhere from a few minutes to several hours from the time of this comment. 😅
I responded to @savvyplayer's request to try out the !TF command on your bot's post. 🤔🤗 Maybe you want me to invite other Hive users I often talk with (such as tydynrain) to help with the testing! 😎😏 !HOPE !INDEED !WEIRD
I noticed the edit on your test post, where it says that works fine and was turned off after the first 2 Replies here. 🤔 Are those 2 replies from @kennybot and your main Hive account, such that @savvytester's comment there was not part of those "first 2 replies"? 🤯😅 !WEIRD !LOLZ
Maybe the thing that you wanted to be tested was that whether your bot being turned off will still process my !TF command on that test post. 🤔🤯 !PIZZA !HOPE
Anyway, I find it unusual to see you reply (to @savvyplayer in this case) with only one word (excluding token tipping commands)! 🤯😅 !WEIRD !INDEED