been going at this damn thing for 6 hrs straight now. I remember why I've been putting it off for so long.

BTW I told Davinci that I wouldn't release this publicly for at least a week after he got it which I think is fair given the hefty bounty he's posted. However he generously declined the offer and requested I make it available to everyone immediately so if you do use it please consider making a donation to Davinci because I certainly wouldn't have gotten off my lazy arse to finish if he hadn't dangled the carrot in front of me.

Awesome dude send me your address and I will send the first 100 right away.Nodemaster has his own test net with the difficulty at crazy low value for namecoinsadd this to yoru bitcoin.conf with noirc=1

addnode=78.47.40.55:18334

However I am not sure if he as taken it down. Create a VM and check I'm busy trying testing your code.

Just uploading rev .02 atm. Found a deadlock in the work submit thread. There's some awfully convoluted syncing that has to go on there.

about 6 mins to go on my lightning internet connection.

also, recommend that you set 'forceAllSubmitsUpstream' until it's proven that it detects winning shares. There will be a log file created in yr launch directory called 'real-share-submits.log' that tracks the progress of a suspected winning share through the server and gives the info we need to prove it's going to work without the force option switched on.

So what happens to the shares table with merged mining option enabled?

Can you confirm, that upstream result from each row refers to the parentchain (btc) only? So the upstream results from the merged chain is currently not in the database right?

The upstream result should be true for both chains for now and you just check your wallet to see witch block chain got it. In the future shadders can add column in the database or a new table (preferable) that indicates witch block chain found a block.

So what happens to the shares table with merged mining option enabled?

Can you confirm, that upstream result from each row refers to the parentchain (btc) only? So the upstream results from the merged chain is currently not in the database right?

The upstream result should be true for both chains for now and you just check your wallet to see witch block chain got it. In the future shadders can add column in the database or a new table (preferable) that indicates witch block chain found a block.

Thanks DavinciJ15, this solution works fine for me.

May i ask if you found a 4diff patch which can be compiled with the current bitcoind version vom vinced?

Quick question on poolserverj - is there by chance a config setting that will let me change the difficulty for 'accepted work'? Haven't had a chance to take a closer look at the source yet, figured somebody else might know.

The reason I'm asking is I'm considering porting it to make a pool for litecoins, but of course would ask permission if I had to modify any of the source (I did manage to take a brief look at license.txt while perusing a bit of the poolserverj code ).

I'd prefer this over pushpool because I like Java.

As far as I can tell anything other than share difficulty would have an easy workaround to get litecoind and poolserverj to work together (in terms of, if I run into an issue, I can make another program of my own to translate between the two, or modify litecoind).

Quick question on poolserverj - is there by chance a config setting that will let me change the difficulty for 'accepted work'? Haven't had a chance to take a closer look at the source yet, figured somebody else might know.

The reason I'm asking is I'm considering porting it to make a pool for litecoins, but of course would ask permission if I had to modify any of the source (I did manage to take a brief look at license.txt while perusing a bit of the poolserverj code ).

I'd prefer this over pushpool because I like Java.

As far as I can tell anything other than share difficulty would have an easy workaround to get litecoind and poolserverj to work together (in terms of, if I run into an issue, I can make another program of my own to translate between the two, or modify litecoind).

No need to ask permission to modify psj. It's GPL. Earlier versions were no-derivs creative commons license but that's long gone. However, I don't think you'll need to. Take a look at the very end of the sample properties file. There is actually an option to set difficulty though no one's ever used it in production as far as I know. I would recommend after setting you do a manual getwork and inspect the target to ensure the endianess is correct.

I don't know anything about litecoin but psj has been successfully used on several alt chains. The only real requirement is that the alt chain uses the same hashing algorithm as bitcoin, if so poolserverj won't know the difference and will happily do it's thing.

One this to watch with alt chains though is whether or not they've got the duplicate work bug. Have search back in this thread for an explanation of it...

been going at this damn thing for 6 hrs straight now. I remember why I've been putting it off for so long.

BTW I told Davinci that I wouldn't release this publicly for at least a week after he got it which I think is fair given the hefty bounty he's posted. However he generously declined the offer and requested I make it available to everyone immediately so if you do use it please consider making a donation to Davinci because I certainly wouldn't have gotten off my lazy arse to finish if he hadn't dangled the carrot in front of me.

This is just badass and props to both of you. I have merged mining going on my pool now. My only request now is it separate the winning shares between chains.