Topic: [BTB][P2POOL][UPDATED] Source + 0% public node! Read instructions carefully! (Read 4629 times)
June 05, 2013, 02:37:13 PM
One thing great about P2Pools is that the block rewards are sent immediately to your wallet where they mature like solo mining. This lowers the risk because your bars are not sitting at a pool for the long confirmation process where they could have problems.
June 05, 2013, 12:00:20 PM
For anyone who is confused about how to setup up your public key in windows:
Start the Bitbar-qt wallet.
Go to the wallet console by clicking on Help > Debug Window > then click on the Console tab.
1)
In console, type:
Hit enter and this will return your new public key. The "someaccount" title can be any name. This title will be the label of the wallet address tied to your public key.
2)
Next type:
xxxx... should be the new public key that was created by the console after you did step one. This will return some data about your new public key including the wallet address that it is tied to.
3) Use your new public key as the worker username when connecting to a public node, just like you use your address with other coin p2pools.
Hope this helps.
Start the Bitbar-qt wallet.
Go to the wallet console by clicking on Help > Debug Window > then click on the Console tab.
1)
In console, type:
Code:
getnewpubkey "someaccount"
2)
Next type:
Code:
validatepubkey xxxx...
3) Use your new public key as the worker username when connecting to a public node, just like you use your address with other coin p2pools.
Hope this helps.
June 04, 2013, 11:46:44 AM
Is that 0.5% for all blocks in Bitbar or just the way you set it up on this pool?
It is set in original p2pool code (for BTC and all other coins). The rest 99.5% of block reward is distributed between miners proportionally to amount of work done.
June 04, 2013, 11:26:43 AM
Does it show who found the last block? Cgminer said rejected on the share that said BLOCK! on my console.
I guess (not sure though) that cgminer said rejected because the share was stale. This means that a new share was already found by someone else before you submitted yours. However, in p2pool, we need stale shares because a stale share can be a valid block if it satisfies block difficulty.
To find out who found a block, click on the arrow in the rightmost cell of the table on the stats page. Then look for 'payout address'. BTW, block solver receives 0.5% of its value in addition to his payout.
Ok thanks, I see it. I have found all the blocks on the table (last 24hrs) so it must have went through even though it said rejected on cgminer.
Is that 0.5% for all blocks in Bitbar or just the way you set it up on this pool?
June 04, 2013, 11:20:55 AM
Does it show who found the last block? Cgminer said rejected on the share that said BLOCK! on my console.
I guess (not sure though) that cgminer said rejected because the share was stale. This means that a new share was already found by someone else before you submitted yours. However, in p2pool, we need stale shares because a stale share can be a valid block if it satisfies block difficulty.
To find out who found a block, click on the arrow in the rightmost cell of the table on the stats page. Then look for 'payout address'. BTW, block solver receives 0.5% of its value in addition to his payout.
June 03, 2013, 07:53:54 PM
Thanks for your help,
I changed this on users 0387eaeedc4a2... and 02749f315187dc63e6... how will I know if it worked? The diff on cgminer appears to be same as before (~85).
I changed this on users 0387eaeedc4a2... and 02749f315187dc63e6... how will I know if it worked? The diff on cgminer appears to be same as before (~85).
According to my logs, your share difficulty is now 0.256, just like intended. Your cgminer shows the same difficulty because this is pseudoshare difficulty, which is lower that "real share" difficulty. Pseudoshares are sent to the node but aren't propagated to p2pool network and don't affect payout. They are only useful for monitoring purposes, so that you can see if your miner is working shortly after launch, calculate hashrate precisely and find out quickly if it stops hashing or connection to the node is broken. You can adjust pseudoshare difficulty by setting username to
Code:
021c25e5046f6be38270ffe94ed4d2d05f926e957af6c061aaea3577fceb5822ed/0.25+0.025
Thanks for the free lesson on P2P. I get slightly higher worker utility with the pseudoshare set higher.
Does it show who found the last block? Cgminer said rejected on the share that said BLOCK! on my console.
June 03, 2013, 02:08:00 PM
Thanks for your help,
I changed this on users 0387eaeedc4a2... and 02749f315187dc63e6... how will I know if it worked? The diff on cgminer appears to be same as before (~85).
I changed this on users 0387eaeedc4a2... and 02749f315187dc63e6... how will I know if it worked? The diff on cgminer appears to be same as before (~85).
According to my logs, your share difficulty is now 0.256, just like intended. Your cgminer shows the same difficulty because this is pseudoshare difficulty, which is lower that "real share" difficulty. Pseudoshares are sent to the node but aren't propagated to p2pool network and don't affect payout. They are only useful for monitoring purposes, so that you can see if your miner is working shortly after launch, calculate hashrate precisely and find out quickly if it stops hashing or connection to the node is broken. You can adjust pseudoshare difficulty by setting username to
Code:
021c25e5046f6be38270ffe94ed4d2d05f926e957af6c061aaea3577fceb5822ed/0.25+0.025
June 03, 2013, 01:45:28 PM
So if I had 2mh/s, I would set the diff to 0.256 by putting /0.256 at the end of my user name/key?
Yes.
Thanks for your help,
I changed this on users 0387eaeedc4a2... and 02749f315187dc63e6... how will I know if it worked? The diff on cgminer appears to be same as before (~85).
June 03, 2013, 12:13:30 PM
So if I had 2mh/s, I would set the diff to 0.256 by putting /0.256 at the end of my user name/key?
Yes.
June 03, 2013, 12:06:23 PM
So if I had 2mh/s, I would set the diff to 0.256 by putting /0.256 at the end of my user name/key?
June 03, 2013, 11:40:10 AM
Thanks.
Why does it adjust the difficulty and say "LONGPOLL from pool requested work restart" so often? Is that optimizing the hash rate? Should I set the difficulty with my username to reduce this?
Why does it adjust the difficulty and say "LONGPOLL from pool requested work restart" so often? Is that optimizing the hash rate? Should I set the difficulty with my username to reduce this?
This is normal p2pool behaviour. New work is set every time a share is found, which in our case is 30 seconds on average (10 seconds in BTC p2pool).
The short version is that the work to produce the "next" block depends on the previous block. The moment a new block is found, any in-progress searching is aborted because it won't produce anything useful. This is important because it encourages a "found" block to be used and distributed quickly.
It might very briefly decrease your mining hashrate because of the time required to fetch new work from the pool/start working on the new work. It should be noted that p2pool has 10-second blocks so you'll see this message about once every 10 seconds. That's why you can't use p2pool with devices that take a long time to start new work like BFL singles.
It might very briefly decrease your mining hashrate because of the time required to fetch new work from the pool/start working on the new work. It should be noted that p2pool has 10-second blocks so you'll see this message about once every 10 seconds. That's why you can't use p2pool with devices that take a long time to start new work like BFL singles.
Difficulty is adjusted every time a new share is found.
In any case, it is considered a good practice for miners with big hashrates to set their difficulty manually because it reduces p2pool's minimum share difficulty, helping small miners to achieve less variance. I would recommend tuning it in such way that your estimated time to share is several (5-10) times less than p2pool's time to block. So your difficulty can be calculated as
Code:
p2pool_difficulty * (your_hashrate / p2pool_hashrate) * (time_to_block / 30s) / 10
Details:https://bitcointalk.org/index.php?topic=18313.msg2060914#msg2060914
June 03, 2013, 10:48:50 AM
Thanks for setting up the P2P.
Why does it adjust the difficulty and say "LONGPOLL from pool requested work restart" so often? Is that optimizing the hash rate? Should I set the difficulty with my username to reduce this?
Why does it adjust the difficulty and say "LONGPOLL from pool requested work restart" so often? Is that optimizing the hash rate? Should I set the difficulty with my username to reduce this?
June 03, 2013, 07:14:40 AM
Strangely, coinminer.net has no p2p connections to other nodes at the moment 
EDIT: seems like connected again. To be stable, the p2pool network definitely needs a couple more nodes.
EDIT: seems like connected again. To be stable, the p2pool network definitely needs a couple more nodes.
June 03, 2013, 06:41:02 AM
Ok, I'll try this out..
how long will you keep the pool up at 0%?
how long will you keep the pool up at 0%?
Is this your pool too?
http://coinminer.net:9444
Would you prefer that we use that one instead?
Coinminer is not my pool. I just came across it here on the forums. It uses the code posted here.
Well, initially, I just wanted to mine BTB in p2pool, like I mine other coins. I opened my public node to test the code and show that it works to encourage others to host their own nodes. Obviously, higher p2pool hashrate reduces variance like in any centralized pool. At the same time, distribution of hashing power between many p2pool nodes keeps decentralized nature of cryptocoins. My node does not consume any significant amount of resources, so for now, I will keep it up and free, as long as it comes under "no guarantees, no hoster responsibility, no complaints" terms
. Feedback from both miners and node hosters is highly appreciated. If I am going to close the node or introduce fee, I will announce beforehand both here and on the stats page. June 03, 2013, 01:18:59 AM
Ok, I'll try this out..
how long will you keep the pool up at 0%?
how long will you keep the pool up at 0%?
Is this your pool too?
http://coinminer.net:9444
Would you prefer that we use that one instead?
June 01, 2013, 08:13:29 PM
Ok, I'll try this out..
how long will you keep the pool up at 0%?
how long will you keep the pool up at 0%?
June 01, 2013, 06:05:10 AM
My node is temporarily down because of network connection problems. Use http://coinminer.net:9444 . It charges 2% fee.
May 31, 2013, 10:11:50 PM
Hmm...my address (BSAL3Gm4ckPbygyoyf2X6ZHBUdtBa1BFrn) is showing as a payout of 0. Shouldn't it drop off the list? Or should the payout not be 0?
I searched but didn't figure out if this is normal p2pool behavior so in this case I don't know if I'm pointing you towards a problem or just showing my ignorance.
-Mo
I searched but didn't figure out if this is normal p2pool behavior so in this case I don't know if I'm pointing you towards a problem or just showing my ignorance.
-Mo
May 31, 2013, 04:38:13 PM
Woohoo, got my first little bit of BTB! Thanks, baloo_kiev, for all your hard work and help.
May 31, 2013, 10:32:58 AM
Updated the code. Fixed worker payouts and graphs, added one more bootstrap node.
This is a critical fix, please make sure you have the latest version!
Jump to: