Topic: [ANN] Woodcoin [LOG] Pure Skein POW, Logarithmic Release, No Premine nor ICO - page 10. (Read 126309 times)

Well it looks like it finally was included 77 blocks ago.

The networking portion of the clients I have worked on is identical to that for satoshi-client based bitcoin nodes - if a published transaction does not appear in the blockchain, it will periodically be rebroadcast.  It probably would be good to have some fine tuning for this functionality (like "resubmit TX now" button).  Maybe in the next version.  

For now if this happens again you can use the command line or debug console:  

gettransaction [txid]

to get the raw transaction in hex, and then copy that hex rawtx and use

sendrawtransaction [rawtx]

to manually resubmit it to the network.  Again, with some patience, this will happen automatically.    

I'm glad to see it worked eventually, thanks for your feedback!  


  

i added your nodes, but still no confirmations, here the tx id 803377fd57c36a8bde74cd3698b8bb972b50acd89f68db287450a7583405de32

木币狮子来



Who can add woodcoin logo please

Good morning!

Yeah, I'm not sure if skipped is the right word (the blocks still come in a numbered sequence with no numbers skipped) but you are right that the total number of blocks per day decreases.  Take a look at the chart for "Transactions"  here:

http://cryptoguru.tk/Charts/index.php?Currency=LOG

Everywhere it dips below 500 per day, we have kangaroo miners hopping across the outback with logs in their pocketses.

Hmm that sucks a TX not confirming, can you post the TXID?  It could be you aren't connected to many nodes for some reason.  Add this to your woodcoin.conf file:

addnode=217.77.59.45
addnode=96.33.131.50
addnode=73.61.69.113
addnode=80.229.163.230
addnode=92.214.191.144
addnode=83.252.17.134
addnode=76.64.74.218
addnode=163.172.28.249
addnode=92.170.141.48
addnode=67.205.162.80
addnode=163.172.90.105
addnode=199.231.215.253
addnode=104.236.96.120
addnode=5.9.233.99
addnode=23.242.89.131
addnode=50.166.119.69
addnode=67.35.116.81
addnode=199.231.215.252
addnode=167.114.103.43
addnode=185.86.148.224
addnode=110.10.176.94
addnode=45.55.152.37
addnode=106.185.41.253
addnode=159.203.76.85
addnode=82.144.204.28

There are some issues with the network interfacing between these clients.  I have not adjusted any parameters from those found in the "core" implementation because:  this should be a learning experience for us.  I mean seriously, some clients are programmed to consider another one "friend" or "enemy" based on whether the other reports a certain version name.  Can anybody defend this behavior?  

  




  

yeah but 17 blocks in 7 hours is way below the average of two minutes per blocks, which would have been 210 blocks in 7 hours, the 30 block with diff 80 in 14 minutes can't close this gap, so i see that some blocks are like skipped, not sure if this is the correct word
 
ah by the way i sent 150 log with the old 1.0.0 client and now they are stuck with no cinfirmations for 1 days already, how can i solve this?

Hi Ayers -
The net hashrate isn't staying the same.  There are miners hopping on the low difficulty and then moving off when it goes up.  You can see historically that when that hasn't happened, the difficulty is more constant.  Lets do the math ourselves for an exercise:

506340   2017-05-07 07:24:52    80.22
506369   2017-05-07 07:38:57    80.22

506370   2017-05-07 07:45:03   320.88
506387   2017-05-07 15:20:25    320.88

So we see in the first period, with difficulty 80, 30 blocks were solved in 14 minutes
This is about four times faster than our 2 minute per block target.  So, we adjust the difficulty to four times higher. 

In the second period with diff 320, 17 blocks were solved in 7 hrs plus.  Clearly, hashpower has left the network.  We are going to drop the difficulty to a factor of four lower (that's the maximum difficulty adjust we allow). 

We have discussed changing the difficulty adjust algo to minimize this kind of behavior but the general consensus is that it isn't worth the trouble.  Eventually people will realize they are wasting their time with this kind of thing and we should see smooth sailing, and in the meantime - hey the coin still works. 



 

i didn't try but it ask me to change the rpcallowip for non local ip it same it can't allow * in the rpcallowip, what should i put there i'm not familiar with this? also
i think there is something wrong with this coin, because with 1/3 of the net i can't find much block many block are solved by no one it see, i think i identified the problem, the diff retarget it's weird, if the net hashrate stay the same i see that the diff increase anyway 4x, this should not happen can you look into it?

Ah so it's working?  That icon on the woodcoin client looks like the older version?
How about with woodcore-RC1 version ? 
 

no look i made a complete image




oh i made it, it seems that the client for a strange reason don't like 4x00 port, but only 400x, you see there it think i have put 4000 port, instead was 4400

timed out means he is using the wrong rpc port i guess...

else -u and -p should also match the wallet rpc keys (but its another error in this case)

Shoot, well in that case you do have the right version set up, but something else is going wrong. 

My apologies Ayers.  For now I recommend you go back to using the old client or the pool.  While the newer client is spiffier it won't help you chop wood faster, nor are the logs a different quality.  I'll keep trying to fix this. 

Take a look at this thread to see other disgruntled miners trying to use ccminer:
https://www.dash.org/forum/threads/solved-solo-mining.5911/

Epsylon3 do you have any advice for us? 


 

yeah that is correct i get this

{
"midstate" : "660687c4f173fd3523fdd2670581c3353b15de37bc45fb0bda55e94d70222cb5",
"data" : "00000002d54673048f4ce9d7580aed82e9443e7513aa9c36d871f106d7b660d5b995bea2032b931 c8cddb42ef1beead18e9dcbbb8adaef5a0795e70a1e8114b2a6d870a1590b25d31c010881000000 0000000080000000000000000000000000000000000000000000000000000000000000000000000 0000000000080020000",
"hash1" : "0000000000000000000000000000000000000000000000000000000000000000000000800000000 0000000000000000000000000000000000000000000010000",
"target" : "0000000000000000000000000000000000000000000000000081080100000000"
}

Thanks!
Hmm that's odd..  if you open the help-debugWindow-console on qt and type "getwork" does it give you a response?

It should give you something like


08:30:15

getwork


08:30:15

{
  "midstate": "90b87f7ab77f090b87f7ab77f030b87f7ab77f0000e1dc3b77f0000",
  "data": "20000001696c8b1916e274be0459f7781a81fce409bc0465a5f0ad5afd0c4ec29503fed64cd43db 62d43c836740aa8769f3adc96398969c44c3e276b3336dc590b1ed7110000000000000080000000 0000000000000000000000000000000000000000000000000000000000000000000000000080020 000",
  "hash1": "0000000000000000000000000000000000000000000000000000000000000000800000000000000 0000000000000000000000000000000000000010000",
  "target": "0000000000000000000000000000000000000000000081080100000000"
}
 

i get this firewall is allowing the client, can't be that, everything else is right

Thanks Ayers, can you post the errors? 

i tried that version but i get getwork failed, everythign is correctly set and config is good? what's wrong?

Whoa!  That's a little strange.  Those alarms come sometimes because some malware uses your computer to mine coins, and our code does that (that's what we are doing here, except we keep the rewards).  The exact same alarms should go off if you run litecoin-core client or bitcoin-core client, seeing as it's the same code.

If you are worried the executable has been tampered with you can compare to the checksum I posted.  At any rate, you are using a windows machine so you know for a fact it is compromised.  Don't store life-changing amounts of any coin on there if it is online. 

Thanks for testing  

yeah the first qt is the one i need to try solo, but windows ask me that the publisher is not veryfied like the other official version posted here, the version is also very old 4.8.6, when most solo client use 5.3, there is the 5.3 somewhere?

LOL - I was waiting for others since the Windows build set off all kinds of alarms on my A/V.  Your first version with "getwork" did not set off my alarms.  So sometimes i like to wait because I am not the most technical person when it comes to A/V.

If you are looking for a windows build there are two here:

https://github.com/woodcoin-core/woodcoin-windows/

woodcoin-qt is the version mentioned above, built from the pre-core satoshi codebase

woodcore-qt is the "core" version, built on the bitcoin-core codebase, and so doesn't support the "Getwork" rpc call, nor the setgenerate-true built in cpu miner.   

You can also try :

https://github.com/woodcoin-core/woodcoin-windows/blob/master/RC1/woodcoin-qt.exe

which DOES have "getwork"  built on top of the "core" codebase, but this is currently untested. 

Has anybody tried it?  Pokeytex?  I'm curious if it works.