Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 501. (Read 2592017 times)
No you aren't stealing. I run 22ghs at diff 1. You get paid instantly when a block is found. Sometimes none in a week, sometimes 3 a day. You get virgin coins.
Well, that sounds ok 
but am i not stealing shares from slower miners with my miner because my difficulty is still 1?
And when do they pay out? I mean, it is weekly, monthly or wen you have reached a certain goal like 1BTC? As i said, i am a noob in p2pool mining and all i want is doing the right way to give everyone the best outcome. But like it seems now it pays better then Slush's pool or is there some kind of sneaky thing behind this story?
Sorry for all my questions
but am i not stealing shares from slower miners with my miner because my difficulty is still 1? And when do they pay out? I mean, it is weekly, monthly or wen you have reached a certain goal like 1BTC? As i said, i am a noob in p2pool mining and all i want is doing the right way to give everyone the best outcome. But like it seems now it pays better then Slush's pool or is there some kind of sneaky thing behind this story?
Sorry for all my questions
Most people run their own but using a public one like you are is also a good idea. That way you don't have to set it up or run Bitcoin.
Uhm, sorry for the noobies question i give here, but i guess i need something sorted out about P2pool. First of all, i always used Slush's pool, so i used cgminer and the same string everyone is using and mined away. Yesterday i read about p2pool and went to the website p2pool.org and all i saw on the mainsite was
So i did that and it worked for some time. In the meantime i read more about it and the wiki says that i have to run the Bitcoin client and have to connect to my own localhost with the p2pool client. BUt the site clearly stated that i can run it as stated in the above quote.
I am using OS X with a compiled cgminer and all i did was using the string
Am i doing it wrong or am i working the good way?
Quote
Mining for Bitcoins on P2Pool.org is quick and easy. Simply point your miner to the provided URL and use your Bitcoin address as the username and payments will be sent there automatically. Use settings below to start mining BTC!
Pool URL: http://p2pool.org:9332
Username: Bitcoin Address
Password: Anything
Pool URL: http://p2pool.org:9332
Username: Bitcoin Address
Password: Anything
So i did that and it worked for some time. In the meantime i read more about it and the wiki says that i have to run the Bitcoin client and have to connect to my own localhost with the p2pool client. BUt the site clearly stated that i can run it as stated in the above quote.
I am using OS X with a compiled cgminer and all i did was using the string
Quote
cgminer -o http://p2pool.org:9332 -u {my wallet string} -p {choosen password}
Am i doing it wrong or am i working the good way?
There is a patch needed, I think, to mine on new p2pool network for correct chain. See this post:
https://bitcointalksearch.org/topic/m.2816945
He's running a node with new client and correct chain. A TRC-friendly asic just joined one of the other pools to help get some of these high difficulty blocks off our back.
https://bitcointalksearch.org/topic/m.2816945
He's running a node with new client and correct chain. A TRC-friendly asic just joined one of the other pools to help get some of these high difficulty blocks off our back.
Hello everybody.
I recently updated my p2pool installation to 13.2 and my TRC client/wallet to the last available 0.1.3-44 and this started a multitude of problems and malfunctions.
- My p2pool shortcut command is: (...program path) --net terracoin -a myTRCpublicaddress
- My TRC client/wallet shorcut command is: (program path) -datadir=Y:\Terracoin (I use another data dir than the default)
- In my default TRC datadir path and in Y:\Terracoin directory I have a notecard called "terracoin.conf" with this text:
server=1
rpcuser=(myusername)
rpcpassword=(mypassword)
rpcallowip=127.0.0.1
Something wrong is happening after do these updates, there are no shares, no orphan, no dead..., no payments, a lot of block-stales detected and everything has stopped working normally. I deleted and rebuild the TRC client and p2pool share blocks but still the same issue. I use CGminer 2.11.4 for mining and the program connects and shows good the accepted shares as always but it's like not connected.
I never had problems with p2pool and TRC, What can I do?
I recently updated my p2pool installation to 13.2 and my TRC client/wallet to the last available 0.1.3-44 and this started a multitude of problems and malfunctions.
- My p2pool shortcut command is: (...program path) --net terracoin -a myTRCpublicaddress
- My TRC client/wallet shorcut command is: (program path) -datadir=Y:\Terracoin (I use another data dir than the default)
- In my default TRC datadir path and in Y:\Terracoin directory I have a notecard called "terracoin.conf" with this text:
server=1
rpcuser=(myusername)
rpcpassword=(mypassword)
rpcallowip=127.0.0.1
Something wrong is happening after do these updates, there are no shares, no orphan, no dead..., no payments, a lot of block-stales detected and everything has stopped working normally. I deleted and rebuild the TRC client and p2pool share blocks but still the same issue. I use CGminer 2.11.4 for mining and the program connects and shows good the accepted shares as always but it's like not connected.
I never had problems with p2pool and TRC, What can I do?
MINX you are on right chain if you are on -44. The problem is high difficulty blocks as chain heals from the mandatory upgrade and the prior attack. p2pool as a whole is on the wrong chain, that's a lot of hash power going to waste.
what i'm doing wrong? and how can I avoid those forked nodes?
Right now you can't avoid them if you are using p2pool.Use a different TRC pool
or do solo mining (if you are a fast miner).
The correct chain has 175038 blocks now.
Idk I don't use trc.
Your p2pool could be connected to forked nodes?
I don't know how this connected to forked nodes, i'm using the default configuration... what i'm doing wrong? and how can I avoid those forked nodes?
Thanks
Your p2pool could be connected to forked nodes?
Hello everybody.
I recently updated my p2pool installation to 13.2 and my TRC client/wallet to the last available 0.1.3-44 and this started a multitude of problems and malfunctions.
- My p2pool shortcut command is: (...program path) --net terracoin -a myTRCpublicaddress
- My TRC client/wallet shorcut command is: (program path) -datadir=Y:\Terracoin (I use another data dir than the default)
- In my default TRC datadir path and in Y:\Terracoin directory I have a notecard called "terracoin.conf" with this text:
server=1
rpcuser=(myusername)
rpcpassword=(mypassword)
rpcallowip=127.0.0.1
Something wrong is happening after do these updates, there are no shares, no orphan, no dead..., no payments, a lot of block-stales detected and everything has stopped working normally. I deleted and rebuild the TRC client and p2pool share blocks but still the same issue. I use CGminer 2.11.4 for mining and the program connects and shows good the accepted shares as always but it's like not connected.
I never had problems with p2pool and TRC, What can I do?
I recently updated my p2pool installation to 13.2 and my TRC client/wallet to the last available 0.1.3-44 and this started a multitude of problems and malfunctions.
- My p2pool shortcut command is: (...program path) --net terracoin -a myTRCpublicaddress
- My TRC client/wallet shorcut command is: (program path) -datadir=Y:\Terracoin (I use another data dir than the default)
- In my default TRC datadir path and in Y:\Terracoin directory I have a notecard called "terracoin.conf" with this text:
server=1
rpcuser=(myusername)
rpcpassword=(mypassword)
rpcallowip=127.0.0.1
Something wrong is happening after do these updates, there are no shares, no orphan, no dead..., no payments, a lot of block-stales detected and everything has stopped working normally. I deleted and rebuild the TRC client and p2pool share blocks but still the same issue. I use CGminer 2.11.4 for mining and the program connects and shows good the accepted shares as always but it's like not connected.
I never had problems with p2pool and TRC, What can I do?
Hi there. Please review:
http://sourceforge.net/mailarchive/message.php?msg_id=31222636
The p2pool web site is showing about 200 incompatible blocks "ahead" of the official chain. The new version of TRC was mandatory as of block 175,000.
http://sourceforge.net/mailarchive/message.php?msg_id=31222636
Quote
Important info : some p2pool users aren't running the latest client build, if you're running p2pool, please download last TRC client and/or update your client source code prior to new compilation
The p2pool web site is showing about 200 incompatible blocks "ahead" of the official chain. The new version of TRC was mandatory as of block 175,000.
I just reset one of my p2pool nodes (to add more outgoing connections).... did the whole loading share business & got that finished before cancelling out the first process, so it was down for maybe 10 seconds, the part where it's out of sync until the next 'new work' broadcast..
Anyway, it looks like someone got out of sync, where they're getting like 60% DOA now. I tried to reset it again but that didn't do anything. Is there any way to "fix" that? The only thing I can think of is taking the pool offline for a minute or two & hope the person has a backup pool set?
Local rate: 8.93GH/s (50% DOA) Expected time to share: 1.44 hours
(normally it's 0-5% DOA)
Anyway, it looks like someone got out of sync, where they're getting like 60% DOA now. I tried to reset it again but that didn't do anything. Is there any way to "fix" that? The only thing I can think of is taking the pool offline for a minute or two & hope the person has a backup pool set?
Local rate: 8.93GH/s (50% DOA) Expected time to share: 1.44 hours
(normally it's 0-5% DOA)
What is the latest p2pool version today? 13.2-2-gebae741 ??
The latest is commit 07162a3f7d, ebae741e9e is almost a week old. https://github.com/forrestv/p2pool/commits/master 
What is the latest p2pool version today? 13.2-2-gebae741 ??
There could be corrupt nodes that ignore your address though.
It can be easily verified if you connect with stratum.
By the way, you should monitor it constantly if you mine on a public node, especially if it charges fee. Technically, a node takes fee by randomly giving work for its own address. On average, a miner gets %fee% node-address works in 100 requests. And those "randomly" and "on average" mean that 1 request is not enough to determine whether a node actually charges the same fee that it states.
Hence also a way for mining without fee on any node. If a miner modifies his mining software code, he can mine only to his own address. Whenever the node gives work for its own address, the miner can just discard it and make another request immediately.
With the new ASIC-compatible version of p2pool, is it still recommended to turn off queuing in cgminer?
Any input on this? I'm trying p2pool with my Jalapeño and I'm curious if this still makes a difference.ckolivas, is that true for jalepeno's - or p2pool in general?
Thank you twmz and baloo_kiev, that explains it. It basically works the same as Eligius, then. Mine with your address to get paid, mine without to donate to the pool funds.
It basically works the same as Eligius, then. Mine with your address to get paid, mine without to donate to the pool funds. Thats wrong.
Without address is Donate to the NODE owner, Not the entire Pool .
Yes, sorry, that's what I meant. I'm confusing Node with Pool.
Thank you twmz and baloo_kiev, that explains it. It basically works the same as Eligius, then. Mine with your address to get paid, mine without to donate to the pool funds.
It basically works the same as Eligius, then. Mine with your address to get paid, mine without to donate to the pool funds. Thats wrong.
Without address is Donate to the NODE owner, Not the entire Pool .
With the new ASIC-compatible version of p2pool, is it still recommended to turn off queuing in cgminer?
Any input on this? I'm trying p2pool with my Jalapeño and I'm curious if this still makes a difference. Jump to: