Bitcoin Forum
March 19, 2024, 08:00:34 AM *
News: Latest Bitcoin Core release: 26.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 [518] 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 ... 814 »
  Print  
Author Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool  (Read 2591571 times)
PatMan
Hero Member
*****
Offline Offline

Activity: 924
Merit: 1000


Watch out for the "Neg-Rep-Dogie-Police".....


View Profile WWW
August 25, 2014, 07:26:03 PM
 #10341

Good stuff  Smiley

The way I see it, the less processes running - the more resources available for p2pool/bitcoind, especially when java is involved  Wink

"When one person is deluded it is called insanity - when many people are deluded it is called religion" - Robert M. Pirsig.  I don't want your coins, I want change.
Amazon UK BTC payment service - https://bitcointalk.org/index.php?topic=301229.0 - with FREE delivery!
http://www.ae911truth.org/ - http://rethink911.org/ - http://rememberbuilding7.org/
1710835234
Hero Member
*
Offline Offline

Posts: 1710835234

View Profile Personal Message (Offline)

Ignore
1710835234
Reply with quote  #2

1710835234
Report to moderator
1710835234
Hero Member
*
Offline Offline

Posts: 1710835234

View Profile Personal Message (Offline)

Ignore
1710835234
Reply with quote  #2

1710835234
Report to moderator
"Governments are good at cutting off the heads of a centrally controlled networks like Napster, but pure P2P networks like Gnutella and Tor seem to be holding their own." -- Satoshi
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1710835234
Hero Member
*
Offline Offline

Posts: 1710835234

View Profile Personal Message (Offline)

Ignore
1710835234
Reply with quote  #2

1710835234
Report to moderator
1710835234
Hero Member
*
Offline Offline

Posts: 1710835234

View Profile Personal Message (Offline)

Ignore
1710835234
Reply with quote  #2

1710835234
Report to moderator
1710835234
Hero Member
*
Offline Offline

Posts: 1710835234

View Profile Personal Message (Offline)

Ignore
1710835234
Reply with quote  #2

1710835234
Report to moderator
drukoz2
Member
**
Offline Offline

Activity: 395
Merit: 10


View Profile
August 25, 2014, 10:17:10 PM
 #10342

i am currently earning 0.035 - 0.04 btc everyday with 1.5 TH i wanted to know how much would i earned in p2pool and wicth pool would i use since there are lots of them or i don't get it would love some explanation
the same or more.
You dont use a public p2pool, you setup p2pool on a local machine.
Mining on a remote p2pool is stupid and if you want to do this, you could just stick to the pool your already using.
So much fail.... *sigh*  And people wonder why p2pool doesn't get higher adoption rates with answers like this.

You CAN use a public P2Pool node, take a look at this page for a listing of some of them - http://p2pool-nodes.info/ - you can sort by country, latency, etc.  Just find a couple geographically close to you and ping them... the lower the ping (latency), the better off you will be.

It is absolutely NOT stupid to mine on a remote p2pool node, especially if you have one close enough to you.  If you aren't close enough to a public node it could affect your performance, so it might be more wise to look at building your own local node if you have the capability, but some folks don't have the resources to do that.  It's all about your comfort level and resources.

The main issue with p2pool is latency - how quickly your miners can communicate to the node you're mining on.  The lower the latency, the less DOA rate you will have.  The less DOA you have the better chance you have of getting good shares, and thus payouts.  This is why it's RECOMMENDED to bring up your own p2pool node locally, because obviously the miners are right next to the node.

There's a bunch more to go into with DOA, shares, stales/orphans and how in general it works if you want to.  The bottom line is that all things equal, over time, you should see at least equal if not better payouts on p2pool versus others, as long as you have a decent hashrate, which I personally consider over 600GH/s.  Judging from your payouts I'd say you have about 1.2-1.5 TH/s, which should be plenty fine.

To configure it's simple.  Once you find a pool node it would look like this-

Pool: stratum+tcp://ip.add.ress.here:9332
Pool worker:  {your bitcoin payment address here}
Pool password:  anything123

I would suggest finding at least 2 P2Pool nodes for pool1 and pool2, and then put your original proprietary node in for pool3.  This way you're covered with failovers and backup in case any of the p2pool nodes go down.

And, no matter what pool node you mine on, if you keep your payment address the same (the pool worker), your shares and payouts will "follow" you to whatever node you're on, so you won't lose any mining time if you failover to another node.

Hope this helps to get you started.  Read up on the last 20-30 pages of this thread if you can at least, and post more questions, most folks here are pretty helpful.



allright so i looked at the other p2pools remote from whre i am now shoudl i put those in higher priority ? then my local one ?


i am currently earning 0.035 - 0.04 btc everyday with 1.5 TH i wanted to know how much would i earned in p2pool and wicth pool would i use since there are lots of them or i don't get it would love some explanation

the same or more.

In the short term (i.e. "per day") variance will be much higher. At 1.5 TH/s and the current pool rate you should expect a payout from each block the pool finds (after you have a share in the chain), here is the closest example to 1.5 TH/s I could find on my node, the payouts per block should give you an idea of what to expect:

http://minefast.coincadence.com/miner.php?id=1JPVPkdnpYYwyYic51id6anMBn9weHwVV9

You dont use a public p2pool, you setup p2pool on a local machine.

Mining on a remote p2pool is stupid and if you want to do this, you could just stick to the pool your already using.

I disagree.

While setting up your own local node is ideal, and how p2pool is intended to be used, it is not a requirement, and mining on a public node is a great way to get started with p2pool.

There are many 0% fee public nodes available to give the pool a try, I would recommend committing for a minimum of 4 days. P2pool uses a PPLNS payout system and the share chain is ~3 days long, any amount of time under that will not give you accurate results.

In picking a public node latency (the time it takes your data to reach the server) is very important. Find your 2-3 closest nodes by using ping and use those in your miner configuration.

My node is in the US east, for other nodes you can explore here:

http://p2pool-nodes.info/

Patience is very important with p2pool. Once you are connected to your closest node for a couple hours check the stats, as long as your DOA rate is lower then the pool average your are doing just fine. Then sit back and let your miners do their thing. Again I would say 4 days is a minimum.



i will be doing this thank you very much for your help Cheesy
hamburgerhelper
Member
**
Offline Offline

Activity: 83
Merit: 10


View Profile
August 26, 2014, 01:09:11 AM
 #10343

If you're running RelayNodeClient.jar it looks like it's time to upgrade. I got the following email from the author, Matt Corallo:

Sorry for the inconvenience, please upgrade your relay client node as an
incompatible server change was made Sad. Still, fitting most blocks in
one TCP packet is probably worth it.

I'm waiting to hear back from him to see if he will be producing a .jar file, right now there's only RelayNodeClient.java.
kgb2mining
Member
**
Offline Offline

Activity: 112
Merit: 10


View Profile
August 26, 2014, 01:13:44 AM
 #10344

If you're running RelayNodeClient.jar it looks like it's time to upgrade. I got the following email from the author, Matt Corallo:

Sorry for the inconvenience, please upgrade your relay client node as an
incompatible server change was made Sad. Still, fitting most blocks in
one TCP packet is probably worth it.

I'm waiting to hear back from him to see if he will be producing a .jar file, right now there's only RelayNodeClient.java.
If you're in conversation with him, can you ask whether the jar file is even needed?  Seems like putting it in the bitcoin.conf does the trick as well, or are there things within the jar that specifically aren't available by just peering using "addnode"?  If it's fine just peering, like PatMan said, one less thing to have to worry about especially with the associated java bloat.
hamburgerhelper
Member
**
Offline Offline

Activity: 83
Merit: 10


View Profile
August 26, 2014, 01:20:19 AM
 #10345

Good idea. I'll see what he says.
Matt Corallo
Hero Member
*****
Offline Offline

Activity: 755
Merit: 515


View Profile
August 26, 2014, 01:31:58 AM
 #10346

Someone asked me this in email so I figured I'd copy the response here:

> Someone on the forum wanted me to ask if there's any advantage to
> running java RelayNodeClient versus simply connecting bitcoind to the
> Relay Network via "addnode"?

Yes, there is quite a huge advantage to it - namely if you connect to
your nearest Relay Network addnode you get the blocks relayed as normal
(ie the whole block is sent again), if you use the relay client (which,
despite it being java uses almost no memory/CPU, and can be easily kept
from growing its heap with -Xmx100m) the only thing relayed over the
wire is transactions you havent seen before, so it can (more often than
not) fit the entire block in one TCP packet. Also, addnode does not
reconnect very aggressively and, as such, if the relay node gets
restarted due to upgrade or whatever, you will likely lose the
connection and not end up reconnecting for a day or so, however the
relay network client will reconnect almost immediately.

If there is enough demand, I've been considering rewriting the relay network client in Rust/C++/whatever for those with concerns.

Matt

Bitcoin Core, rust-lightning, http://bitcoinfibre.org etc.
PGP ID: 07DF 3E57 A548 CCFB 7530  7091 89BB B866 3E2E65CE
hamburgerhelper
Member
**
Offline Offline

Activity: 83
Merit: 10


View Profile
August 26, 2014, 01:35:49 AM
 #10347

^ That's what he says. Smiley
Matt Corallo
Hero Member
*****
Offline Offline

Activity: 755
Merit: 515


View Profile
August 26, 2014, 01:38:49 AM
 #10348

On a related note, I usually dont monitor bitcointalk, but if you have any questions regarding the relay network, bitcoin-peering@ my full name.com is there to help.

Bitcoin Core, rust-lightning, http://bitcoinfibre.org etc.
PGP ID: 07DF 3E57 A548 CCFB 7530  7091 89BB B866 3E2E65CE
PatMan
Hero Member
*****
Offline Offline

Activity: 924
Merit: 1000


Watch out for the "Neg-Rep-Dogie-Police".....


View Profile WWW
August 26, 2014, 01:41:01 AM
 #10349

Someone asked me this in email so I figured I'd copy the response here:

> Someone on the forum wanted me to ask if there's any advantage to
> running java RelayNodeClient versus simply connecting bitcoind to the
> Relay Network via "addnode"?

Yes, there is quite a huge advantage to it - namely if you connect to
your nearest Relay Network addnode you get the blocks relayed as normal
(ie the whole block is sent again), if you use the relay client (which,
despite it being java uses almost no memory/CPU, and can be easily kept
from growing its heap with -Xmx100m) the only thing relayed over the
wire is transactions you havent seen before, so it can (more often than
not) fit the entire block in one TCP packet. Also, addnode does not
reconnect very aggressively and, as such, if the relay node gets
restarted due to upgrade or whatever, you will likely lose the
connection and not end up reconnecting for a day or so, however the
relay network client will reconnect almost immediately.

If there is enough demand, I've been considering rewriting the relay network client in Rust/C++/whatever for those with concerns.

Matt

Thanks for clearing that up Matt!  I'm not a big fan of java tbh (as you can probably tell  Wink), so if you do get enough demand for the client in C++/whatever I'd definitely be interested in using that instead.

Nice one  Smiley

"When one person is deluded it is called insanity - when many people are deluded it is called religion" - Robert M. Pirsig.  I don't want your coins, I want change.
Amazon UK BTC payment service - https://bitcointalk.org/index.php?topic=301229.0 - with FREE delivery!
http://www.ae911truth.org/ - http://rethink911.org/ - http://rememberbuilding7.org/
hamburgerhelper
Member
**
Offline Offline

Activity: 83
Merit: 10


View Profile
August 26, 2014, 01:50:20 AM
Last edit: August 26, 2014, 02:04:19 AM by hamburgerhelper
 #10350

This may not be too useful since most people don't run CentOS7 / RHEL7, but here's a systemd script to run the RelayNodeClient application. Systemd has the very nice feature that it will restart the process if it dies, and all stdout messages can be monitored with "journalctl -f -u relaynodeclient". Put the text below into a file such as: /etc/systemd/system/relaynodeclient.service

Then change the following to appropriate values:

Change to the name of your bitcoind systemd unit file:
Code:
After=bitcoin.service

