|
The "Cumulative hashes reflected in blocks in an alternate universe" line was the result of a simulation done using P2Pool's hash rate data that assumes that P2Pool is working perfectly. It was useful to get an idea of the variance to be expected in the green line. It changed every hour.
I just changed it to display 30 of the same thing, so now it gives a better idea of the expected variance in the blue line.
EDIT: I wouldn't say that they're definitely spreading.. and no, assuming nothing is wrong (no bugs or people maliciously dropping block solutions), it's due to bad luck. They should eventually converge.
|
|
|
|
|
Using "--gpu-threads 1" isn't at all essential for P2Pool. I get fine reject rates without it.
There's an optimum point that balances between a lower rejection rate and a lower hash rate, you just have to find it. However, you might be below that point.. maybe try dropping --gpu-threads 1 or a slightly higher intensity. (Bitcoin has a balance in the same manner, it's just at a very different point since work needs to be updated every 10 minutes instead of 10 seconds.)
|
|
|
|
|
The "VIP password" doesn't do anything except affect the deprecated RRD graphs.
|
|
|
|
|
Hm.. Is it possible for you to use the "-a" argument to p2pool to set the address instead of the miner username? The miner username is only really useful if you have a public p2pool node that others mine on.
|
|
|
|
|
The bitcoin 0.5.4 backport works too - see the first post here for a link.
|
|
|
|
I have 2 questions:
1. Why did it go down?
2. Will it go up? Why?
Are you mining to a different address by setting your miner's username to a Bitcoin address? The "current payout" graph only displays bitcoins going to the default address. Did you maybe change your miner's username to a Bitcoin address about 24 hours ago..? |
|
|
|
|
DeathAndTaxes: Yes, it only listens for block invs, but also polls getmemorypool occasionally, so it does update the txs.
Ente: The share count varying is normal. Peers only exchange blocks of 1000 shares, when you start P2Pool, it loads more shares than it needs, and last, other peers that are downloading the sharechain may rebroadcast old shares that your node remembers for a while.
|
|
|
|
|
No, it connects to bitcoind over the P2P port and listens for "inv" block messages. So, yes, it's asynchronous.
|
|
|
|
Need clarification on how p2pool builds a block header.
Does this sound right?
1) p2ool uses RPC call "getmemorypool" to get block components from bitcoind
2) p2pool generates coinbase transaction from current sharechain
3) p2pool generates merkle tree (combining tx from bitcoind w/ coinbase from sharechain).
4) p2pool issues block headers to miners via getwork call (prior block, timestamp, merkle tree root, difficulty)
Right? Wrong? Clarifications?
Nobody? OK how about 1 BTC bounty a) verify and/or correct the above execution flow above. b) provide filename and line # of code (p2pool github) where p2pool pulls works from bitcoind. c) provide fielname and line # of code (p2pool github) where p2pool modifies work from bitcoind to include coinbase reward split. That's correct. P2Pool calls "getmemorypool" from p2pool.main.getwork (main.py line 30) and the generation transaction for a share is computed in p2pool.data.Share.generate_transaction (data.py lines 130-145 and 164). I have to say.. I don't think this should be that hard to find. EDIT: Some more details: The current work from bitcoind is held in the current_work and current_work2 variables in main.py. When mining for a share, generate_transaction is called from WorkerBridge.get_work (line 535-554) in main.py. When a share is being validated, generate_transaction is called from Share.check in data.py (line 238). P2Pool actually combines everything into a work unit on lines 581-588 in main.py. EDIT EDIT: I think the reason you didn't get an answer is that most people were sleeping in between your two posts.. I was. |
|
|
|
I am playing around with usernames (to change difficulty). Now the whole username (including the postfix /1000+1) is shown in the statistics, and whenever I change the postfix a new miner shows up in the stats. WHen I delete the rrd stuff, the deprecated rrd graphs are cleaned. How can I clean/reset the new graphs? I deleted most files in /data/bitcoin (or similar), no help. I had to reinstall p2pool, which starts the whole sharechain-load+verify again. I would love to see the postfix ignored in the graphs altogether? In the meantime, where is the data stored? Ente In the graph_db file. There isn't a way to just remove one username, but I'll change it to make it only consider the first part of the username. |
|
|
|
Uh, so what happens when a few, or when most nodes switch? I can't imagine the sharechain would split, you would have made instructions about that. So it doesnt matter when we switch, as long as it is in the next days? Sooner, to get all the nice new features! :-)
You can upgrade anytime you want between now and April 1. Assuming this is going to work just like the last protocol change a few weeks ago, the p2pool software will automatically switch from the old way to the new way at midnight (U.S. Eastern Time probably) on April 1. And there is probably a 1 hour grace period like there was last time to account for the fact that everyone's clocks are not exactly synchronized. That's mostly correct, but there's no grace period this time because it's syncronized to the sharechain's time, not users' clocks. Also, it's midnight UTC this time to coincide with the BIP16 date. I know bitcoind generates the "getwork" but does p2pool have any control over it. Say I wanted to only include paying transactions with a fee of >= 0.01 BTC in my blocks.
Does that require modifying p2pool to request modified work from bitcoind or simply modifying bitcoind to only include the matching transactions in the merkle tree?
In theory, you could do it either way, but changing CreateBlock in bitcoind would be a lot easier because p2pool doesn't have a way to figure out fees and there are probably existing patches to bitcoind to do this. |
|
|
|
p2pool shows a global hashrate stat shown at "/rate" or on the p2pool command line. Anyone know over what time period that is calculated? Last hour? Last day? Last x shares? I got an idea for a promo / contest involving p2pool.
720 shares, which should normally be 720*10 seconds = 2 hours. This should be more self-documenting.. maybe return a JSON Object with an "averaging period" attribute. --- Thanks for the recomendations about handling the donation amount. I will implement the warning-on-p2pool-start idea. Also, the RRD graphs are deprecated. The new JavaScript-based ones have a lot more potential and flexibility. They don't have support for measuring individual miners yet, but that will come soon. Does anyone know if there are plans for a p2pool WITHOUT bip16 support come april 1st? Would p2pool be robust enough to work in a mixed client scenario?
It seems to me like there could be quite a few miners who like the idea and lower variance of p2pool but would also like some say in which changes get accepted into the bitcoin protocol.
BIP16 is already final. It has >50% of he Bitcoin network's hash rate behind it. Any attempt at opposing it can only invalidate your own work. Note that during the last few months, P2Pool has passed through your bitcoind's "coinbaseflags" into mined blocks, which let you vote during the period where it mattered. |
|
|
|
Hi!
The following error can be ignored?
Thanks for that report, Thiago. I just fixed it in git. |
|
|
|
I get an error:
at least one server needs to be running??
Maybe you didn't forward the port? The friend needs to be able to connect to port 9332 (p2pool's port). |
|
|
|
Last q, even if I explicitly set payout add, i dont have to do a thing to let users successfully use their add as a username?
Nope, username always overrides the set payout address unless there's a fee set. |
|
|
|
No, nothing there needs to be private (it does expose your payout address though). The only possible attack is a DoS. No, you need to run "bitcoind sendmany XXX" to make the transaction. That just creates the output list. |
|
|
|
|
Show Posts
