RE: Nectar.Hive - Slipping on a new API
(Edited)
You are viewing a single comment's thread:
I took a look at hivehub.dev and it looks like the active key is needed. Here is a link to one of the failed tx attempts. I am glad to see you have it to this point, and make sure not to accidently put your keys on github.
0
0
0.000
I have placed the active key into the code. I'm going to have to dig a little more to figure out where I went wrong at.
After u added the active key did it post to hive nodes?
That would show up on HiveBlocks right? I'm sorry if I'm not grasping the terminology.
Yes, if you try again with the active key I think it will work. After you try it should show on hiveblocks with any error or success if it consumes RC.
So just the active key or both keys? I'm still having the same problem its being signed locally I believe but not reaching a Node... I think. I'm not 100 percent sure.
Maybe just the active, it is still showing the same error but it did hit a node and try to post. Recent attempt here
I appreciate the help and patience with my lack of knowledge.
No problem at all, I still have no clue how to set any of the stuff up through python. So you are helping me learn through trying to help you.
Python is the only thing I really know... and some HTML and a lil java
Is there a way to add wait 3seconds, check block id, then check bal? It looks like you are burning a ton of rc on failed transactions at the moment.
Maybe. I'll go back and clean it up, maybe add a few minutes in between.
The bot is working now though you were right about the active key... I was missing forcing it later in the code.