Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 721. (Read 2591919 times)

Ah, I see that something broke on p2pool.info.  I'll have to fix it.

I'm sorry, I mean I have always used -a
p2pool.info shows unknow
my challenge is to see how quickly someone can figure out my address

It's only unknown if you not choosing it explicitly.  Stop doing that.

If you want to know what address it has been using for past mining, look through the log file.  It outputs the dynamic address in the log when it starts up.  You should also see it in the cached_payout_address file in the data directory.

"specify that address using the command line when you run the p2pool node using the -a parameter"

then it won't be unknown.  If you have it setup for dynamic address it will change everytime p2pool restarts so even if you figure it out it will be different next time.  Just follow the recommendation.  STOP p2pool, start it with -a (payout address) parameter.  Then you will always know what it is.

Address is currently unknown though.

1. Go to http://p2pool.info
2. Switch to the Current Payouts tab
3. Find your address, and click the star icon
4. Come back from time to time and look for the yellow row

If your question really is, "how do I know what address I am using" then you are doing it wrong*  Instead of letting p2pool choose an address dynamically, pick one yourself.  Get a new address form your preferred bitcoin wallet  and do one of the following:

1. Specify that address as your username on all of your miners
2. Or specify that address using the command line when you run the p2pool node using the -a parameter



*Yes, technically it's not wrong to let p2pool get a dynamic address, but it just confuses people and there is no real benefit to letting it be dynamic, so just don't do it.

To whoever figures out my payout address and give me a blockchain.info link gets 0.03 BTC

I dunno about on p2pool.info but if you go to blockchain.info you can get some good info about what's happening at your payout address

http://blockchain.info/address/1CLYeVZdVh5XWmQxU5euYbNQ3LwqLhBjbT

of course replace the address above with your own payout address.

How do i monitor my payout address on p2pool.info?

Fine with me.  Full disclosure, though, that I borrowed the idea from an image I saw in someone else's forum avatar, so it's not my original idea.

I believe it was twmz.

Don't forget about http://p2pool.info/

I use it to check stats all the time from my phone.  It would be great if it had additional stats for individual mining addresses.

Duplicated work, security, and the fact that bitcoind is in beta (v 0.6).  

Every time there is a change to bitcoind, p2pool developers would need to spend time figuring out what the change it, how to integrate it into bitcoind/p2pool hybrid.  bitcoind exposes JSON for a reason to allow integration without requiring a custom hybrid application.

Making a GUI or web dashboard for p2pool is currently possible.  If a static address is used you can even lookup total revenue via blockchain.info. You could also lookup low level miner stats via cgminer JSON API.  Someone just needs to do it.

Lastly making p2pool friendly to complete noobs is likely futile.  As p2pool grows it becomes less attractive to tiny noob miners no matter how easy the code becomes.  So building robust tools which are attractive to medium sized miners is likely a better use of resources.

No, the namecoin (and other merged chains) side is pure solo mining.
That "generate" is whether namecoind is generating (using cpu). False is probably what you want.
Actually 8th April, 22:34 

Thanks.  I didn't know about the command line commands, I didn't start working with bitcoins until the GUI was already done.  Those work for my purposes.


Any particular reason why not?  It seems like the absolute easiest system for a newbie windows miner would be a simple one piece program that you install and it gives you the p2pool program, a wallet, bitcoind, and a usable GUI with info such as current payout, total mined, wallet balance, mined per day, perhaps even integrate a miner if that is possible.  Such that you just install the program using all defaults, run the .exe and you are mining.  If you don't want to use the included wallet and wallet functionality, you can use the equivalent of the -a command and use your own wallet located wherever.

talking of....
can I set static namecoin address in merged p2pool mining?


thank you, naimecoind getinfo show "generate" : false,
it is right?

You can use either bitcoind or bitcoin-qt (GUI) while mining w/ p2pool.
bitcoind when running unintuitively is blocking and responds to no commands.
Once bitcoind is running you can simply run the desired command from a second command line (in windows).


to get a list of all RPC

Including wallet functionality in p2pool doesn't seem like a good solution.


I agree and hopefully forrestv sees this.  The default option should be a static payment address.  Not just for your particular case but because dynamic unspecified payment address isn't intuitive to most users.   Those who would want that option are likely savy enough to manually specify it. 

"Normal" pools ask users for a payment address so by default it is more intuitive if p2pool does also.

There often are complaints about "not getting paid" because user is looking at address A in blockchain.info but address B is now being used.  Many new users just startup p2pool with no options and then are confused as to where they the payment is going.  Even those who figure it out may not realize that each time p2pool starts it can pick a new address. 

Tools like http://p2pool.info are more useful with  a static payment address.

Honestly I think dynamic addresses as the default just create confusion and produce very little value.  It is similar to how solo-mining works (and I guess the reason forrestv made it work that way) but most users no longer solomine.

If it were me I would drop the -a option make an address a required parameter which can be overridden by a new "-d | --dynamic" parameter.

i.e. something like

FYI,you can send commands to a running bitcoind instance from another window. It is annoying that it doesn't just log to stdout or else fork to the background by default, but since it doesn't, just open a new command window and run the commands to access bitcoind as usual, and the one that you run will talk to the already-running instance and send you the data.

So, to get information about the currently running instance of bitcoind, just open a new command window and type 'bitcoind getinfo' (no quotes) and it will start a new instance of bitcoind that talks to the running instance and will spit out the requested information.

Although I haven't tested it, I hear it should be possible to tell the GUI to talk to a running bitcoind as well, but I don't what arguments that would require.

I was talking about the balance on the bitcoin wallet that bitcoind is running from.  Since you can't run the wallet simultaneously, the only way to find the balance is to stop mining briefly and open up the wallet.  If the p2pool occasionally showed the balance of the wallet in it's output this wouldn't be an issue.  Of course, I learned about the -a option later which makes this obsolete, maybe some people don't run with -a for various reasons and would like to know their balance with stopping the miners and bitcoind?


Yes, the -a option makes it perform much like a regular pool.  There is just an extra piece that needs to be installed, but it's not too much extra work.  I'll be using -a to payout to my normal secure wallet from now on.  Maybe my case is unusual, but it seems like the -a option should be the default.

Simple version:
p2pool (your node or any node) only has knowledge of the single payment address used.  Without -a it is a random address from the wallet (which changes on each run).  With the -a option it is the address you provide.  All compensation (block subsidy, tx fees, donations, etc) are split among all node's addresses by hashing power.

All nodes (not just yours) split the total block reward by the % each address has in the sharechain.  Anything else would be an invalid share.

More complex:
tx fees are part of block reward.  subisdy + tx fees = block reward.  For each getwork every node takes all the shares in the sharechain and determines what % belong to each address.  It then builds a coinbase sending that % of total block reward to each address.  If address a has 1% of shares in sharechain it gets 1% of reward, if address b has 10% it gets 10% of the reward.