[BTB][P2POOL][UPDATED] Source + 0% public node! Read instructions carefully! - page 2.

baloo_kiev

sr. member

Activity: 476

Merit: 250

Quote from: ?? on ??

Quote from: baloo_kiev on May 31, 2013, 09:04:25 AM

Quote from: ?? on ??

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:/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.

baloo_kiev

sr. member

Activity: 476

Merit: 250

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

jdebunt

legendary

Activity: 1596

Merit: 1010

gonna run this tonight to see how it goes, thanks for all the work

baloo_kiev

sr. member

Activity: 476

Merit: 250

Quote from: ?? on ??

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!

baloo_kiev

sr. member

Activity: 476

Merit: 250

Quote from: ?? on ??

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 Grin

baloo_kiev

sr. member

Activity: 476

Merit: 250

First block with payout to worker addresses!
http://btb.cryptocoinexplorer.com/block/0000000000ab9f661bdeb1367d553abee759326ba9244601ca09fb599176b00c

baloo_kiev

sr. member

Activity: 476

Merit: 250

Updated the code. Payouts to worker addresses now work! I open my public node to miners again. However, unlike with other p2pools, you have to specify your public key (not an address!) as username.
Since I am not a developer, I used a crazy python hack containing several lines of shit-code to achieve it. However, it works and generates payouts to workers. I have tested it in the testnet.

To point worker to my (or any other) public node you have to get a public key:
1) launch bitbar

2) in bitbar directory, run

Code:

./bitbard getnewpubkey "someccount"

you will receive a hex string, call it , which is the public key to a new address in account "someaccount" (you don't have to keep it secret, as it's public)

3) (optionally) make sure it works as supposed to: run

Code:

./bitbard getaddressesbyaccount "someaccount"

you should see a new address, and

Code:

./bitbard validatepubkey

will return JSON object, which is expected to have 'isvalid' and 'ismine' properties set to 'true'

4)use as a worker username when connecting to a public node, just like you use your address with other coin p2pools. You may now close your bitbar.

baloo_kiev

sr. member

Activity: 476

Merit: 250

Added bootstrap address.

MoTLD

newbie

Activity: 42

Merit: 0

Thanks for explaining! Setting up my own instance of P2Pool is probably beyond my current capabilities, but I'll read up on the technical details and see if I'm up to it. Probably about the time I get it working, you'll have yours back to accepting outside connections... Wink

baloo_kiev

sr. member

Activity: 476

Merit: 250

Quote from: MoTLD on May 29, 2013, 06:40:35 PM

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 ?

I closed access to port 8333 from outside because of this:

Quote from: baloo_kiev on May 27, 2013, 04:42:50 PM

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.

If I open it, you will be able to connect, but all your work in this case will generate payouts to my address! So it only works like described above: launch bitbard and p2pool on your computer and point your workers to it. Your p2pool node will connect to my p2pool node (and other running nodes), grab an address from your local bitbard and generate payouts to this address.

I am trying to enable payouts to worker addresses now and will update if I get it working. Please read the thread if you want more technical details. Stay tuned!

MoTLD

newbie

Activity: 42

Merit: 0

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 ?

baloo_kiev

sr. member

Activity: 476

Merit: 250

One more fix: disable reward rounding to cents, which is used in NVC but not BTB.
Previously found blocks generated 0.17 BTB instead of 0.172421 (e.g. http://btb.cryptocoinexplorer.com/block/0000000011f9f1834ebb07844db877b6016d9a8b0cb7191a13229066976ef197)

baloo_kiev

sr. member

Activity: 476

Merit: 250

Fixed links to block explorer on the stats page.

baloo_kiev

sr. member

Activity: 476

Merit: 250

First block found!

http://btb.cryptocoinexplorer.com/block/00000000055aa1afdb25984d4740e1e81f79c8f258cce029483a1c51c2b83fd6

baloo_kiev

sr. member

Activity: 476

Merit: 250

One more fix. Re-download the source, please.

baloo_kiev

sr. member

Activity: 476

Merit: 250

Download the code from github and clear data/bitbar directory.

baloo_kiev

sr. member

Activity: 476

Merit: 250

Quote from: baloo_kiev on May 28, 2013, 03:40:24 PM

Quote from: baloo_kiev on May 28, 2013, 03:20:41 PM

Quote from: jdebunt on May 28, 2013, 03:07:24 PM

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

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

Fixed code at github.
All work submitted to a node by workers goes to the node's address!

jdebunt

legendary

Activity: 1596

Merit: 1010

Only 1 way to learn these things, is by trial & error

baloo_kiev

sr. member

Activity: 476

Merit: 250

Quote from: baloo_kiev on May 28, 2013, 03:20:41 PM

Quote from: jdebunt on May 28, 2013, 03:07:24 PM

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

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

jdebunt

legendary

Activity: 1596

Merit: 1010

Quote from: baloo_kiev on May 28, 2013, 03:20:41 PM

Quote from: jdebunt on May 28, 2013, 03:07:24 PM

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

Take your time, don't worry, just letting you know

Topic: [BTB][P2POOL][UPDATED] Source + 0% public node! Read instructions carefully! - page 2. (Read 4630 times)