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

sawa

legendary

Activity: 1308

Merit: 1011

Orphan again on jtoomimnet:
http://208.84.223.121:9334/static/share.html#00000000000000000093cc2a72c8ae2db421fb2316145ceba3f951b3296fc741

Code:

P2Pool > Share 296fc741

Parent: ab61f587

Far parent: 9730508f

Children: ed097354

Type: NewShare
Local data

Verified: true

Time first seen: Sat Nov 11 2017 10:31:35 GMT+0600 (1510374695.359508)

Peer first received from: 10.0.1.3,40084
Share data

Timestamp: Sat Nov 11 2017 10:30:51 GMT+0600 (1510374651)

Difficulty: 18679830.96432212

Minimum difficulty: 622660.3268996184

Payout address: 1GuDnEyYSE3Ra3pMar7311tx5poR5PGXR3

Donation amount: 0.00%

Last stale: null

Nonce: 2656979016

Desired version: 33

Absolute height: 4524535

Absolute work: 1.8942896648170373e+23
Block

Hash: 00000000000000000093cc2a72c8ae2db421fb2316145ceba3f951b3296fc741

jtoomim

hero member

Activity: 818

Merit: 1006

Quote from: Elphamyto on November 10, 2017, 12:49:40 AM

What size CPU and RAM do I need to run a node of your branch? Would it be feasible to run on a VPS server (i.e. one with the space necessary to hold the blockchain)?

The most recent version of 1mb_segwit needs about half as much RAM but a little more CPU than p2pool master.

If you're using pypy, you should probably have about 3-4 GB of available RAM and a 2.2 GHz Intel Core-based CPU or better. AMD Ryzen CPUs should work fine. Older AMD CPUs (e.g. A10 or A8) will need a lot more GHz, but if you have a 3.5 GHz older AMD CPU, that will probably also work fine. You might be able to get away with slower CPUs, but I can't promise anything.

If you're using python2.7, then you only need about 1.5 GB of available RAM but you might need a 3.0 GHz Intel Core i3 CPU.

I strongly recommend using pypy. That's much easier to do on Linux. Orphan rates will be lower and revenue will be higher if you use a fast CPU and if you use pypy.

Thread and core counts are basically irrelevant. GHz and IPC are king. This means a cheap desktop Core i3 CPU will be quite a bit better than a high-end server 16-core Xeon. The Xeon should still work fine, though.

Unfortunately, p2pool requires that the full node's blockchain be unpruned. It needs to access the genesis block for some reason; I haven't looked into the details on why. I recommend making the ~/.bitcoin/blocks/ directory a symlink to a cheap HDD and keeping the ~/.bitcoin/chainstate/ directory on an SSD. The chainstate is the UTXO database, and it needs to be read from and written to frequently and randomly when validating blocks. The blocks directory is just the raw block storage, and is accessed infrequently and sequentially, which makes it perfect for HDDs.

Elphamyto

member

Activity: 117

Merit: 16

What size CPU and RAM do I need to run a node of your branch? Would it be feasible to run on a VPS server (i.e. one with the space necessary to hold the blockchain)?

jtoomim

hero member

Activity: 818

Merit: 1006

Quote from: kzv on November 08, 2017, 06:14:20 AM

When i trying to mine with small hashrate, i got this errors:

The "Block stale detected" message is normal (though eliminated in jtoomimnet) and does not indicate a problem.

The "submitted share more than once" message is more unusual, but by itself does not itself indicate that things aren't working, nor does it give much of a hint how things would be failing if they were failing. My only guess for why you might be getting that is if the difficulty set by your node is too low. It's also possible that your mining hardware is just buggy or your network is buggy/congested/laggy or your node's CPU is getting saturated.

Quote from: chasaamm on November 07, 2017, 11:36:50 AM

And also i don't know if jtoomimnet has a block finding reward like p2pool.org has!

It currently has the same 0.5% bonus that mainnet has. I might want to increase that in the future, but for now it's the same.

Quote from: chasaamm on November 05, 2017, 02:01:48 PM

Is the forrestvnet not well configured
or is just a big blow of bad luck?

With mainnet's current hashrate of 760 Th/s, it is expected to find one block every 95 days or so. Mainnet last found a block 85 days ago on August 15, 2017, so this doesn't even qualify as bad luck. With this hashrate, "bad luck" would mean not finding a block for about a year.

jtoomim

hero member

Activity: 818

Merit: 1006

Quote from: windpath on November 08, 2017, 12:45:12 PM

@jtoomim given today's news, can we now get back on the same sharechain?

I don't see how that's relevant. The absence of my code in the main repo was never about 2x; it was about compatibility issueswith altcoins.

windpath

legendary

Activity: 1258

Merit: 1027

@jtoomim given today's news, can we now get back on the same sharechain?

https://lists.linuxfoundation.org/pipermail/bitcoin-segwit2x/2017-November/000685.html

kzv

legendary

Activity: 1722

Merit: 1285

OpenTrade - Open Source Cryptocurrency Exchange

Hi
Can someone help me?

I'm trying to configure p2pool for my fork. I have changed two files
1. https://github.com/3s3s/p2pool/blame/master/p2pool/networks/bitcoin.py
2. https://github.com/3s3s/p2pool/blob/master/p2pool/bitcoin/networks/bitcoin.py

Yesterday I ran a pool on three servers and all worked wery well... I connected to them and found three blocks http://mc-pool.multicoins.org:39332/static/

Today I tried to mine again but now I can not find any share (((

When i trying to mine with small hashrate, i got this errors:

Code:

2017-11-08 10:46:58.082334 P2Pool: 526 shares in chain (527 verified/527 total) Peers: 2 (2 incoming)
   2017-11-08 10:46:58.082482 Local: 178GH/s in last 10.0 minutes Local dead on arrival: ~0.0% (0-14%) Expected time to share: 52.1 seconds
   2017-11-08 10:46:58.082511 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: (0.0000)=0.0000 MC
   2017-11-08 10:46:58.082546 Pool: 7424GH/s Stale rate: 4.0% Expected time to block: 5.8 hours
   2017-11-08 10:46:59.635201 Punishing share for 'Block-stale detected! height(3ca685b68be3bcff76a05512b05458cd5fc0d3f7bfef852e6cb) < height(14c3dde56560a96d09e3115e20ef8f856c3883767b62db8d36) or 1a01da8c != 1976ae34'! Jumping from b48805c5 to 80de13ac!
   2017-11-08 10:46:59.635564 Punishing share for 'Block-stale detected! height(3ca685b68be3bcff76a05512b05458cd5fc0d3f7bfef852e6cb) < height(14c3dde56560a96d09e3115e20ef8f856c3883767b62db8d36) or 1a01da8c != 1976ae34'! Jumping from b48805c5 to 80de13ac!
   2017-11-08 10:47:00.727749 Handshake timed out, disconnecting from 83.148.207.82:9333
   2017-11-08 10:47:04.636909 Punishing share for 'Block-stale detected! height(3ca685b68be3bcff76a05512b05458cd5fc0d3f7bfef852e6cb) < height(14c3dde56560a96d09e3115e20ef8f856c3883767b62db8d36) or 1a01da8c != 1976ae34'! Jumping from b48805c5 to 80de13ac!
   2017-11-08 10:47:04.637263 Punishing share for 'Block-stale detected! height(3ca685b68be3bcff76a05512b05458cd5fc0d3f7bfef852e6cb) < height(14c3dde56560a96d09e3115e20ef8f856c3883767b62db8d36) or 1a01da8c != 1976ae34'! Jumping from b48805c5 to 80de13ac!

With high hashrate got this errors:

Code:

2017-11-08 10:51:44.570448 P2Pool: 527 shares in chain (531 verified/531 total) Peers: 2 (0 incoming)
   2017-11-08 10:51:44.570603 Local: 5055GH/s in last 1.9 minutes Local dead on arrival: ~0.0% (0-3%) Expected time to share: 1.8 seconds
   2017-11-08 10:51:44.570662 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: (0.0000)=0.0000 MC
   2017-11-08 10:51:44.570721 Pool: 7259GH/s Stale rate: 4.0% Expected time to block: 5.9 hours
   2017-11-08 10:51:44.867776 > Worker MM3Lomzqspu7tqdCME4h4mm21RggLwKFvb submitted share more than once!
   2017-11-08 10:51:45.007366 > Worker MM3Lomzqspu7tqdCME4h4mm21RggLwKFvb submitted share more than once!

chasaamm

newbie

Activity: 19

Merit: 0

Quote from: Xantus on November 07, 2017, 03:38:38 AM

Quote from: chasaamm on November 05, 2017, 02:01:48 PM

Is the forrestvnet not well configured
or is just a big blow of bad luck?

as i know is it not as efficient as Jtoomim, and so less hash power behind.

Could be!
But jtoomimnet doesn't have a cool stats frontpage like p2pool.org has!
And i like to be well informed !
And also i don't know if jtoomimnet has a block finding reward like p2pool.org has!

Nikoloz

sr. member

Activity: 284

Merit: 252

Quote from: jtoomim on October 31, 2017, 09:48:42 PM

Quote from: davidadrake on October 31, 2017, 01:34:40 PM

Sure hope jtoomim's fork finds a block soon, or I'm gonna have to bail. I'm trying to hang in there, but I wish we had a few more PH to bring down the expected time a little.

We will have about 3x as much hashrate in December.

to increase hashrate of the pool-it is necessary to invite Jtoomim.Jonathan , you as Santa for Christmas will arrive, or before? Watched you on YouTube, great job,great everything you've got. You may want to connect power and make blocks until 25 November?

Xantus

newbie

Activity: 43

Merit: 0

Quote from: chasaamm on November 05, 2017, 02:01:48 PM

Is the forrestvnet not well configured
or is just a big blow of bad luck?

as i know is it not as efficient as Jtoomim, and so less hash power behind.
and by the way, bad luck we do have on jtoomim cain also :-(

but other question :
Wath happen at the 25. November ? does any P2Pool version switch over to 2MB Block sitze ?

chasaamm

newbie

Activity: 19

Merit: 0

Is the forrestvnet not well configured
or is just a big blow of bad luck?

Nikoloz

sr. member

Activity: 284

Merit: 252

Quote from: jtoomim on October 31, 2017, 09:48:42 PM

Quote from: davidadrake on October 31, 2017, 01:34:40 PM

Sure hope jtoomim's fork finds a block soon, or I'm gonna have to bail. I'm trying to hang in there, but I wish we had a few more PH to bring down the expected time a little.

We will have about 3x as much hashrate in December.

Is it possible to connect the power at your command for maximum effect ?

frodocooper

sr. member

Activity: 351

Merit: 410

Quote from: Kiefff on November 04, 2017, 01:07:21 PM

Is there a way to setup a password for miners? Keeping the pool private.

No. But you can do one of two things, or both:

1. Set a fee of 100% with the --fee 100 flag when you start your P2Pool node. This would discourage others from mining at your node, since all of their mining proceeds would be going to you. Be sure to also set a valid Bitcoin address that belongs to you, with the -a flag.

2. Set a custom worker port with the -w flag when you start your P2Pool node. Most, if not all, P2Pool node scanners do not detect nodes with custom worker ports — i.e., ports other than P2Pool's default port 9332. Setting a custom worker port therefore prevents others from finding your node using such scanners.

Kiefff

newbie

Activity: 32

Merit: 0

Is there a way to setup a password for miners? Keeping the pool private.

frodocooper

sr. member

Activity: 351

Merit: 410

Quote from: jtoomim on October 31, 2017, 09:48:42 PM

We will have about 3x as much hashrate in December.

But on the 2x fork, I presume.

Is jtoomimnet still on track to automatically split into separate sharechains during the 2x hard fork?

jtoomim

hero member

Activity: 818

Merit: 1006

Quote from: davidadrake on October 31, 2017, 01:34:40 PM

Sure hope jtoomim's fork finds a block soon, or I'm gonna have to bail. I'm trying to hang in there, but I wish we had a few more PH to bring down the expected time a little.

We will have about 3x as much hashrate in December.

Kiefff

newbie

Activity: 32

Merit: 0

Quote from: frodocooper on October 30, 2017, 10:26:35 PM

Quote from: Kiefff on October 30, 2017, 12:17:00 PM

Hey all. Recently got p2pool working with litecoin. Pool was working for fine about 6 hours and now will not connect to any p2pool peers? I was connected to 6 since starting, now 0. Do I need to manually add other p2pool nodes?

No.

It could be a firewall issue. Make sure that your firewall allows incoming connections over port 9338, which is Litecoin P2Pool's default P2P port.

If your node is behind a NAT router, make sure that TCP port forwarding is enabled on the router, and that port 9338 is forwarded to your P2Pool node.

I'm assuming that you've already followed these instructions when you set up your node.

You may also try using sawa's P2Pool for Litecoin instead. Sawa's fork contains fixes and enhancements that improve compatibility with Litecoin.

If these do not resolve your issue, then please post here your node's logs — located at /litecoin/log in your P2Pool data directory — so that we may have a closer look at what's going on when your node starts dropping connections. A snippet of your node's terminal output, of around the time your node starts dropping connections, may also be of help here.

Using sawas p2pool is working quite well so far. Thanks for the info!

Xantus

newbie

Activity: 43

Merit: 0

seams p2pool has a litlle bit bad luke this time ... Undecided

davidadrake

newbie

Activity: 41

Merit: 0

Sure hope jtoomim's fork finds a block soon, or I'm gonna have to bail. I'm trying to hang in there, but I wish we had a few more PH to bring down the expected time a little. I know that if I leave, the second my shares drop off, it'll solve a block, and I will have wasted a month with nothing but warm fuzzies to show for it.

frodocooper

sr. member

Activity: 351

Merit: 410

Quote from: Kiefff on October 30, 2017, 12:17:00 PM

Hey all. Recently got p2pool working with litecoin. Pool was working for fine about 6 hours and now will not connect to any p2pool peers? I was connected to 6 since starting, now 0. Do I need to manually add other p2pool nodes?

No.

It could be a firewall issue. Make sure that your firewall allows incoming connections over port 9338, which is Litecoin P2Pool's default P2P port.

If your node is behind a NAT router, make sure that TCP port forwarding is enabled on the router, and that port 9338 is forwarded to your P2Pool node.

I'm assuming that you've already followed these instructions when you set up your node.

You may also try using sawa's P2Pool for Litecoin instead. Sawa's fork contains fixes and enhancements that improve compatibility with Litecoin.

If these do not resolve your issue, then please post here your node's logs — located at /litecoin/log in your P2Pool data directory — so that we may have a closer look at what's going on when your node starts dropping connections. A snippet of your node's terminal output, of around the time your node starts dropping connections, may also be of help here.

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