Anybody have any ideas how to increase the hash rate? We are sinking to a smaller and smaller percentage of the network, and round times are growing. We're having 4 day rounds now, a few more difficulty jumps and it may be weeks or longer.

Something must be done.

Fantastic news

Sounds like a positive

Unless you have a very fast internet connection (both up and down) without any hard or soft caps I recommend you just block incoming bitcoind connections at your firewall (i.e. don't forward port 8333) and rely on outgoing connections (the default 8 is fine -- no need to increase this). That will avoid a lot of your bandwidth being used up by people wanting to download the blockchain.

That alone should substantially increase the number of people who are able to successfully run a p2pool node.

I think I misinterpreted this statement about rounding up from https://en.bitcoin.it/wiki/Transaction_fees as applying to mintxfee. It probably doesn't (but I will look at the code soon).

"the reference implementation will round up the transaction size to the next thousand bytes and add a fee of 0.1 mBTC (0.0001 BTC) per thousand bytes"


I chose those values for testing purposes to simplify the collection of transactions (generally down to one or two) since I was seeing similarly confusing behavior with more reasonable settings.

I have blockprioritysize=0 and mintxfee=0.01 yet I'm still getting transactions with smaller fees. Does anyone know why before I start digging into the source code?

2014-02-28 14:48:26.238012 New work for worker! Difficulty: 156.935343 Share difficulty: 504240.247210 Total block value: 25.016500 BTC including 2 transactions

EDIT: Just a guess but maybe "per KB" is actually applied "per 1/2 KB"?

Those are much lower CFM than the original ones (as are most if not all "silent" fans). I wouldn't recommend as a replacement but as a second fan should be fine. (I didn't see the earlier context.)

Thank you.


2014-02-28 09:21:58.696997 > Error while processing Event callbacks:
2014-02-28 09:21:58.697274 > Traceback (most recent call last):
2014-02-28 09:21:58.697372 >   File "/home/p2pool/p2pool/p2pool/p2p.py", line 282, in handle_shares
2014-02-28 09:21:58.697467 >     self.node.handle_shares(result, self)
2014-02-28 09:21:58.697555 >   File "/home/p2pool/p2pool/p2pool/node.py", line 48, in handle_shares
2014-02-28 09:21:58.697869 >     self.node.set_best_share()
2014-02-28 09:21:58.697977 >   File "/home/p2pool/p2pool/p2pool/node.py", line 297, in set_best_share
2014-02-28 09:21:58.698067 >     self.best_share_var.set(best)
2014-02-28 09:21:58.698153 >   File "/home/p2pool/p2pool/p2pool/util/variable.py", line 74, in set
2014-02-28 09:21:58.698240 >     self.changed.happened(value)
2014-02-28 09:21:58.698327 > --- <exception caught here> ---
2014-02-28 09:21:58.698436 >   File "/home/p2pool/p2pool/p2pool/util/variable.py", line 42, in happened
2014-02-28 09:21:58.698523 >     func(*event)
2014-02-28 09:21:58.698608 >   File "/home/p2pool/p2pool/p2pool/node.py", line 96, in broadcast_share
2014-02-28 09:21:58.698694 >     peer.sendShares([share for share in shares if share.peer_addr != peer.addr], self.node.tracker, self.node.known_txs_var.value, include_txs_with\
=[share_hash])
2014-02-28 09:21:58.698782 >   File "/home/p2pool/p2pool/p2pool/p2p.py", line 290, in sendShares
2014-02-28 09:21:58.698867 >     assert tx_hash in known_txs, 'tried to broadcast share without knowing all its new transactions'
2014-02-28 09:21:58.698954 > exceptions.AssertionError: tried to broadcast share without knowing all its new transactions

I got an error where it said something about trying to broadcast a share without having all the transactions (?). Then the share was counted against orphans, I think. The message scrolled off before I could save it. There's no log file for p2pool right? At least I couldn't find it.

My BTC ROI was very slightly negative as well, and yes I'm pretty sure it depended on your date of buy in. These GBs were usually priced in dollars, with BTC conversion at the time of order.

Looking at the public node list, most of the public nodes are well under 1 TH. (That shouldn't be a surprise given the total hash rate for p2pool as a whole.) If you have a 500 GH node and take 1% that means your fee hash rate is 5 GH, making your fee payments quite small. Maybe not technically dust, but small enough to be annoying. Opinions differ but personally I'd rather get at least a 1-share fee occasionally.

WiFi is hit or miss on these and I don't think its actually supported, they just happen to be using a WiFi router as a control unit.

Your best bet is to get a cheap WiFi extender box with an ethernet port and plug into that. I have several hooked up like that and they work fine, but either way you have to make sure you have good WiFi coverage without interference.

Do you have data on the frequency of these transactions in mined blocks?

Some no-fee transactions won't get relayed by the standard client, but still might get included by a miner. Anth0ny seems to be saying that the majority of no-fee transactions are like that, but I'm not sure why he believes this.

The issue with this would be dust. If you have a 1% fee on your node then your node hash rate would have to be such that 1% of that wouldn't create dust on every block.

I have no comment on that. I requested a refund for my own reasons. You should do your own analysis and act accordingly.

OK, I understand that. FCFS starting with last payment. Makes sense.

Can somebody explain what the deal is with moving into worse position in the queue?  Wouldn't it make more sense for the queue to be like an actual queue (first in, first out).

Are you in the US? There is no customs duty on computer equipment, although I suppose they could still charge a processing fee for customs clearance (which as you say UPS apparently does not).

That was the originally stated policy for refunds. It is a "1.5% restocking fee." What exactly they are restocking has never been explained, but at this point I'd be very happy getting 98.5% of my coins back instead of the 0% I've actually gotten.