Change to the name of your relaynodeclient user and group:
Code:
User=YOURRELAYUSER
Group=YOURRELAYGROUP

Change to the Relay Network region closest to your p2pool node:
Code:
ExecStart=/bin/java -Xmx100m -jar /PATH/TO/RelayNodeClient.jar public.YOURRELAYREGION.relay.mattcorallo.com 127.0.0.1:8333

Code:
[Unit]
Description=relaynodeclient
After=network.target
After=bitcoin.service

[Service]
Type=simple
User=YOURRELAYUSER
Group=YOURRELAYGROUP
ExecStart=/bin/java -Xmx100m -jar /PATH/TO/RelayNodeClient.jar public.YOURRELAYREGION.relay.mattcorallo.com 127.0.0.1:8333
Restart=always

[Install]
WantedBy=multi-user.target

*Edited to add Matt's suggestion of limiting java's heap space to 100 MB to conserve RAM.
windpath
Legendary
*
Offline Offline

Activity: 1258
Merit: 1027


View Profile WWW
August 26, 2014, 02:11:12 AM
 #10351

Someone asked me this in email so I figured I'd copy the response here:

....

Thank you very much Matt!!
PatMan
Hero Member
*****
Offline Offline

Activity: 924
Merit: 1000


Watch out for the "Neg-Rep-Dogie-Police".....


View Profile WWW
August 26, 2014, 02:18:22 AM
 #10352

Change to the Relay Network region closest to your p2pool node:
Code:
ExecStart=/bin/java -Xmx100m -jar /PATH/TO/RelayNodeClient.jar public.YOURRELAYREGION.relay.mattcorallo.com 127.0.0.1:8333

Shouldn't this be:

Code:
ExecStart=/bin/java -Xmx100m -jar /PATH/TO/RelayNodeClient.jar public.YOURRELAYREGION.relay.mattcorallo.com:8335

 Huh

"When one person is deluded it is called insanity - when many people are deluded it is called religion" - Robert M. Pirsig.  I don't want your coins, I want change.
Amazon UK BTC payment service - https://bitcointalk.org/index.php?topic=301229.0 - with FREE delivery!
http://www.ae911truth.org/ - http://rethink911.org/ - http://rememberbuilding7.org/
kgb2mining
Member
**
Offline Offline

Activity: 112
Merit: 10


View Profile
August 26, 2014, 02:20:18 AM
 #10353

Indeed, thanks a bunch Matt and hamburgerhelper!  Very useful and appreciate the quick response.

Been away from java for a couple years, forgot about xms and xmx... that should help my 11G virt mem issue... Smiley
kgb2mining
Member
**
Offline Offline

Activity: 112
Merit: 10


View Profile
August 26, 2014, 02:22:31 AM
 #10354

Change to the Relay Network region closest to your p2pool node:
Code:
ExecStart=/bin/java -Xmx100m -jar /PATH/TO/RelayNodeClient.jar public.YOURRELAYREGION.relay.mattcorallo.com 127.0.0.1:8333

Shouldn't this be:

Code:
ExecStart=/bin/java -Xmx100m -jar /PATH/TO/RelayNodeClient.jar public.YOURRELAYREGION.relay.mattcorallo.com:8335

 Huh
No, the above is right running the jar version... I believe it connects to your local bitcoind instance first, and interacts with it, relaying out to his server on 8335/8336.  At least that's the way I am running it, and it seems to work.

BTW for those running it on the commandline, don't forget "nohup ... &" if you're not running in the same screen as when you started p2pool.
PatMan
Hero Member
*****
Offline Offline

Activity: 924
Merit: 1000


Watch out for the "Neg-Rep-Dogie-Police".....


View Profile WWW
August 26, 2014, 02:34:53 AM
 #10355

Right, didn't realise the jar version worked differently. So, from the command line my syntax would be:

Code:
nohup java -Xmx100m -jar /PATH/TO/RelayNodeClient.jar public.YOURRELAYREGION.relay.mattcorallo.com 127.0.0.1:8333 &

Is this correct? Don't I have to stipulate either port 8334 or 8335 anywhere?

Thanks  Smiley

