I just hit my biggest share to date I think: 169,159,254  |
|
|
|
Shellshock, Aftershock & P2PoolIf you have not heard, a new vulnerability called Shellshock — also called the "Bash Bug" — is affecting both Linux computers and Macs, and it has the potential to let attackers take control of your computer or server. Many P2Pool nodes run on Linux and Mac, to test your node open up a shell and run: env x='() { :;}; echo vulnerable' bash -c "echo this is a test"If you see: vulnerable
this is a test You are vulnerable and should update bash immediately. Linux users should run: sudo apt-get update
sudo apt-get install bash One advantage of running windows servers 😉 Apple has promised a security fix for Mac users soon. |
|
|
|
I'd love to understand what exactly went on and what everyone was thinking. Maybe my experience was one that they were trying to boost their image by swapping out equipment that was useless anyway and they had plenty of just sitting around.
Guess we'll never know but if enough evidence has been gathered to shut them down, I'm not going to argue.
We know. They were scamming people. Read the FTC documents and read all the posts made in these forums from customers who have complained since day one. BFL is rightly shut down because they were scamming people out of MILLIONS of dollars. haha yeah but I mean what were individuals thinking etc. they were pretty successful at it for quite a while, they even still got people to buy into pre-orders after several failed delivery dates and all kinds of backlash. how much of this is the scammers fault and how much is the "gamblers" fault.  either way good to see due process has served and they have been duly shut down to save anyone else from getting scammed. Luckily I never actually purchased anything from them |
|
|
|
|
I'd love to understand what exactly went on and what everyone was thinking. Maybe my experience was one that they were trying to boost their image by swapping out equipment that was useless anyway and they had plenty of just sitting around.
Guess we'll never know but if enough evidence has been gathered to shut them down, I'm not going to argue.
|
|
|
|
Very interesting. I may point some has at this soon as I am currently back in "testing the waters mode". p2pool has been good to me and I've roi'd on 2 s1's but starting to see non-paying blocks. I'll be over shortly, have a beer waiting for me Well if I can update the S1/S2/S3 driver in a few days hopefully more of the S's will join too  I've got 2 s1's, do they require a driver update for ckpool? I have the p2pool driver update installed on them already. No driver update needed. It will work already as is. What I'm referring to is updating all 3 S1/S2/S3 drivers to the latest cgminer with my modified version of the driver that does everything 'properly' i.e. stratum rolling to reduce work generation CPU to ~15%, standard API, submitting stale nonces so p2pool blocks aren't discarded, etc. Ah I see, well if you need testers i'll be happy to do some experimenting. |
|
|
|
I'm out; I can no longer justify running my hardware for obvious reasons. But it's been a fun run, and I don't regret taking the chance. I'm still in it for the long haul, and can't wait to see what the future holds for Bitcoin. So I just wanted to leave a note of thanks to you eleuthria. I don't know how long you can keep this pool going as the mining becomes more & more centralized, but I hope you find a way & wish you the best. Best Regards, bananalogjam The price is going back up....... never jump on a reaction |
|
|
|
I've downloaded the exe client and am running it with "D:\Temp\relay\relaynetworkclient.exe public.au.relay.mattcorallo.com 127.0.0.1 8333" but I just get the following:
Closing bitcoind socket, failed to connect() (10049: Unknown error)
Closing relay socket, failed to connect() (10049: Unknown error)
Closing bitcoind socket, failed to connect() (10049: Unknown error)
Closing relay socket, failed to connect() (10049: Unknown error)
Closing bitcoind socket, failed to connect() (10049: Unknown error)
Closing relay socket, failed to connect() (10049: Unknown error)
Closing bitcoind socket, failed to connect() (10049: Unknown error)
Closing relay socket, failed to connect() (10049: Unknown error)
Closing bitcoind socket, failed to connect() (10049: Unknown error)
Closing relay socket, failed to connect() (10049: Unknown error)
Closing bitcoind socket, failed to connect() (10049: Unknown error)
Closing relay socket, failed to connect() (10049: Unknown error)
Closing bitcoind socket, failed to connect() (10049: Unknown error)
What am I doing wrong?
I'm getting this too with the windows exe client on Win7. It eventually killed my TCP/IP stack, all programs were getting TCP/IP errors until I killed the relay client. Going back to the python version here. M It was a broken build, have you tried the latest? Also try disabling ipv6 |
|
|
|
Does anyone know if I change the COINBASE_NONCE_LENGTH (larger to make nonce2 larger) on a local p2pool whether shares will be rejected by the p2pool network? I'm trying to make it more suitable to using a ckproxy front end.
This is proving extraordinarily difficult to test with my piddly hashrate (yes I know it's unbelievable but I'm only a very small miner). Could someone be so kind as to point their hashes at a public node I've placed at stratum+tcp://p2pool.ckpool.org:9332 please? It's a zero fee node so you can mine to your address as per any other node. I only need someone to mine until they get one valid real share and then they can move away. The worst thing that can happen is the share is not accepted so you will not get the reward for it. The testing is all to potentially find a meaningful interface between ckpool and p2pool which should hopefully benefit miners and p2pool in the future. Thanks. I've just pointed one of my s1's at it. let me know when you've seen enough shares. |
|
|
|
Very interesting. I may point some has at this soon as I am currently back in "testing the waters mode". p2pool has been good to me and I've roi'd on 2 s1's but starting to see non-paying blocks. I'll be over shortly, have a beer waiting for me Well if I can update the S1/S2/S3 driver in a few days hopefully more of the S's will join too I've got 2 s1's, do they require a driver update for ckpool? I have the p2pool driver update installed on them already. |
|
|
|
Well full respect to you Con. What do you think of Bitmains comments on p2pool, what do we expect to see from them? I wish I had the spare cash (and power prices) to go buy a few chunky miners but it's just a hobby for me. Your pool is private atm correct? some of the work you are doing looks great, does it help smaller miners?
Bitmain's contribution to p2pool will not help regular miners. They see that being proponents of p2pool will raise their status in the eyes of potential customers. However it appears they simply want to run their own solo mining operation using their own p2pool instance which is really of no relevance to miners. Even if they dump their hashrate directly into regular p2pool, it just increases share difficulty even further, making it even harder for regular miners. The only way they may be contributing is by adding code/improvements to the p2pool network, but in my experience every hardware manufacturer directs the absolute minimum amount of effort towards software/drivers as possible to just expedite delivery of their hardware. Offtopic about ckpool: There are public pools using the ckpool code - regular, solo and testnet. Just check the announce thread for the listed pools. Thanks for the insight. p2pool has some interesting benefits but also some equally interesting draw backs as the total pool rate increases. a double edged sword as we yearn for more block and high hash rate we almost push ourselves out. will be watching closely. Yeah found a certain pool running ckpool |
|
|
|
Very interesting. I may point some has at this soon as I am currently back in "testing the waters mode". p2pool has been good to me and I've roi'd on 2 s1's but starting to see non-paying blocks. I'll be over shortly, have a beer waiting for me |
|
|
|
Hmm... now if only there was a way to combine a properly written pool implementation that is written in a language that understands performance and multihreading, with a concept that peers together a number of nodes to form a de-centralized network of stand-alone miners large and small.... now that would be something......
Any scalability issues with the python client are not as important as the marginalising problem so that's not really going to help. You can see the problems I described a long time ago as users are now discovering on this thread. That's why I left p2pool. I was squeezed out. The one share I got rolled off within 36 hours before a block was found (it was one of those long streaks).
I am starting to see what you mean. even 400gh/s is now considered small?! I'm hanging in there but really starting to loose patience with lack of block payouts. What to do?! Ironically the only current solution I can see is... putting regular pools in front of the distributed pool which of course adds centralisation detracting from the distributed nature, so it's hard to see how this is actually better than just using a full regular pool. I've yet to come up with a better solution to the problem, but that doesn't mean I've given up on looking for solutions entirely. Well full respect to you Con. What do you think of Bitmains comments on p2pool, what do we expect to see from them? I wish I had the spare cash (and power prices) to go buy a few chunky miners but it's just a hobby for me. Your pool is private atm correct? some of the work you are doing looks great, does it help smaller miners? |
|
|
|
Maybe you can try a miner, let it find one share then stop it. I can guarantee its not valid not much more than 24 hours!!! Or if thats too difficult see with your eyes - http://p2pool.servebeer.com:9332/static/sharetime.jpg the last share in graps wasnt valid for a single block.... That's why I left p2pool. I was squeezed out. The one share I got rolled off within 36 hours before a block was found (it was one of those long streaks). M I am starting to see what you mean. even 400gh/s is now considered small?! I'm hanging in there but really starting to loose patience with lack of block payouts. What to do?! |
|
|
|
I was wondering if someone can tell me how to look at the 'real time load' graph.
I mean, what are those numbers telling me; what is the unit for those numbers ?
thanks in advance,
TurboDuck
those are the router stats. the S1 uses a tplink router module and openwrt software, similar to Linux. the load values you see are the system load values from the Linux kernel. http://luv.asn.au/overheads/NJG_LUV_2002/luvSlides.html |
|
|
|
what port does relaynetwork use?
8335 or 8336?
8336 Matt, looks like you have an issue with the SG node.
Strange, can you double-check now...there was a bug due to bitcoind banning relay servers... looks fine now, thanks. |
|
|
|
|
Matt, looks like you have an issue with the SG node.
|
|
|
|
What kind of power usage are you seeing at 406.25MHz? That's amazing how your miner is stable there - none of mine seem to be stable even at 375MHz.  I've got one that can run at 406 but the power draw is around 420w. I run it at 400 and another at 393 and together they use just over 750w. |
|
|
|
I'm having some questions about P2Pool mining, I'm mining on http://elizium.name node with 2 Antminer S3+'s, at about 920GH/s. But I've been mining for 12+ hours now, and I still have nothing. I added after my payout address "+518" but still nothing. Is this normal or...? Because P2pool is PPLNS so it takes around 3 days to build up enough shares to start seeing payment. conversely when you stop mining you'll still receive payments for a few days. have a little patience, it'll come and when it does it'll be sweet. p2pool has been finding quite a few blocks lately. |
|
|
|
It is done correctly if ure using git on windows.
Ahh ok, I only just changed over to using the python version from git. I did see that but have yet to test thanks for confirming! |
|
|
|
|
Show Posts
