Anyone know why current p2pool wouldn't download the share chain? I decided to fire up p2pool to test some antminer code - but grabbed current p2pool git - and it says everything connecting ok on startup but drops any remote connections before downloading any shares for the share chain. Current git is of course a6f3f9259a5ea4975e961946b7ad7fe941ac76be e.g. 2015-09-13 21:21:44.519528 Outgoing connection to peer 72.14.191.28:9333 established. p2pool version: 1400 '14.0-9-g4e5afe9'
2015-09-13 21:21:45.731987 Outgoing connection to peer 62.213.58.41:9333 established. p2pool version: 1400 '14.0'
2015-09-13 21:21:45.846680 Lost peer 62.213.58.41:9333 - Connection to the other side was lost in a non-clean fashion.
2015-09-13 21:21:59.520494 Lost peer 72.14.191.28:9333 - Connection was aborted locally, using.
Permanently staying at 0 shares in chain I've used the same startup settings I used back in July (and I've used p2pool for testing on and off since back in Feb-2013) Just now it won't work any more. Hiya kano, I think the current spamming is playing havoc atm. Have you tried binding to a running node using the "--p2pool-node" option in the startup syntax? Once it's connected you should be fine, it's just the initial chain download that seems to be a problem. |
|
|
|
I can confirm that I'm working on upgrading I0coin to the latest Bitcoin upstream code. I've not yet created the Github repository for that, but my username there is domob1812, so it will probably be https://github.com/domob1812/i0coin. Looking good domob - great work  Will this be a straight forward wallet update or will we be forking?........  |
|
|
|
Just a heads up for anyone merge mining, many coins are upgrading to the latest core versions, resulting in some of them being incompatible with p2pool, namely NMC, HUC & CRW so far that I'm aware of, but there may be more, details here: https://github.com/p2pool/p2pool/issues/270#issuecomment-138758888Forrestv has addressed the issue, but I've not had time to test it due to work commitments, so if anyone merge mining could update to the latest p2pool version & give him feedback it would be appreciated. Fair play to forrestv for being on the ball Update on this, merge mining is working again with the latest p2pool version & the altcoin "core" versions. Anyone who is using the latest core versions of altcoins for merge mining should update to the latest p2pool version in order for merge mining to work again. Thanks again forrestv |
|
|
|
Well... The miners would have done better than on any other PPS pool, but not better than any pool. I showed that p2pool did better than BAN during the timeframe when things were all working as expected. Anyway, time marches on and hopefully people learn from their mistakes FWIW, most of the hardcore attacks coming from that single guy were in the name of P2Pool. Not saying you're in that boat too, but one guy with a giant P2Pool stick up his ass caused most of the undue drama around this pool. Blaming other pools for your own failings does not reflect well on you, especially after reading through your comments on your scam thread: https://bitcointalk.org/index.php?topic=782765.0Bitaffnet why does not reset the password?
Because the pool is abandoned. |
|
|
|
Glad to be involved I like the demurrage concept, this together with merge mining on a truly decentralized p2pool network provides the stability & security needed for this coin to grow. Good work |
|
|
|
On another note, is the latest huntercore daemon safe to use for mining yet?
If you mean my work on implementing Huntercoin on top of Bitcoin 0.11.99, then no, you should not use it for mining. I did not yet spend any effort at all in adapting the mining code, so you a) won't be able to choose the algo and b) won't even correctly collect miner fees from the game and such (if it works at all). Thanks for the clarification domob |
|
|
|
I've never touched scrypt I'm afraid, so am unable to help. Maybe if you asked in the relevant altcoin thread? Just a heads up for anyone merge mining, many coins are upgrading to the latest core versions, resulting in some of them being incompatible with p2pool, namely NMC, HUC & CRW so far that I'm aware of, but there may be more, details here: https://github.com/p2pool/p2pool/issues/270#issuecomment-138758888Forrestv has addressed the issue, but I've not had time to test it due to work commitments, so if anyone merge mining could update to the latest p2pool version & give him feedback it would be appreciated. Fair play to forrestv for being on the ball Oh, we just got a block!!  |
|
|
|
Pretty sure merge mining HUC with p2pool no longer works - I've not found any blocks for a couple of months now with over 10Th, so have removed HUC from my nodes. Same thing with NMC actually - I'm wondering if it's the same problem, especially now that CRW merge mining isn't working either, as I know they were all coded by domob. @ domob: Any chance you could have a look? Thanks not sure but hopefully domob can have a look. As you seem pretty experienced i guess you understand that when merge mining, the merged mine coin is not sharing hash with p2pool miners, only sharing (like a pool) with the primary coin (bitcoin). So you are going up against DiscusFish (f2pool) basically solo mining. (afaik) Hi snailbrain, Yeah, I realize that I'm basically solo mining when merge mining. However, I've been getting errors on p2pool startup with HUC & NMC for some time now, but never took much notice until recently when I realized I'd not found any HUC or NMC blocks for months, & now CRW is giving me a similar error on startup I think I might have found a common problem between them all, especially as all three were coded by domob. I've just finished doing some startup tests on my node & have collected the error logs of all three coins for domob to have a look at - it does seem to be a similar error with all three - so I'll PM him my results now. Cheers Following up on this, it turns out I was right about merge mining this & other coins not working with p2pool. Domob kindly contacted me with an explanation & a suggested resolution to pass on to the p2pool dev for implementation - which he has now done & I am testing now. On another note, is the latest huntercore daemon safe to use for mining yet? Thanks |
|
|
|
Still itīs strange. The 64 version works well.
Not on my system it doesn't. I use many 64bit wallets & this is the only one that doesn't work. |
|
|
|
Voted. Good to see some movement happening with this coin The block explorer link isn't working though....... |
|
|
|
postpone POS
this is a quark algo, corrrect?
51% attack issue is LOW risk in this case
if a hybrid flavor comes along and actually WORKS ... sorry all are very buggy unless you have PP sized capital.
then okay explore a POW/POSv fork
algo is good as is
focus on network and wallet improvements
not a path to fork
--------
the main challenge is getting o2o supporters/users in the 020 area
+1 There are already many POS alts out there going nowhere, there's absolutely no reason to change this coin. Growth is slow but steady, as any stable coin should be. I chose this coin because it's POW, if it changes I will find an alternative. |
|
|
|
UPDATE: I uninstalled the 64bit Win-QT wallet & decided to try the 32bit version instead - SUCCESS!. So the problem is with the 64bit QT wallet only. I suggest the OP remove the link to the 64bit wallet download until someone (anyone?) has fixed & fully tested the wallet so as to save any potential Crowncoin users days of aggravation & frustration trying to get the 64bit wallet to work like I have  THE 64BIT WINDOZE-QT WALLET DOES NOT WORK - USE THE 32BIT VERSION INSTEAD! |
|
|
|
I would like to get 10 million coins just because i plan to be a long term supporter of this.
You sir have been paid and as I just saw your reply PM I'm excited to see it finished :-) ***NEWS FLASH*** 020Londoncoin injects 10 million into the Greek economy......  |
|
|
|
Here's a small section of my debug log: ERROR: ProcessBlock() : CheckBlock FAILED
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckBlock() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckBlock() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckBlock() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckBlock() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckBlock() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckBlock() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckBlock() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
ERROR: CheckProofOfWork() : hash doesn't match nBits I get the same errors with both the pre-built binary & the installer of the 64bit Windoze QT version. I have tried -reindex & -upgradewallet as well as downloading the blockchain from scratch using connect=stratum.infernopool.com in my conf file as suggested by infernoman multiple times - all resulting in the same errors. Previous wallet worked perfectly. Any crowncoin dev out there can have a look?  |
|
|
|
|
Sorry for the late reply, I got called out.
OK, I've tried everything suggested but the Win 64bit QT wallet refuses to sync & is unusable until it does. This is the only wallet out of 15 others that does not work, but the previous version was fine. I fear I will no longer be able to use this coin until a working solution is found.
If anyone else can't get the win 64bit wallet to run, please post here.
|
|
|
|
On a positive note, the pool is up to 291 miners..
30 day luck of 127% didn't hurt, I bet.
Yup, let's hope that luck continues |
|
|
|
One of the nodes was not working - it should by ok now.
Mining interest is slowly increasing!
In Crown we trust!
Still no sync It's not a node problem, I got plenty of connections - it's a wallet issue, but only with the QT version, the daemon runs fine..... |
|
|
|
|
Show Posts
