[ANN] Woodcoin [LOG] Pure Skein POW, Logarithmic Release, No Premine nor ICO

[tryphe]

Hey!  Hey!  Put the hatchets down a second, lets chat.  

So, I had been working on "woodcoin-b", which was just another woodcoin wallet / full node, but built on a fork of the current bitcoind / bitcoin-qt  version as pushed by "the power rangers", a.k.a. what you get at github.com/bitcoin/bitcoin.git.  

The idea was, why not have another client?  It can't hurt and could strengthen the network.  Currently, the reference client for woodcoin is, at least is afaik what most you folks run, a fork of litecoin with the woodcoin algos and genesis block dropped in, as advertised at github.com/funkshelper/woodcoin.git.  Woodcoind and woodcoin-qt : solid, reliable, and fast wallets.    



So then last week, the litecoin team (that is, the folks who update github.com/litecoinproject/litecoin.git), comes out and "moves to the 0.10 branch".  I'm not going to get into what that means for litecoin, but basically it means I have to make some decisions on which codebases to maintain here.  Simply saying "git merge" won't work here.  


I'm not going to pretend that any of this controls the coin.  Github could drop off the face of the  earth, and me as well (and by the way, we both will), and woodcoin won't really care.  However, I am going to do what I can to help the codesbases that I see as important while I can.  In this regard, I am going to maintain our current reference client as is (forked from litecoin 0. as long as possible.  A source tarball, with checksum and signature, sits at woodcoin.org/woodcoin.tgz at the moment (see download page for details).  I encourage you to grab a copy just in case.  

I'm also going to try to continue with a full whatever-we-find-at-bitcoin-github client, to be merged with any changes to that project.  

-And- I am going to make a 0.5.3 woodcoin reference ciient (no gui), to be merged with any changes to that project (see thebitcoin.foundation for more info on that project).  

However I don't at the moment see any need to try to duplicate the direction github/litecoinproject is going, that is we don't need to merge changes into our reference client in that way, not if the above two project are being maintained.  Of course if you want to do that, you are welcome to it.    

Please let me know if you have any concerns over the state any of this software is in, or have better ideas.  Other related projects on the table for bounty:


LOGd (fork of BTCd written in GO)
LOG Android Wallet  


OK, thanks for listening.  This has been a forest-wide public service announcement brought to you by:

funkenstein the dwarf
  

This is really awesome.

I wholeheartedly agree with your "no merge" statement. If we're going to have a concensus network with multiple clients, a free range of used code would be best rather than everything being inherent of something else. So, for example, let's use the same general idea, but I really like how each project will take on a level of ambiguity of its own.

As for the direction of code, "In Funk We Trust" really comes to my mind. I think I can give a really sucessful example for a coin I've been involved a little bit in for a while. When Clams started out nearly a year ago, it was simply a fork of Blackcoin, which had its inherent forks (Peercoin, and so on). Now, however, it's taken on multiple characteristics of its own, and doesn't follow any code line of any other coin. The most important thing is when to know (key word, when) you should add a commit, and when not to. For example, it has some BIPS implemented, and some not implemented. It has the bitcoin autotools build system, which most coins don't have but has become a huge asset. I could go on and on here, but just one of these things can make a huge difference in the overall prospect of our user base, while another could make them neutral or turn them away. The important thing is leaving out the "extra", or feature creep that will turn users off. Again, it depends on the time. This is what makes coins truely great. From my experience, it's important to simply make the best decision on behalf on the coin at its current state (however impossible that may be) and not try to dilute it into just "being like these other coins". This is where your personal preference comes in, and you need to nitpick the code. There really isn't any other way. This is what will make Woodcoin, Woodcoin.

I almost think any indirect question regarding how to aim the project properly is almost a fallacy, but I see where you're trying to go with getting a general concensus of code direction. These new projects (in my opinion) should broaden our base for incoming developers, so that's the best thing really to do. I think in the case of Woodcoin, you really are the best judge. In fact, that's really the best thing you can do. In my opinion, this is what separates your style and other coin devs that would simply add feature creep. You're a thinker before a doer.

I hope that made a little bit of sense.  

TLDR: In Funk We Trust!

[funkenstein]

This is really awesome.

I wholeheartedly agree with your "no merge" statement. If we're going to have a concensus network with multiple clients, a free range of used code would be best rather than everything being inherent of something else. So, for example, let's use the same general idea, but I really like how each project will take on a level of ambiguity of its own.

As for the direction of code, "In Funk We Trust" really comes to my mind. I think I can give a really sucessful example for a coin I've been involved a little bit in for a while. When Clams started out nearly a year ago, it was simply a fork of Blackcoin, which had its inherent forks (Peercoin, and so on). Now, however, it's taken on multiple characteristics of its own, and doesn't follow any code line of any other coin. The most important thing is when to know (key word, when) you should add a commit, and when not to. For example, it has some BIPS implemented, and some not implemented. It has the bitcoin autotools build system, which most coins don't have but has become a huge asset. I could go on and on here, but just one of these things can make a huge difference in the overall prospect of our user base, while another could make them neutral or turn them away. The important thing is leaving out the "extra", or feature creep that will turn users off. Again, it depends on the time. This is what makes coins truely great. From my experience, it's important to simply make the best decision on behalf on the coin at its current state (however impossible that may be) and not try to dilute it into just "being like these other coins". This is where your personal preference comes in, and you need to nitpick the code. There really isn't any other way. This is what will make Woodcoin, Woodcoin.

I almost think any indirect question regarding how to aim the project properly is almost a fallacy, but I see where you're trying to go with getting a general concensus of code direction. These new projects (in my opinion) should broaden our base for incoming developers, so that's the best thing really to do. I think in the case of Woodcoin, you really are the best judge. In fact, that's really the best thing you can do. In my opinion, this is what separates your style and other coin devs that would simply add feature creep. You're a thinker before a doer.

I hope that made a little bit of sense.  

TLDR: In Funk We Trust!

Tryphe!  Your vote of confidence is much appreciated.  My nitpicking has just begun.  Since I first released woodcoin, I have learned a log truck load about the bitcoin codebase and operation of P2P currency networks.  I plan to make sure woodcoin stays on the woodcutting edge of the altcoins in stability, longevity, and useability.    We are just  getting started.  I will check out clam and autotools to see what I can learn there.  People prefer different kinds of clients, that is natural and healthy. 

As to exchange, c-cex has proved reliable and trustworthy compared to other similar venues; of course it remains a counterparty risk so the usual provisos apply.  I wouldn't put too much stock in prices reflected in very low volume, however it remains the only public establishment in which one can obtain the genuine article: LOG. 

 

[funkenstein]

New all time high - difficulty 24

Half a gigahash/sec of double skein. 

Nice chopping folks! 

[Houndirno]

It's ashame theres no Rentable DoubleSkein rigs ;c

[funkenstein]

Moar Noads: 


"addr" : "172.245.60.101:8338",
"addr" : "178.33.126.221:8338",
"addr" : "84.90.149.57:8338",
"addr" : "104.236.69.105:8338",
"addr" : "37.187.27.4:8338",
"addr" : "199.193.248.126:8338",
"addr" : "104.131.102.63:8338",
"addr" : "95.28.5.181:8338",


It is recommended to keep a list of working nodes handy, in case of emergency.  Here are eight that are working today. 

[myagui]

It's ashame theres no Rentable DoubleSkein rigs ;c

I could rent my industrial grade chopping gear: well oiled, razor sharp chain, chops away like there's no tomorrow!
The total chopping power is ~15 horsepower at 20.000 RPM, which translates to about 300MH/s DoubleSkein 
Safety Equipment is not included.

Feel free to PM if interested.

[tryphe]

We hit 1k on c-cex today! 

[SalimNagamato]

funk where are you ? not posting about pluto ?

[bitillionaire]

https://www.cryptocoinsnews.com/ccn-episode-13-middle-earths-cryptocurrency/

Interview with a man who claims to have worked intimately with our own Funkenstein.

[funkenstein]

funk where are you ? not posting about pluto ?

Thanks Salim, I am back!  



The Dwarf Planet has been visited by a human probe, and some of our mountains imaged by human cameras.  A new horizon indeed.  

Good thing too, Charon will be needed to guide Sir Fiat across the rivers Styx and Acheron.  

One more for you  

[funkenstein]

https://www.cryptocoinsnews.com/ccn-episode-13-middle-earths-cryptocurrency/

Interview with a man who claims to have worked intimately with our own Funkenstein.

Nice find Bitillionaire!! 

Props to Paul Madore for releasing this interview.  Sal was totally unprepared as usual but worth a listen anyway.

   

[kahir]

is there nvidia ccminer windows binary ?

[SalimNagamato]

is there nvidia ccminer windows binary ?

I think this can mine woodcoin, -a skein2


https://github.com/tpruvot/ccminer/releases/tag/1.6.5-tpruvot

[funkenstein]

Nice chopping kids! 

Difficulty continues to rise on woodcoin.  New high today crossing diff=30 line for the first time, presumably a few more folks using the GPU chainsaws. 

Keep up the good work  

[Blawpaw]

is there nvidia ccminer windows binary ?

I think this can mine woodcoin, -a skein2


https://github.com/tpruvot/ccminer/releases/tag/1.6.5-tpruvot

nope...

I'm running W7 and can't get it to mine... Even so I dont even know if this is worth mining...
What's the best CPU miner for Windows?

[Monopoly]

I got connections but not downloading blocks ........... restarted wallet but still there is problem....

[funkenstein]

I got connections but not downloading blocks ........... restarted wallet but still there is problem....

Connected yet? 

You may have to try using "addnode"  manually with one of the nodes listed in the thread above. 

Please post if you are still having problems, thanks!   

[funkenstein]

These nodes have been very reliable:

37.187.27.4
85.25.214.175
104.236.69.105
144.76.238.2
82.247.134.167
178.33.126.221


Please post your connected node lists! 

Thank you

[funkenstein]

More nodes for my woodcutters:

        "addr" : "199.231.215.252:8338",    <-- dnsseed.woodcoin.org  should resolve here
        "addr" : "104.131.102.63:8338",
        "addr" : "37.187.27.4:8338",
        "addr" : "178.33.126.221:8338",
        "addr" : "144.76.238.2:8338",
        "addr" : "83.222.84.128:8338",
        "addr" : "85.25.214.175:56885",
        "addr" : "83.222.84.128:59139",
        "addr" : "104.131.102.63:34259",
        "addr" : "178.33.126.221:37391",
        "addr" : "104.236.69.105:8338",
        "addr" : "104.236.69.105:43566",
        "addr" : "188.134.72.213:61647",
        "addr" : "80.236.18.96:50271",
        "addr" : "67.35.116.81:62825",

Keep up the good work; winter's a comin'. 

[funkenstein]

Quick network update: 

Today we reached Difficulty=32.24   new ALL TIME HIGH. 

600+ MSkein/s 

All systems go.  Keep up the good work woodcutters!