Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 147. (Read 2591920 times)

No, though I'm not sure where to get the address list from.
I believe p2pool.info isn't the source any more.
... and I was thinking that since I had 3 addresses all doing the same that may or may not help - i.e. some other problem may be the cause.
So what would be a reliable address in your opinion

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.

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.
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.

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 

um, looks like you've trimmed too much context man!
can you post more ...

I'm getting this message with bitcoin core.

EXCEPTION: MSt8ios_basefailureE
String length limit exceeded
C:\Program Files\Bitcoin\bitcoin-qt.exe in ProcessMessages0

Anyone know why?

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-138758888

Forrestv 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!!   

Trying to complie scrypt module on my win2008 r2 Server.
I insralled python2.7 and the newest mingw. While i Compiler the Module i got this Error

c:\mingw\bin\gcc.exe -shared -s build\temp.win-amd64-2.7\Release\scryptmodule.o build\temp.win-amd64-2.7\Release\scrypt.o build\temp.win-amd64-2.7\Release\ltc_scrypt.def -LC:\Python27-64\libs -LC:\Python27-64\PCbuild\amd64 -lpython27 -lmsvcr90 -o build\lib.win-amd64-2.7\ltc_scrypt.pyd
scryptmodule.c: In function 'scrypt_getpowhash':
scryptmodule.c:15:5: warning: implicit declaration of function 'scrypt_1024_1_1_256' [-Wimplicit-function-declaration]
build\temp.win-amd64-2.7\Release\scryptmodule.o:scryptmodule.c:(.text+0x1e): undefined reference to `__imp__PyArg_ParseTuple'
build\temp.win-amd64-2.7\Release\scryptmodule.o:scryptmodule.c:(.text+0x35): undefined reference to `__imp__PyMem_Malloc'
build\temp.win-amd64-2.7\Release\scryptmodule.o:scryptmodule.c:(.text+0x44): undefined reference to `__imp__PyString_AsString'
build\temp.win-amd64-2.7\Release\scryptmodule.o:scryptmodule.c:(.text+0x83): undefined reference to `__imp__Py_BuildValue'
build\temp.win-amd64-2.7\Release\scryptmodule.o:scryptmodule.c:(.text+0x8e): undefined reference to `__imp__PyMem_Free'
build\temp.win-amd64-2.7\Release\scryptmodule.o:scryptmodule.c:(.text+0xcd): undefined reference to `__imp__Py_InitModule4'
collect2.exe: error: ld returned 1 exit status
error: command 'gcc' failed with exit status 1

I tried it with Python 32 Bit and 64 Bit. But always the same Error.
A p2pool fort Terracoin and Bitcoin is working in this Server.

Who can help?
Tank you

73.182.147.206:9332/static
Inviting people to mine on my node. No Fee
Any input would be appreciated

If that doesnt work find me on.
http://nodes.p2pool.co/

opah!  4 blocks, with an 11,000% luck on the last one!

Oh my, 3 blocks in 24h. 


Oh and forrest,

The primary P2Pool repository has moved from https://github.com/forrestv/p2pool to https://github.com/p2pool/p2pool. GitHub redirects should ensure that everything continues to work, but efforts should be made to use the new URL instead of the old one.

Yup, let's hope that luck continues 

On a positive note, the pool is up to 291 miners..

30 day luck of 127% didn't hurt, I bet.

You were never accused of trolling, welcome to the straw man club.

Wow... Just wow.

The project is open sourced on Github. Forrestv was absent by his own admission for a long time due to personal priorities.  Like ANY open source project, we asked for developers to contribute and fork the code to a more maintained state. No one picked up the mantle.  As simple as that.

Believe what you want.  Doesnt matter.  forrestv is back and there have been numerous github commits and developer pull requests from others since then.

Not going to apologize for advocating what open source development and github branching and forking are all about.  

Others may have been more vehement about it, but im not going to stand here and be buried under retarded statements of imaginary slights.  Welcome to the ignore list. I see only one person trolling here now.

anyone who does know the post history also knows that it was NOT like that. You people had NO PLAN as to how you would replace the person that wrote this code, you simply shouted loudly for weeks and weeks about how no-one should give forrest money. Trying to squirm out of it now with diversions and fantasy reflect very badly on you.



Apologise for backing the (now heavily discredited) coyotes who tried to push forrest out of his own project. That would be entirely appropriate. But it seems you're too intransigent for that.



You're consistently referring to emotions and making repeated use of expressions like "pissed off". I supply morality, but not emotion. Don't get confused.

Well, please read my posts again, and forrestv's in relation to his long absence.  I did NOT intend to take personal attacks on forrestv at all and only held the position that others should take up the mantle if he was too busy with his personal life and school to work on p2pool.  I also was on the side of turning the donation fee into a bounty for those that would take up that mantle, if forrestv really couldn't work on this anymore.  I also backed the donations going to forrestv for solving some of our continuing issues coming from the Litecoin Dev camp (I believe you've seen me post in those threads as well, since I remember you posting there too).  But if you remember, those solutions did not come even though he put some time into it.  

I don't see how that is a personal attack on forrestv at all.  Besides it's a moot point since he's been back as you've said.
Either way I'm not the one taking things to a personal level here and I apologize if you think I've ever come across that way.  If anything I think you're unjustly conflating my positions on the subject with those who have a more, shall we say emotive presence on this thread.

I'm alright, you're not as offensive as you seem to think.

You were one of many who consistently, on many occasions, supported personal attacks on the developer of p2pool. In fairness, you've also been more accommodating since then. I have been reading this thread although I don't always post.

You were wrong to behave that way towards the developer. So apologise, as you've intimated. Being nice when he returned is not an apology (to adults, anyway)

Allow me to modify my statement, although you should know what I meant.

After this specific planned fork to XT on January 11th 2016, miners will not be able to fork the XT chain, because the checkpoints (hence the XT devs) decide the valid chain, not the miners.


You are correct about one thing; nothing will prevent miners who don't want XT from continuing using a different chain. But XT itself cannot be forked at the network level, that's what the checkpoints are for, they are intended as such.