[1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool

[Amph]

yeah, two days and still no transactions, even with 4 share and efficiency of 130...
i switch to btcguild for now

[KALRONG]

yeah, two days and still no transactions, even with 4 share and efficiency of 130...
i switch to btcguild for now

remenber that the shares expire around 24h after you get them hehe

[gyverlb]

i guess 'mintxfee' would be the creation tx fee, which you probably wont want to change unless you want to increase fees on your own transactions.  i assume most pools run with the default setting of 0.0001

minrelaytxfee doesn't exist in 0.8.1 (it's a constant). Looking at the source (main.cpp, CTxMemPool::accept), I added:

Code:

limitfreerelay=0

to my configuration. It may not be enough (I've not fully grasped all the conditions where this is applied).

[daemondazz]

So I'm wondering whether the current long round time is related to the high latency issue. I've clicked on over a dozen of the servers in the list at http://p2pool-nodes.info/ and every single one of them has had a getwork template latency of >10 seconds.

I'm currently running a reindex on my bitcoind. It found a heap of orphan transactions and is now re-downloading the blockchain from around height 100,000...

I think I'm also going to have to temporarily switch to a different pool, until this catches up.

[mdude77]

So I'm wondering whether the current long round time is related to the high latency issue. I've clicked on over a dozen of the servers in the list at http://p2pool-nodes.info/ and every single one of them has had a getwork template latency of >10 seconds.

I'm currently running a reindex on my bitcoind. It found a heap of orphan transactions and is now re-downloading the blockchain from around height 100,000...

I think I'm also going to have to temporarily switch to a different pool, until this catches up.

I was thinking it might be related to the recent switchover.  5/15 just happened.

Could also be bad luck.

M

[GrapeApe]

I made some changes in the source code and compiled my own bitcoin-qt as per some controversial suggestions several weeks ago. My latency has been around 3.5 ms but about once an hour I get a spike as high as 2 seconds and that spike has caused a few orphans. What switch over are you speaking of on 5/15?

[gyverlb]

I made some changes in the source code and compiled my own bitcoin-qt as per some controversial suggestions several weeks ago. My latency has been around 3.5 ms but about once an hour I get a spike as high as 2 seconds and that spike has caused a few orphans. What switch over are you speaking of on 5/15?

On 2013/5/5 block size in 0.8.1 nodes are allowed to be >500000 bytes and <0.8.0 versions must be upgraded to avoid remaining behind IIRC.

[furball]

So I'm wondering whether the current long round time is related to the high latency issue. I've clicked on over a dozen of the servers in the list at http://p2pool-nodes.info/ and every single one of them has had a getwork template latency of >10 seconds.

I'm currently running a reindex on my bitcoind. It found a heap of orphan transactions and is now re-downloading the blockchain from around height 100,000...

I think I'm also going to have to temporarily switch to a different pool, until this catches up.

Could be right...I upgraded to the latest bitcoin version and applied the changes to the config per Prattlers suggestion and latency went away completely. What exactly do you mean by "catches up"? Will everybody need to update their bitcoind etc?

[powersync]

Can anyone point me in the right direction on how to update bitcoind from 8.1 to 8.2 from command line on a ubuntu 11.10 server with a tar file.  I have it extracted  and I run "make -f makefile.unix bitcoind".  It builds the files and I run it but it still shows 8.1 when I do a getinfo.  Any help would be great.

PS

[Richy_T]

Can anyone point me in the right direction on how to update bitcoind from 8.1 to 8.2 from command line on a ubuntu 11.10 server with a tar file.  I have it extracted  and I run "make -f makefile.unix bitcoind".  It builds the files and I run it but it still shows 8.1 when I do a getinfo.  Any help would be great.

PS

are you running it from the install directory? You may need to do a 'make install' to make it the system default.

[gyverlb]

I compiled the latest git version of bitcoind and with

Code:

mintxfee=0.01
minrelaytxfee=0.005

this is currently twice as fast as 0.8.1 with every settings I tried (from ~6s bitcoind latency to ~3s).

[K1773R]

3s lag? holy shit!

[Subo1977]

I compiled the latest git version of bitcoind and with

Code:

mintxfee=0.01
minrelaytxfee=0.005

this is currently twice as fast as 0.8.1 with every settings I tried (from ~6s bitcoind latency to ~3s).

I think These Settings Must be in satoshis for the latest git

[gyverlb]

I compiled the latest git version of bitcoind and with

Code:

mintxfee=0.01
minrelaytxfee=0.005

this is currently twice as fast as 0.8.1 with every settings I tried (from ~6s bitcoind latency to ~3s).

I think These Settings Must be in satoshis for the latest git

Damn that lack of hidden settings documentation...
It makes git performance even more interesting.

[furball]

Can anyone point me in the right direction on how to update bitcoind from 8.1 to 8.2 from command line on a ubuntu 11.10 server with a tar file.  I have it extracted  and I run "make -f makefile.unix bitcoind".  It builds the files and I run it but it still shows 8.1 when I do a getinfo.  Any help would be great.

PS

I had a similar issue compiling from the git repository after doing a "pull" of the latest code. Ended up moving the old bitcoin source to another directory and starting with a fresh clone of the Bitcoin source code. I just used "make -f makefile.unix" without bitcoind...seemed to work for me.

All the best with it.

[Mogumodz]

Hmmmmm

[K1773R]

Hmmmmm

ROFL

[furball]

Looks like a block was found in the last 30 minutes...hopefully we wont see another 3 day round like that for a while!

[Prattler]

Default settings are:

Code:

mintxfee=0.0001
minrelaytxfee=0.0001

If you're suffering from high getblocktemplate latency, try to increase both. Don't go crazy, just slightly higher than default should work. The goal here is that your mempool doesn't accumulate spam transactions that other pools won't confirm might take a while to get confirmed by pools.

These settings will get your getblocktemplate latency down:

Code:

mintxfee=0.0005
minrelaytxfee=0.0005

I think These Settings Must be in satoshis for the latest git

These settings need to be as floats in BTC.

Code:

    if (mapArgs.count("-minrelaytxfee"))
    {
        int64 n = 0;
        if (ParseMoney(mapArgs["-minrelaytxfee"], n) && n > 0)
            CTransaction::nMinRelayTxFee = n;
    }

ParseMoney parses strings, but only accepts float values in BTC, like "0.0005". "50000" will get parsed as 50000 BTC.
See https://github.com/bitcoin/bitcoin/blob/master/src/util.cpp#L417. Will edit if someone corrects me.

[powersync]

Can anyone point me in the right direction on how to update bitcoind from 8.1 to 8.2 from command line on a ubuntu 11.10 server with a tar file.  I have it extracted  and I run "make -f makefile.unix bitcoind".  It builds the files and I run it but it still shows 8.1 when I do a getinfo.  Any help would be great.

PS

I had a similar issue compiling from the git repository after doing a "pull" of the latest code. Ended up moving the old bitcoin source to another directory and starting with a fresh clone of the Bitcoin source code. I just used "make -f makefile.unix" without bitcoind...seemed to work for me.

All the best with it.

Yep I ended up doing the same thing.  Thanks

PS