Bitcoin Forum

./bitbard getnewpubkey "someccount"

./bitbard getaddressesbyaccount "someaccount"

./bitbard validatepubkey <your_new_pub_key>

UPDATE: One more fix to avoid rounding of the award to cents. Please re-download the code and clear data directory.

P2pool works!
Source: https://github.com/baloo-kiev/p2pool
All work submitted to a node by workers is payed to the node address! Address specified as worker's username is ignored!
Download the source, host your node, point your workers to it.

EDIT4. First block found! http://btb.cryptocoinexplorer.com/block/00000000055aa1afdb25984d4740e1e81f79c8f258cce029483a1c51c2b83fd6

EDIT3. Some changes reverted. All work submitted to a node by workers is payed to the node address! Address specified as worker's username is ignored! Download the source, host your node, point your workers to it.

EDIT2. Fixed. Get the code at https://github.com/baloo-kiev/p2pool or point workers here http://78.27.191.182:8333/, still 0% fee.
Launch with

EDIT. Don't point your miners to my node. It does not payout to worker addresses at the moment! P2p vonnections work ok, though.

Testing Bitbar p2pool, help appreciated!

Please drop a little hashrate to http://78.27.191.182:8333/ (essentially, fee is 0%)
or
modify p2pool as described here https://bitcointalk.org/index.php?topic=193669.msg2288975 and launch with '-n 78.27.191.182' to connect to my node.

(Both options assume you know how to mine with p2pool: set username, view stats, etc.)

Thank you!

Testing, with my paltry 1.7Kh or so from an old CPU.

One thing I noticed, the BTB address I'm mining with is listing in the local stats with a hash rate, but even after a few hours of hashing it hasn't shown up on either the users or the current payouts pages. I've heard P2Pool can be a bit slow to show such things, and my low hash rate probably doesn't help, but is this a problem or should I just leave it running and be patient?

Also, if I mine at such a low hash rate for a few hours but don't show up in the users or payouts, and then I shut down the machine, have I wasted all of the time I spent mining? I assume the payout stats indicate a payout for a block already found, so if I do show up in the payout stats and then stop mining in the pool, I'll eventually get a (small) payout...?

Good luck with the pool and the currency!

-Mo

Edit: Forgot to mention, BTB address is: BJH5ykFQisPAnwnAkeqgvisDbxnJs6owGt
Edit 2: Switched my meagre mining muscle to another pool for now. I'll be back if it'll help you test, I like P2Pools.

I see your address on the stats page. At this hashrate, your expected time to share is about 10 hours, so the variance will be huge.

Once you submit a share, you get payout with every block found by the p2pool for some time. Current payouts (if a block were found now) for every address are shown here http://78.27.191.182:8333/static/graphs.html?Day

Yeah, I figured hashing at such a low rate would make for delays in various ways, I just wanted to make sure it wasn't going to waste, otherwise I'll just solo mine and cross my fingers. ;)


So, my minerd telling me "accepted" isn't the same thing as having submitted a share? Because quite a few were accepted, which I'm sure is how P2Pool figured out my hashrate.

Is there a number it has to accept before I have a share?

Thanks!

-Mo

Edit: Mining for a few hours in the btb.ltcoin.net pool last night got me 4 shares and an eventual payout of around 0.00005. Useless since that pool pays out at 0.02, but it showed me that my minerd is working, at least. So what has me worried is that my address didn't show up in the P2Pool "Payouts if a block were found NOW:" table, even though I mined for longer last night under P2Pool than ltcoin.net and had "accepted" figures in the double digits. I'm back to P2Pool and I'll let it run for the day and see what happens.

Never mind, I wasn't abstracting far enough. I was thinking blocks:pseudoshares, not blocks:shares:pseudoshares. So minerd won't know, but what's the difficulty difference between pseudoshares and shares so I can estimate?

I guess the difficulty difference between blocks and shares is bigger for the ltcoin pool, meaning I got 4 much smaller shares last night. Presumably after your estimate of 10 hours, give or take (a lot), I'll get one share from P2Pool that's a good deal bigger than the ones I got last night from ltcoin, right?

BL5vKqnKHmnzvLZ5qCxETNnMzTM6CCdUzf/0.01+0.001

doing some CPU mining here now, looks good so far :)

Thank you for your help. I hope we will find a block eventually. Estimated time to block now is 6.5 hours.

Thanks, that's how I understood it to work.

So is there a number of pseudoshares I have to submit before I show up in the "Payouts if a block were found NOW" list?

Edit: Er, an estimated number? And, does my minerd know the difference?

We found a block !!!

Tue May 28 2013 21:53:21 GMT+0200 (Mitteleuropäische Sommerzeit )   402334   000000000894834c5541ed8d289a693736677d7bf8f28412405e4f1878ebd70b

edit : no payout though, not sure if that's working properly?

I'm not sure either. Now reading the logs. It definetly tried to submit it to bitbard, but then... I need a couple of minutes...

I'm not sure either. Now reading the logs. It definetly tried to submit it to bitbard, but then... I need a couple of minutes...

Oh crap  >:( I shouldn't have changed coinbase type to pubkeyhash.

The situation is like this.

Bitcoin/Bitbar/etc. address is encoded 160-bit hash of the public key. In Bitcoin, it is enough to provide coinbase (generation transaction) output. In PPC/NVC/BTB, coinbase type must be TX_PUBKEY, not TX_PUBKEYHASH, which means that you need full public key to create coinbase, not its 160-bit hash. So when a worker specifies its address as a username, the node cannot give it coins from the coinbase. Type of coinase outputs was TX_PUBKEY in NVC p2pool, so it didn't create payouts for workers. I changed it to TX_PUBKEYHASH, and as a result, the block was not accepted by bitbard. i will now change it back to TX_PUBKEY, so nodes can only mine to their own address. Worker names/addresses will be ignored (just like it is in NVC p2pool).

I have been unable to connect to the pool since yesterday, either with minerd or a web browser. It just times out.

Is it still at http://78.27.191.182:8333 ?

All work submitted to a node by workers is payed to the node address! Address specified as worker's username is ignored!
Download the source, host your node, point your workers to it.

How do I get this to work in Windows?

I've got the p2pool running in windows, how do I get the public key?

OK, cheers. So how long until payouts start from my own p2pool node?

Updated the code. Fixed worker payouts and graphs, added one more bootstrap node.

Ok, I'll try this out..

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?

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?

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.

p2pool_difficulty * (your_hashrate / p2pool_hashrate) * (time_to_block / 30s) / 10

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).

021c25e5046f6be38270ffe94ed4d2d05f926e957af6c061aaea3577fceb5822ed/0.25+0.025

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.
Increasing pseudoshare difficulty should decrease network/CPU load.

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.

Is that 0.5% for all blocks in Bitbar or just the way you set it up on this pool?