Hey i havent been paid out on the last three blocks?? Can u tell me whats going on???
Check the graphs, you mustn't have had valid shares in the chain to pay on those blocks. Two things need to happen for a payout: 1. You need to hash shares and have them successfully submit to the sharechain 2. You need those shares to stay valid until the next block, shares can fall off before the block is solved. I gain and loose shares all the time, that can be seen on the graphs that my payout goes up and down depending on the shares I have on the sharechain. |
|
|
|
nothing shows mate, the graphs etc .... but there wasn't any hashrate.
let me try again
I use my front end and have tested it on windows as well as on a separate server. I found some of the json code in the alternate fonts ends less than perfect. |
|
|
|
It is connected to a 1Gig E port on the office switch connected to a sonicwall firewall then a 100 Meg fiber connection, so i am kind of lost thats for sure. I am going to have to fine the ip and determine the latency to them. The latency to bitchain.info is only 7ms but i do know that has no baring on this issue,
Get rid of that Windows 7 crap and install a good Linux distribution  . Problem solved. There's nothing wrong with running it on windows. I run mine on windows and it runs well. lol... I was wondering how long it would take for someone to come on and defend Windows... man Norgz, I was just screwing around...  got me hook line and sinker  |
|
|
|
It is connected to a 1Gig E port on the office switch connected to a sonicwall firewall then a 100 Meg fiber connection, so i am kind of lost thats for sure. I am going to have to fine the ip and determine the latency to them. The latency to bitchain.info is only 7ms but i do know that has no baring on this issue,
Get rid of that Windows 7 crap and install a good Linux distribution . Problem solved. There's nothing wrong with running it on windows. I run mine on windows and it runs well. |
|
|
|
Norgz - Diff settings for a C1 - 1th Bitmain unit for ur p2pool?
What should they b to max it out?
Optimising Shares: If your running S1's set <share> to 0 ("0" defaults to lowest p2pool diff, currently 1677854.73) And <pseudo_share> to 220.4 (optimized for 190GH/s) <pseudo_share> is calculated as your hash rate in KH/s times 0.00000116 i.e. 190,000,000 * 0.00000116 = 220.4 Here is an example for an ant S1: Code: 19vXrwKGUhK4cCU8tA4kWZgbChcmh9a6qj/0+220.4 If you have a hash rate over 1TH/s you might consider upping your share diff to something higher then the p2pool minimum to reduce network traffic and increase the value of your shares For a C1 1000000000 * 0.00000116 = 1160 So something like btcaddress/0+1160 Or perhaps btcaddress/1+1160? You'll need to experiment. Considering the node only has two miners and they are a similar hash rate i doubt it will make a huge difference in the end. |
|
|
|
I created a chatbox for all p2pool users. Just like this forum does, in brining p2pool operators and power p2pool users together, a chatbox on each every p2pool node's home page can do the same for the entire p2pool community. At least, it is worth a shot. To see the chatbox you can go to us-east.p2pool.co or europe.p2pool.co and if you would like to add it to your own p2pool site you can do so by just adding this line: <iframe width=90% height=400px src="https://chatbox.com/#/p=6_qWgAgGqT29Eg==LS9g3ZbmtCThSWWnugDCrkHUQrs="></iframe>
Thanks, I've added it to my node's page. |
|
|
|
wow, node just hit 12th/s and took it fine. come back whoever that was lol
I had the same for an hour or two a while ago on my node....... Same hash rate? Maybe someone is doing p2pool testing. |
|
|
|
|
wow, node just hit 12th/s and took it fine. come back whoever that was lol
|
|
|
|
|
Edit: never mind that's an old payment. Must be an old text notification or something....
|
|
|
|
Ok I am wondering how does one determine what miner or if there pool found the block. I have not figured that out yet. 2 ways... First is to look at your logs and you'll see the message that the block was found. 2014-04-26 04:18:51.302213 GOT BLOCK FROM MINER! Passing to bitcoind!
Second is to look at your payout. If you found the block you get a 0.125 BTC reward for it. Is the reward to the miner or the nodes address? It's the miner right? |
|
|
|
Ok I am wondering how does one determine what miner or if there pool found the block. I have not figured that out yet. it's on the node logs. something like Block found passing to network. |
|
|
|
Yes and your rejects and stale may actually go up, but you want that since you've already mined those shares anyway and they might solve a block.
Thanks will give it a go. (FYI I was looking at Kano's binaries not Cons lol) |
|
|
|
Might be worth while asking ckolivas if the S3 binary he done to fix the stale shares filtering can also be used in the C1? I don't have a C1, but it might be compatible......
If S3 binaries run on the C1, my binary is compatible. Are the S3 binaries still needed with the latest firmware? I'm getting ~4% rejected and ~1.5% stale on my S3's with p2pool EDIT: is there an S3 binary from Kano?? |
|
|
|
Some new changes on the node: Bitcoind tweaks for even lower getblock latency. Updated p2pool from Github Now listed on http://nodes.p2pool.co/ with a 96% score! |
|
|
|
geez the share diff is down. pointing some miners back here for a bit. |
|
|
|
How can I test whether running the relay client is actually benefiting me? In 24 hours since starting it I have 4 shares in p2pool, 2 of which are orphaned, this is high compared to my previous 20 days. I'm running bitcoind, p2pool, and relaynetworkclient all on the same system.
it's just a matter of testing over time. It can't make things worse  |
|
|
|
sweet, can we have a new exe compiled please?
Dont need it, just a server-side bug. ah! cool, thanks mate. |
|
|
|
Sigh,
seems like another relay ddos.
Lots of txns over a short period of time followed by
"Closing relay socket, got freely relayed transaction too large (0: )"
Happening repeatedly.
This is not a dos, this is a bug. Specifically, this one. (Fixed now). Oh nice Bugs are better (IMO) than a ddos, coz there's a definite fix for it Updated. Thanks. sweet, can we have a new exe compiled please? |
|
|
|
Gotcha. So he made the changes on git I presume - can you ask him to post a link to it? Thanks No. I don't believe any changes were made or are planned to be made on git. It is a separate payout system developed for NastyPool that is written in a different computer language (C vs Python). Are there plans to open source that code and allow others to use it on their nodes? I find it interesting that all of the communications I've received so far are asking if there are plans to give this development away, but nobody has even tried mining on our node with it yet.  Give it time People are wary of closed source mining software, and rightly so. Personally, I won't touch anything that's not open source, which was one of the reasons I chose p2pool in the first place. I'm not for one moment suggesting that your software isn't kosher, & I congratulate you on your efforts - I just prefer to see what code I'm using, as do most others I'm sure you'll get some testers soon, and look forward to seeing the results I'm happy to test it on my node and my main point of asking that was are you willing to share your efforts to benefit everyone. I looked at your pool way back but couldn't see how i could use it since all memberships were filled and you had to be a member to mine on it apparently. Nasty always to me seemed a boys club that only the privileged are given access to so I gave up on it. |
|
|
|
|
Show Posts
