Jminer "unconfirmed transactions failure" Debug mode
-
Solo mining with Jminer. In debug mode =true I get a message that says failed to get "unconfirmed transactions" to trigger server. I saw I had a "confirmed" 127 sec DL sitting for a 5 minutes and never got the block, so even though confirmed I think this message is telling me my wallet is not "connecting" with the bulk of the world. What think you?
-
@rds triggerServer not needed for mining at all, it was a test feature, if simulating a open wallet (same requests) would solve issues with stuck/late wallet sever (but seams to have no effect at all)... you can just turn it of by triggerServer=false (thats the default, so you run a old version or you have triggerServer=true).
About you deadline, it seams it never made it to the network (maybe wallet not connected to enough peers) Or your wallet was busy 'failed to get "unconfirmed transactions" to trigger server' indicates it was ... as this message also showed up a lot on the spam attacks to the network.
-
@rds Next version of jminer will have special solo mining feature to commit promising deadlines a few times ... e.g. every 2sec. to ensure/improve the chance that it get propagated ... since i test that, i had no such cases you reported anymore ... maybe next we.
-
@luxe I have 0.4.8, is that the latest?
-
@rds At least you should be able to disable triggerServer. https://github.com/de-luxe/burstcoin-jminer/releases
-
@luxe said in Jminer "unconfirmed transactions failure" Debug mode:
@rds At least you should be able to disable triggerServer. https://github.com/de-luxe/burstcoin-jminer/releases
ok, thanks
-
@luxe I like the sound of this 'hammer the server until it accepts your deadline' feature. :)
-
is there calculative approach to deadline submission say in accordance to plot size on solo mode? a chart would be useful say on a per terabyte basis?
-

