Bump!
We need a higher hashrate on this pool. More miners welcome!
We need real p2pool network, not a set of single p2pool-based nodes, whose operators are so greedy that they cannot share 10 lines of code they have changed in open source software. |
|
|
|
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).
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 <pubkey>/<share_diff>+<pseudoshare_diff>, e.g. 021c25e5046f6be38270ffe94ed4d2d05f926e957af6c061aaea3577fceb5822ed/0.25+0.025
Increasing pseudoshare difficulty should decrease network/CPU load. |
|
|
|
|
So what's the news about shipping?
|
|
|
|
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.
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.
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 p2pool_difficulty * (your_hashrate / p2pool_hashrate) * (time_to_block / 30s) / 10
Details:https://bitcointalk.org/index.php?topic=18313.msg2060914#msg2060914 |
|
|
|
This being just first year level probability and statistics at Lomonosov. What they teaching else places? How to be making fancy Starbuck skinny-soy-skim-mocha latte with whiping creams?
- What do you usually say when you meet %university_name% graduate? - Big Mac menu please!  |
|
|
|
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. |
|
|
|
Ok, I'll try this out..
how long will you keep the pool up at 0%?
Is this your pool too? http://coinminer.net:9444Would 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. |
|
|
|
Coming Soon FPGA /ASIC miner included in USB .ADD-ON 6/1/2013 UPDATE
BITBAR FPGA/ASIC miner ADD-ON 6/1/2013 UPDATE
In the design process the contracted Techs were toying around with Adding an FPGA/ASIC chip to the BTB secured wallet so you could generate BitBars and secure BitBars on the same drive.
Currently All pre-orders after 6/1/2012 will include the miner for 2BTB .After shipping prices will go up
Hey, stop that! Please say that your site was hacked and this was posted by attackers whatever and remove it before it was noticed by the comunity. This isn't even funny. |
|
|
|
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! |
|
|
|
I've got the p2pool running in windows, how do I get the public key?
Just in the same way. If you run graphical interface of bitbar, you can type 'getnewpubkey' in console (I guess it's Help->Debug window->Console). Also, you don't need to specify a public key if you run your own p2pool node. It will automatically request a pubkey from your bitbard and generate payouts to it. You only need to specify your pubkey if you connect your workers to a node run by someone else! OK, cheers. So how long until payouts start from my own p2pool node? Go to http://localhost:<your_worker_port>/static to see full stats. You will see 'Payout if a block were found NOW' line, which shows exactly what it states: you will receive this amount in the next found block generation transaction. Also, you can see how it changes with time on the graphs page (under 'Payout to default address'). Note that Bitbar has 520-block maturity period, i.e. you will be able to spend the coins in about 3.5 days after the generation. Until then, they will be labeled 'immature'. P.S. The payout value is roughly proportional to number of your valid shares. |
|
|
|
|
Updated the code. Fixed worker payouts and graphs, added one more bootstrap node.
|
|
|
|
I've got the p2pool running in windows, how do I get the public key?
Just in the same way. If you run graphical interface of bitbar, you can type 'getnewpubkey' in console (I guess it's Help->Debug window->Console). Also, you don't need to specify a public key if you run your own p2pool node. It will automatically request a pubkey from your bitbard and generate payouts to it. You only need to specify your pubkey if you connect your workers to a node run by someone else! |
|
|
|
How do I get this to work in Windows?
Try to follow instructuion in README file ( https://github.com/baloo-kiev/p2pool). The code is forked from NVC p2pool with minor changes. This is all I can say, as I never tried to install and run it on Windows. If I had to, I would probably run it on linux in VirtualBox, this may be the easiest way  |
|
|
|
|
Show Posts
