Pages:
Author

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

sr. member
Activity: 630
Merit: 257
If you do not submit a valid share within a 24 hour period, that wallet is no longer eligible for payout (even though it will say you would get a payout) ... buddy of mine found that out the hard way.
The p2pool sharechain pays out to the last 8640 shares. At an estimated 30 seconds per share, the sharechain pays out to any share found in the last 72 hours. This is an approximate of course as 30 seconds is only the target share time and it will vary with the pools hashrate variance.

Pulled from the web and this content is referenced all over the place...

The PPLNS payment system is not to be considered as the best for slow hash rate miners. To get payouts, you need to:
solve at least one hash every 24h hours which is higher than the p2pool share difficulty = gets at least one payout each day.
solve at least one hash within the window of the current block with a difficulty higher than the p2pool share difficulty = gets at least one payout each block.

After 24 hours of no mining, you get no more payout even if a block is found within the 3 days (8640 shares).

Like I said, buddy of mine discovered that the hard way and lost a sweet $200 payout.
hero member
Activity: 578
Merit: 501
...

Also, if I run my own node, do I need to have the full blockchain downloaded before mining? It seemed to take over a week to download it the last time I started to, so I gave up.

...
If your hardware is unable to download and validate the entirety of the blockchain within a 24 hour period, I would highly recommend that you download the blockchain via a bootstrap.dat file from a reliable source. I usually update my own bootstrap.dat backup every few months in case I need to do a fast reload.

...

If you do not submit a valid share within a 24 hour period, that wallet is no longer eligible for payout (even though it will say you would get a payout) ... buddy of mine found that out the hard way.
The p2pool sharechain pays out to the last 8640 shares. At an estimated 30 seconds per share, the sharechain pays out to any share found in the last 72 hours. This is an approximate of course as 30 seconds is only the target share time and it will vary with the pools hashrate variance.
sr. member
Activity: 630
Merit: 257
Now, if I were to change my payout address, would the predicted payout of the new address increase at the same rate as the old one decreases? I don't want to miss out on anything, and I  want to use a long-term, cold storage wallet instead of Coinbase.

Also, if I run my own node, do I need to have the full blockchain downloaded before mining? It seemed to take over a week to download it the last time I started to, so I gave up.

You must have the full blockchain in order to mine. If I remember right, p2pool will tell you that bitcoin is downloading blocks in console.

If you do not submit a valid share within a 24 hour period, that wallet is no longer eligible for payout (even though it will say you would get a payout) ... buddy of mine found that out the hard way.
newbie
Activity: 41
Merit: 0
Glad I got in on this block, as I missed out on the last one after mining for 16 days without a block, I changed pools, and got nothing. I really wanted to support decentralization, but I got worried.

Now, if I were to change my payout address, would the predicted payout of the new address increase at the same rate as the old one decreases? I don't want to miss out on anything, and I  want to use a long-term, cold storage wallet instead of Coinbase.

Also, if I run my own node, do I need to have the full blockchain downloaded before mining? It seemed to take over a week to download it the last time I started to, so I gave up.

Thanks,

Dave
hero member
Activity: 496
Merit: 500

 It's raining again !
 Blocks keep coming  Smiley
member
Activity: 107
Merit: 10
Pull request to make P2Pool compliant with SegWit: https://github.com/p2pool/p2pool/pull/327

Please help testing by mining on the Testnet.

veqtrus, I accidentally ran this on Mainnet.  I failed at comprehension and read that post completely wrong..   However; it seems to be running great, finding shares and accepting connections.
Is there any risk in continuing to run this PR on Mainnet?

Also, I was going to suggest but then noticed you already included PR #314 into #327.   Cool

If you manage to activate it on mainnet and there is some bug things might get messy. Also it doesn't help testing much since segwit isn't activated on mainnet.

Edit: Your problem is likely that you haven't connected to my testnet p2pool node so you are working on very low difficulty shares.
newbie
Activity: 58
Merit: 0
Pull request to make P2Pool compliant with SegWit: https://github.com/p2pool/p2pool/pull/327

Please help testing by mining on the Testnet.
I let it run for a bit to see what it would do;  I think I am getting high latency when getting work from bitcoind?  The workers would time out and fallover to elsewhere.  I switched back to the other version and will mess with it more on testnet in a bit.

Would you like me to PM you the log from the node?

https://i.imgur.com/g7yRNyy.png
https://i.imgur.com/vIVURBS.png
newbie
Activity: 58
Merit: 0
i WANNA eat some SQUID !!!

how are you mate & the p2pool gang ?, long time no see, i;ve been around but at other sections.

sad to see p2pool not doing to well, but i will always support p2pool, a big holla to the guys around.

lol!  I am doing okay, still hanging in there Smiley   How have you been?  Around on IRC at all?
The pool is fine, still chugging along as always.




Pull request to make P2Pool compliant with SegWit: https://github.com/p2pool/p2pool/pull/327

Please help testing by mining on the Testnet.

veqtrus, I accidentally ran this on Mainnet.  I failed at comprehension and read that post completely wrong..   However; it seems to be running great, finding shares and accepting connections.
Is there any risk in continuing to run this PR on Mainnet?

Also, I was going to suggest but then noticed you already included PR #314 into #327.   Cool

legendary
Activity: 1500
Merit: 1002
Mine Mine Mine
Pull request to make P2Pool compliant with SegWit: https://github.com/p2pool/p2pool/pull/327

Please help testing by mining on the Testnet.

will do

i WANNA eat some SQUID !!!

how are you mate & the p2pool gang ?, long time no see, i;ve been around but at other sections.

sad to see p2pool not doing to well, but i will always support p2pool, a big holla to the guys around.
newbie
Activity: 58
Merit: 0
Pull request to make P2Pool compliant with SegWit: https://github.com/p2pool/p2pool/pull/327

Please help testing by mining on the Testnet.

will do
member
Activity: 107
Merit: 10
Pull request to make P2Pool compliant with SegWit: https://github.com/p2pool/p2pool/pull/327

Please help testing by mining on the Testnet.
newbie
Activity: 15
Merit: 0
Wrong thread?
Why? Here discuss p2pool? I want to connect to your proxy node.
Sorry for my English, I use Google translator
hero member
Activity: 578
Merit: 501
Good day job seekers! Help please configure ckproxy. Do this:

Code:
sudo git clone https://bitbucket.org/ckolivas/ckpool.git
sudo apt-get update
sudo apt-get install build-essential libtool autoconf automake
cd ckpool
./autogen.sh
./configure --without-ckdb
make
sudo make install

# Next, create a file with the contents /usr/local/bin/notify.sh
#!/bin/bash
/usr/bin/notifier -s /opt

The daemon is started purse line add:
-blocknotify=/usr/local/bin/notify.sh

# Settings ckproxy.conf:
{
"proxy" :  [
{
"url" : "192.168.0.12:3332",
"auth" : "14po2GaS4NQNWte4DnxGyWsWSFGBckHDD8",
"pass" : "123"
}
],
"update_interval" : 30,
"serverurl" : [
"192.168.0.12:3334",
"127.0.0.1:3334"
],
"mindiff" : 1024,
"startdiff" : 1042,
"maxdiff" : 0,
"clientsvspeed" : false,
"loglevel" : 1,
"logdir" : "logs"
}
Comments from here on are ignored.

# Launch ckproxy
screen -dmS ckproxy ckpool -p -k -n ckproxy -c /root/ckpool/ckproxy.conf

Miner General Configuration
192.168.0.12:3334
14po2GaS4NQNWte4DnxGyWsWSFGBckHDD8
123

# Checking:
screen -r ckproxy

Proxy runs and runs, but DOA >= 50%.


What is my problem? Prompt and sundry. Thank you.
Wrong thread?
newbie
Activity: 15
Merit: 0
Good day job seekers! Help please configure ckproxy. Do this:

Code:
sudo git clone https://bitbucket.org/ckolivas/ckpool.git
sudo apt-get update
sudo apt-get install build-essential libtool autoconf automake
cd ckpool
./autogen.sh
./configure --without-ckdb
make
sudo make install

# Next, create a file with the contents /usr/local/bin/notify.sh
#!/bin/bash
/usr/bin/notifier -s /opt

The daemon is started purse line add:
-blocknotify=/usr/local/bin/notify.sh

# Settings ckproxy.conf:
{
"proxy" :  [
{
"url" : "192.168.0.12:3332",
"auth" : "14po2GaS4NQNWte4DnxGyWsWSFGBckHDD8",
"pass" : "123"
}
],
"update_interval" : 30,
"serverurl" : [
"192.168.0.12:3334",
"127.0.0.1:3334"
],
"mindiff" : 1024,
"startdiff" : 1042,
"maxdiff" : 0,
"clientsvspeed" : false,
"loglevel" : 1,
"logdir" : "logs"
}
Comments from here on are ignored.

# Launch ckproxy
screen -dmS ckproxy ckpool -p -k -n ckproxy -c /root/ckpool/ckproxy.conf

Miner General Configuration
192.168.0.12:3334
14po2GaS4NQNWte4DnxGyWsWSFGBckHDD8
123

# Checking:
screen -r ckproxy

Proxy runs and runs, but DOA >= 50%.


What is my problem? Prompt and sundry. Thank you.
hero member
Activity: 496
Merit: 500
Point your miner here!
All sexy girls mine at this pool
legendary
Activity: 1258
Merit: 1027
P2Pool will break once the first tx with witness arrives because of the different serialization format. Also P2Pool will produce invalid blocks once segwit activates.

So I would strongly suggest downgrading to 0.13.0.

I'm working on an upgrade.

Yea, I suspected as much, we have some time till activation, I also opened an issue on Github.

Is this connected to the fact that p2pool not find a block for more than a week?   Huh

No.
hero member
Activity: 496
Merit: 500
P2Pool will break once the first tx with witness arrives because of the different serialization format. Also P2Pool will produce invalid blocks once segwit activates.

So I would strongly suggest downgrading to 0.13.0.

I'm working on an upgrade.

Yea, I suspected as much, we have some time till activation, I also opened an issue on Github.

Is this connected to the fact that p2pool not find a block for more than a week?   Huh
legendary
Activity: 1258
Merit: 1027
P2Pool will break once the first tx with witness arrives because of the different serialization format. Also P2Pool will produce invalid blocks once segwit activates.

So I would strongly suggest downgrading to 0.13.0.

I'm working on an upgrade.

Yea, I suspected as much, we have some time till activation, I also opened an issue on Github.
member
Activity: 107
Merit: 10

P2Pool.org has been updated to Bitcoin Core 0.13.1

TBH I'm not completely sure there are no breaking changes for p2pool.

I went through the release notes, but there is a lot going on in this update.

https://lists.linuxfoundation.org/pipermail/bitcoin-core-dev/2016-October/000023.html

P2Pool will break once the first tx with witness arrives because of the different serialization format. Also P2Pool will produce invalid blocks once segwit activates.

So I would strongly suggest downgrading to 0.13.0.

I'm working on an upgrade.
legendary
Activity: 1258
Merit: 1027

P2Pool.org has been updated to Bitcoin Core 0.13.1

TBH I'm not completely sure there are no breaking changes for p2pool.

I went through the release notes, but there is a lot going on in this update.

https://lists.linuxfoundation.org/pipermail/bitcoin-core-dev/2016-October/000023.html
Pages:
Jump to: