Well yeah.  Private issuance means there is no verifiability.  We all know how this works.  The issuer of the paper notes issues far more notes than there are bitcoins to back them up.  Their ability to issue new notes amounts to an ability to steal from everybody else ad libitum.   

A better way to transact offline is to use a bitcoin check  (private key on a piece of paper with some information).  This requires you have some trust or KYC but that's really not such an uncommon thing in most of our transactions.  Each transaction in this case winds up being put on the chain eventually, when the payee is finally able to get online...  and if they never do (or not within an agreed upon time), the payer keeps a copy and can claw back the funds. 

 

^  ^  ^  
Nice soundtrack

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!  


  

木币狮子来



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?  

  




  

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. 



 

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

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? 


 

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"
}
 

Thanks Ayers, can you post the errors? 

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  

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. 

 

Hey thanks bathrobehero   I am going to read the code on the coins you mention and do some more research.

I don't think having multi-algos eliminates the threat of a 51% attack or double spend, but it could make it more difficult in some circumstances.  If there is a liquid market of hashpower, see e.g. nicehash, then one can always buy the hashpower one needs to make an attack.  Anyway I am going to take a closer look at the consensus mechanism. 

If we were to shift to a multi-algo system, what other hash functions do you think would be appropriate, other than double-skein? 

"Nobody can allow that".  Well.  What happened to the USA?  And so many other places?  Exactly what you describe.

However, with fiat, the people who have "a lot in their wallets" really have an unlimited amount in their wallets.  "Let me issue the currency and I care not who makes the laws"  etc. etc.  They can issue as much as they like at any time, and if you are willing to part for your resources in exchange for this paper, you are easily bought out.  With bitcoin and other public cryptos the amount is limited.

Bitcoin represents the end of financial colonialism.  About fucking time

Completed trade meeting in person.  Thanks! 
Legit, will trade again  

Ineteresting, yes I like the myriadcoin approach.  I think the difficulties of each algo there retarget independently from each other. 

It's interesting that 30 blocks to retarget (at 1 block per 2 minutes) appears slow; compared to LTC or BTC this difficulty adjust is lightning fast.

At various points over the last couple years we've talked about changing the difficulty adjust and/or POW algorithm of LOG.  Anything is possible if this is too annoying to deal with.  A change to a myriad-like network is attractive, what do you think?  Another possibility offering even more stability is moving to a merge-mined system.  However it seems that our fluctuating difficulty is not really such a headache.  Hop miners are still adding their hashpower to secure the network.  As we grow in size these effects will be relatively smaller. 

     

Step 1)  Start mining your own Foocoin chain without publishing it.  Include other transactions you hear on the network if you like, or don't.  Up to you.  What's important is that that you are solving blocks on this private fork with more hashpower than the rest of the network all put together. 

Step 2)  Make a large purchase using a Foocoin transaction.  Publish this transaction on the public chain, but NOT the one you are mining on privately.  On your private chain, make a transaction moving those Foocoin to another address you control (this is the double spend). 

Step 3)  Once the transaction is complete and you have walked away with your goods, publish the private chain you have been working on.  Because it has 51% of the network hashpower, it is now the longest chain and nodes will reorganize their block chains to reflect this "new" history.

And presto, the block chain no longer shows the transactions in step 2 - the foocoins are back in your control - and yet you still have the goods.       

An old article from now defunkt blog on the topic if you are interested to hear more : 
https://web-beta.archive.org/web/20160827095420/http://frass.woodcoin.org/godzilla-vs-the-51-attack/

Thanks for asking Ayers  Rather astonishing swings of hash rate last week!!  I've never seen anything like it on any other coin.  In addition to price changes, and pools going off and online, the drive-by woodcutter is back in full effect.  

Yes the network has been undergoing this stress-test off and on for almost a year now.  It does appear that there is a single entity which controls enough hashpower to perform a 51% attack.  However they only leave it on for short bursts of time, and there has never been a report of a doublespent transaction, in private or from any exchange.  Lets put it this way: on no exchanges is woodcoin the lowest hashrate coin (or most 51%able) to choose from.    

My agents tell me that this party probably has somewhere from 20 to 80 top of the line nvidia GPUs they are throwing at our network.  However just like bitcoin, there could also be efficiency increases in performing the hash algorithm.  The question of why is an interesting one, it doesn't appear the the technique does much for our drive-by wood cutter apart from an upward pressure on the price and a some extra time to mine another coin with the rig during the high difficulty times.  It could be an exploratory technique.   

At any rate, the concern is a real one.  I believe exchanges that accept small-cap currencies without any know-your-customer do so carefully, not just by requiring multiple confirms but also by delaying any large withdraws from accounts that have recently input small-cap deposits, with random delays, and with maximum withdraws per day.  I believe we'll see more double-spend attacks on small-cap coin exchanges in the future, so your warning is a good one.  

Heya pokey!  

Try this one out and see if it does anything.  I built myself but haven't tested on windows or with ccminer yet, so I would put the chances of it working out of the box somewhere in the slim to middlin' range.  

https://github.com/woodcoin-core/woodcoin-windows/tree/master/RC1

sha256sum *.exe
869faaf0645dc445e2ccb1e4cdf9f454bd9edf28bbe9dd10eac5e040328b9250  woodcoin-cli.exe
42d8d49c7291e96218624752f8e60488f14f890e306e43e2fc2e6b8518018681  woodcoind.exe
e0b82e9298fbcb64e6f39e775ba92bd2a3f6161b48a73aa5bf7e5ff82be84b5f  woodcoin-qt.exe
29299257a0671dd15005b79817f6b9cbc6a19fc7e57f9e63a771081509852c48  woodcoin-tx.exe

Aye aye cap'n crunch,

Well that's odd, I still haven't gotten this thing to link properly to boost libraries using HOST=x86_64-w65-mingw32.  And now my afternoon time limit is up. 

My apologies once again.  In the meantime, mine with the old version please, I'll bang my head against this thing again tomorrow.