Search results

On the plus side, I had no problem reconnecting the mining pool... so maybe that is something :) EDIT: Thanks for the IP, it looks like the blocks are loading now

Interesting... that seems to crash the wallet after startup... I'm going to try re-downloading it. EDIT: Nope, neither a new version of 9.4.11 nor 10.8.11 will work. It starts up and appears to crash once it connects to the network. Do we have a known good node that I can try forcing it to...

Also: darkcoin.kicks-ass.net if you want another p2pool. Is there a way to check which fork a pool is on?

Is there a way to force the windows wallet to reindex? I updated to the 10.8.11 client, but I'm stuck on 75125 as well...

darkcoin.kicks-ass.net is back up with the original p2pool on a reindexed 10.08.11 fork. Everything seems to be working correctly now.

OK, darkcoin.kicks-ass is now on the 08.11 fork!

It looks like I got one payout on mine as well... OK, I restarted with 10.08.11 and the masternode is reconnected, and seems to be working after -reindex. Actually, after reindex I have no transactions :( I must have been on the wrong side of the fork I have a spare computer now that I can run...

Alright! we are up and running now!

chaeplin, you have once again saved the day. thanks so much for your many contributions to DRK!

That sucks... I've seen some really high spikes today, like 1.3 G/Hs. I wonder if that is related

yes, unless there is some aspect of twisted (where the error seems to be occurring) that I missed. I'm doing this on a patchwork dev box, so I might have missed something. This is the python portion of my install script" #Install p2pool dependencies sudo apt-get -y install python-zope.interface...

Are you re-cloning the repository or just pulling changes (if this is even possible given that it was originally cloned from Github not Atlassian). For some reason, I'm getting this error when I clone into a clean directory. I know dstorm mentioned something about xcoin_hash, but I'm not sure...

Apologies to everyone... Darkcoin.kicks-ass.net will be late in updating. I had a family emergency late yesterday and I won't be able to update until I get back to the US on Monday night. I'm trying to write a replacement script to update on the 25th, but for some reason on my pull, p2pool...

So to update our current pool on May 25, should we do a pull from your repository? I'm not terribly familiar with the git mechanism... Also, will this need to be recompiled, or will the python modules drop in without too much fuss? BTW, dstorm you rock, dude. Thanks so much for fixing this!

darkcoin.kicks-ass.net updated masternode updated Now I just need to patch p2pool and I'll be good to go! Thanks Evan for all the hard work

I believe you do need one single input of 1000DRK, tho. If you want to test it, send 0.1 DRK to make sure it is receiving, and then send the big 1000DRK in one transaction.

I think what Evan is saying is that the masternodes themselves don't vote - the miners that actually find the blocks do. So a miner would have to get 6 consecutive votes (which means finding 6 blocks in a row) to control which masternode gets selected. The masternode balances are irrelevant as...

Here's mine if you need further info { "version" : 100802, "protocolversion" : 70015, "walletversion" : 60000, "balance" : 1002.10000042, "blocks" : 70592, "timeoffset" : -39, "connections" : 12, "proxy" : "", "difficulty" : 1549.86428363, "testnet" ...

That is indeed good news. Will we have a patch or a new pull from the repository... Or is it too soon to tell?

Let's hope the fix gets done before the 25, or there will be even less :(