"When one person is deluded it is called insanity - when many people are deluded it is called religion" - Robert M. Pirsig.  I don't want your coins, I want change.
Amazon UK BTC payment service - https://bitcointalk.org/index.php?topic=301229.0 - with FREE delivery!
http://www.ae911truth.org/ - http://rethink911.org/ - http://rememberbuilding7.org/
hamburgerhelper
Member
**
Offline Offline

Activity: 83
Merit: 10


View Profile
August 26, 2014, 02:35:48 AM
 #10356

kgb2mining is correct, the arguments to RelayNodeClient.jar include the host:port of your local bitcoind and the port for the Relay Network host is not required. The java application connects on 8336 only:

Code:
[root@p2pool ~]# netstat -a |grep relay
tcp6       0      0 p2pool.domain.:45203 do-nyc1.relay.matt:8336 ESTABLISHED

Glad I could help make p2pool that much more awesome! Kudos to Matt for reaching out to me and the thread to announce the upgrade, clear up our questions, and most importantly his massive improvement to the Bitcoin network.
kgb2mining
Member
**
Offline Offline

Activity: 112
Merit: 10


View Profile
August 26, 2014, 02:37:08 AM
 #10357

Right, didn't realise the jar version worked differently. So, from the command line my syntax would be:

Code:
nohup java -Xmx100m -jar /PATH/TO/RelayNodeClient.jar public.YOURRELAYREGION.relay.mattcorallo.com 127.0.0.1:8333 &

Is this correct?

Thanks  Smiley
Yep, that's exactly how I'm running it at the moment on my node (although I still need to add the xmx part).
Matt Corallo
Hero Member
*****
Offline Offline

Activity: 755
Merit: 515


View Profile
August 26, 2014, 02:39:31 AM
 #10358

Sorry for the issues (still working out the new protocol from last night...), but if you're using the jar, you should update to the latest version ("fuck it, ship it").

Bitcoin Core, rust-lightning, http://bitcoinfibre.org etc.
PGP ID: 07DF 3E57 A548 CCFB 7530  7091 89BB B866 3E2E65CE
hamburgerhelper
Member
**
Offline Offline

Activity: 83
Merit: 10


View Profile
August 26, 2014, 02:45:54 AM
 #10359

Ha!

Code:
Aug 25 22:44:32 p2pool.domain.name java[13614]: Aug 25, 2014 10:44:32 PM com.google.bitcoin.core.Peer processVersionMessage
Aug 25 22:44:32 p2pool.domain.name java[13614]: INFO: Connected to 127.0.0.1: version=70002, subVer='/Satoshi:0.9.2.1/', services=0...=317494
Aug 25 22:44:32 p2pool.domain.name java[13614]: Connected to local bitcoind!
Aug 25 22:44:32 p2pool.domain.name java[13614]: Connected to node with version: fuck it, ship it!
Aug 25 22:44:35 p2pool.domain.name java[13614]: 1409021075219: Received transaction bdece7858e2fdaa412f904dae818db7b7591f290056eae9...428ac7f
PatMan
Hero Member
*****
Offline Offline

Activity: 924
Merit: 1000


Watch out for the "Neg-Rep-Dogie-Police".....


View Profile WWW
August 26, 2014, 02:52:20 AM
 #10360

The java application connects on 8336 only:

Ahh, right. Got it  Smiley

Yep, that's exactly how I'm running it at the moment on my node (although I still need to add the xmx part).

Excellent, thanks for that  Smiley

Sorry for the issues (still working out the new protocol from last night...), but if you're using the jar, you should update to the latest version ("fuck it, ship it").

Great stuff - love the version name  Cheesy Cheesy

Thanks for the help everyone - job for tomorrow, I need sleeeeep  Wink

"When one person is deluded it is called insanity - when many people are deluded it is called religion" - Robert M. Pirsig.  I don't want your coins, I want change.
Amazon UK BTC payment service - https://bitcointalk.org/index.php?topic=301229.0 - with FREE delivery!
http://www.ae911truth.org/ - http://rethink911.org/ - http://rememberbuilding7.org/
Pages: « 1 ... 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 [518] 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 ... 814 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!