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

luthermarcus

full member

Activity: 213

Merit: 100

Quote from: jonnybravo0311 on July 13, 2015, 09:19:34 AM

Quote from: luthermarcus on July 12, 2015, 10:44:36 PM

Anyone know how to ban peers on bitcoin qt. I'm not sure it's possible.
Also can anyone point me in direction of a good tutorial for bitcoind?

Bitcoin 0.11.0 solves the freezing i was seeing (recommended to upgrade if you have issues) This release supports running a fully validating node without maintaining a copy of the raw block and undo data on disk. AKA pruning which has to be manually activated by using below code in
bitcoin config and don't use it if you use the wallet function because it turns it off. (also incompatible with -txindex will auto. turn it of)

prune=N : where N is the number of MB to allot for raw block & undo data (don't know what is a good number they mention 550mb though)

They are also recommending these for the transaction flooding

minrelaytxfee=0.00005
limitfreerelay=5 defualt=10

I'm not sure you can ban peers directly with the core software. If needed, I just add firewall rules to block the IP addresses of the bad peers. If you're using Ubuntu and ufw, it's absurdly easy:

Code:

ufw deny from IP_ADDRESS

My local node has been updated to core 0.11.0 and 14.0-9. While I'm still seeing higher-than-usual rejected hash rate percentages, I haven't experienced the freezing/lost contact issues again. So far, so good.

I heard blocking peers can effect your bitcoin node in a weird way. If you are using -addnode or -connect try using defualts and see if that fixes it.Depending on your peers take off firewall as well.

jonnybravo0311

legendary

Activity: 1344

Merit: 1024

Mine at Jonny's Pool

OgNasty runs his node in the EU (Germany): https://nastyfans.org/nastypool/. Not sure about west coast US nodes, though.

Automatic Monkey

hero member

Activity: 503

Merit: 500

Hey, can anybody recommend some good nodes to use for Nicehash (Amsterdam) and Westhash (San Jose)? I'm ready to drop some rental hash on it, when the price is right.

jonnybravo0311

legendary

Activity: 1344

Merit: 1024

Mine at Jonny's Pool

Quote from: luthermarcus on July 12, 2015, 10:44:36 PM

Anyone know how to ban peers on bitcoin qt. I'm not sure it's possible.
Also can anyone point me in direction of a good tutorial for bitcoind?

Bitcoin 0.11.0 solves the freezing i was seeing (recommended to upgrade if you have issues) This release supports running a fully validating node without maintaining a copy of the raw block and undo data on disk. AKA pruning which has to be manually activated by using below code in
bitcoin config and don't use it if you use the wallet function because it turns it off. (also incompatible with -txindex will auto. turn it of)

prune=N : where N is the number of MB to allot for raw block & undo data (don't know what is a good number they mention 550mb though)

They are also recommending these for the transaction flooding

minrelaytxfee=0.00005
limitfreerelay=5 defualt=10

I'm not sure you can ban peers directly with the core software. If needed, I just add firewall rules to block the IP addresses of the bad peers. If you're using Ubuntu and ufw, it's absurdly easy:

Code:

ufw deny from IP_ADDRESS

My local node has been updated to core 0.11.0 and 14.0-9. While I'm still seeing higher-than-usual rejected hash rate percentages, I haven't experienced the freezing/lost contact issues again. So far, so good.

Meuh6879

legendary

Activity: 1512

Merit: 1012

Quote from: squidicuz on July 12, 2015, 10:06:02 PM

If bandwidth is a major issue, you can try lowering the maximum allowed connected nodes. I personally have not seen what you are experiencing though...

Code:

--max-conns CONNS

thanks for this tips.

problem solve ... the shares of P2Pool are corrupted (i delete it, and after this, no problem with bandwidth).
strange.
first time.

luthermarcus

full member

Activity: 213

Merit: 100

Anyone know how to ban peers on bitcoin qt. I'm not sure it's possible.
Also can anyone point me in direction of a good tutorial for bitcoind?

Bitcoin 0.11.0 solves the freezing i was seeing (recommended to upgrade if you have issues) This release supports running a fully validating node without maintaining a copy of the raw block and undo data on disk. AKA pruning which has to be manually activated by using below code in
bitcoin config and don't use it if you use the wallet function because it turns it off. (also incompatible with -txindex will auto. turn it of)

prune=N : where N is the number of MB to allot for raw block & undo data (don't know what is a good number they mention 550mb though)

They are also recommending these for the transaction flooding

minrelaytxfee=0.00005
limitfreerelay=5 defualt=10

squidicuz

newbie

Activity: 58

Merit: 0

Quote from: windpath on July 12, 2015, 01:44:43 PM

Bitcoin Core 0.11.0 released

I will not have time to test it today, but it looks like there are a lot of speed improvements for the mempool that should speed up GBT latency.

https://bitcoin.org/en/release/v0.11.0

Would be interested in hearing anybody's experience

I have been using 0.11 for a couple weeks now. It works with latest p2pool, no issues, compiled from a local git clone. Working with the current version of the relaynodeclient as well.

Quote from: Meuh6879 on July 12, 2015, 10:32:32 AM

This day, "input already spend" overload my upload bandwidth ...
When i shutdown the P2Pool node, this isn't display (debug.log).

Have you somes tips to solve this ?
It's the first time that it's happend ... Huh

Bandwidth on P2Pool graphic is, it's true, saturated.

http://imagize[Suspicious link removed]ageshack.us/a/img633/7669/GKPWhg.jpg

If bandwidth is a major issue, you can try lowering the maximum allowed connected nodes. I personally have not seen what you are experiencing though...

Code:

--max-conns CONNS

Meuh6879

legendary

Activity: 1512

Merit: 1012

i use the RC2-RC3 since 2 weeks ... Wink

especially to test the pruning mode at the beginning.

windpath

legendary

Activity: 1258

Merit: 1027

Bitcoin Core 0.11.0 released

I will not have time to test it today, but it looks like there are a lot of speed improvements for the mempool that should speed up GBT latency.

https://bitcoin.org/en/release/v0.11.0

Would be interested in hearing anybody's experience

Meuh6879

legendary

Activity: 1512

Merit: 1012

This day, "input already spend" overload my upload bandwidth ...
When i shutdown the P2Pool node, this isn't display (debug.log).

Have you somes tips to solve this ?
It's the first time that it's happend ... Huh

Bandwidth on P2Pool graphic is, it's true, saturated.

jtoomim

hero member

Activity: 818

Merit: 1006

Quote from: p3yot33at3r on July 12, 2015, 05:43:55 AM

Quote from: jtoomim on July 11, 2015, 08:00:08 PM

Code:

minrelaytxfee=0.0001
mintxfee=0.0001

What are the standard settings if nothing is specified in the .conf file? I read about changing these in a guide alse where, but it was a little dated so decided against it.

Edit: Aaaaand another block!! Grin

I believe the defaults are 0 -- i.e., bitcoind will fill blocks with zero-fee transactions if no fee-paying transactions are available, as long as those free transactions are large and old enough.

I will probably upgrade our main node's hardware soon so it can better handle these spammy transaction volumes. I'm trying to decide if I should wait for Skylake to be released (August, supposedly) or just fork out for an i7 4790k now. Currently, the faster of my nodes runs on a Core i3 3.3 GHz (dual-core) with 4 GiB of RAM. I have seen the RAM get saturated on these nodes before and revert to swapping. I've got an 8 GiB RAM upgrade kit that arrived yesterday, and that also might be enough to solve the problem.

Meuh6879

legendary

Activity: 1512

Merit: 1012

Quote from: jtoomim on July 11, 2015, 08:00:08 PM

I had an issue like the above on my two p2pool nodes as well. It appears to be due to bitcoind getting overloaded from the stress test. I added this to my .bitcoin/bitcoin.conf file:

Code:

minrelaytxfee=0.0001
mintxfee=0.0001

After that, performance improved and the periodic bitcoind dropouts stopped.

I don't know what the threshold is for getting it to work. It's possible that 0.00005 or lower might work as well. Anyone want to play around with different values? I've got over 350 TH/s on my nodes, so I don't want to do anything with them that would cause unnecessary downtime.

Aha ! (yes) ... that's why i have, now, a saturated Upload ... Tongue

p3yot33at3r

sr. member

Activity: 266

Merit: 250

Quote from: jtoomim on July 11, 2015, 08:00:08 PM

Code:

minrelaytxfee=0.0001
mintxfee=0.0001

What are the standard settings if nothing is specified in the .conf file? I read about changing these in a guide alse where, but it was a little dated so decided against it.

Edit: Aaaaand another block!! Grin

squidicuz

newbie

Activity: 58

Merit: 0

Quote from: jtoomim on July 11, 2015, 08:00:08 PM

Quote from: Meuh6879 on July 10, 2015, 02:29:31 AM

http://imagize[Suspicious link removed]ageshack.us/a/img537/4057/vs3mqb.jpg

I had an issue like the above on my two p2pool nodes as well. It appears to be due to bitcoind getting overloaded from the stress test. I added this to my .bitcoin/bitcoin.conf file:

Code:

minrelaytxfee=0.0001
mintxfee=0.0001

After that, performance improved and the periodic bitcoind dropouts stopped.

I don't know what the threshold is for getting it to work. It's possible that 0.00005 or lower might work as well. Anyone want to play around with different values? I've got over 350 TH/s on my nodes, so I don't want to do anything with them that would cause unnecessary downtime.

I am using a min relay fee of .12 mBTC at the moment, at least until this spam clears out. A higher fee results in less transactions you are trying to mine with your node. I guess your node was hanging due to the large mempool when doing getblocktemplate.

Anyone else that is still experiencing bitcoind hangouts, please try increasing your minrelaytxfee?

jtoomim

hero member

Activity: 818

Merit: 1006

Quote from: Meuh6879 on July 10, 2015, 02:29:31 AM

I had an issue like the above on my two p2pool nodes as well. It appears to be due to bitcoind getting overloaded from the stress test. I added this to my .bitcoin/bitcoin.conf file:

Code:

minrelaytxfee=0.0001
mintxfee=0.0001

After that, performance improved and the periodic bitcoind dropouts stopped.

I don't know what the threshold is for getting it to work. It's possible that 0.00005 or lower might work as well. Anyone want to play around with different values? I've got over 350 TH/s on my nodes, so I don't want to do anything with them that would cause unnecessary downtime.

Meuh6879

legendary

Activity: 1512

Merit: 1012

... you reference to this ? http://bitcoin.stackexchange.com/questions/2640/p2pool-crashes-the-bitcoin-client

... 0.5.0 version of Bitcoin-QT ?

Roll Eyes

i can espect that developpers (of bitcoin) have solve this issue since a long time ...

no ? (it's a real and dumb question)

rav3n_pl

legendary

Activity: 1361

Merit: 1003

Don`t panic! Organize!

Quote from: notbatman on July 11, 2015, 04:57:05 PM

Quote from: mdude77 on July 11, 2015, 10:46:10 AM

Quote from: Automatic Monkey on July 09, 2015, 11:30:06 PM

OK I think I see the problem now. I actually was getting paid for the shares, and because I could not have bitcoind and bitcoin-qt open at the same time I couldn't see it. That problem was solved by installing an Electrum wallet on the machine that can be open with bitcoind.

I'm pretty sure you don't have to run bitcoind to use p2pool. bitcoin-qt works just fine for that purpose. At least that's how I did it when I was running p2pool on windows.

M

You need to run bitcoind now, bitcoin-core no longer supports mining. It's located in the bitcoin\daemon directory.

Add

Code:

server=1
daemon=1
rpcuser=something
rpcpassword=somethingmore

to bitcoin.conf in %appdata%/bitcoin directory

notbatman

legendary

Activity: 2212

Merit: 1038

Quote from: mdude77 on July 11, 2015, 10:46:10 AM

Quote from: Automatic Monkey on July 09, 2015, 11:30:06 PM

OK I think I see the problem now. I actually was getting paid for the shares, and because I could not have bitcoind and bitcoin-qt open at the same time I couldn't see it. That problem was solved by installing an Electrum wallet on the machine that can be open with bitcoind.

I'm pretty sure you don't have to run bitcoind to use p2pool. bitcoin-qt works just fine for that purpose. At least that's how I did it when I was running p2pool on windows.

M

You need to run bitcoind now, bitcoin-core no longer supports mining. It's located in the bitcoin\daemon directory.

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: Automatic Monkey on July 09, 2015, 11:30:06 PM

OK I think I see the problem now. I actually was getting paid for the shares, and because I could not have bitcoind and bitcoin-qt open at the same time I couldn't see it. That problem was solved by installing an Electrum wallet on the machine that can be open with bitcoind.

I'm pretty sure you don't have to run bitcoind to use p2pool. bitcoin-qt works just fine for that purpose. At least that's how I did it when I was running p2pool on windows.

M

p3yot33at3r

sr. member

Activity: 266

Merit: 250

Another yummy block

A proper one too, that contributes to the network. Unlike some other pools empty blocks........ Wink

A few more would be super nice.......

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