Pages:
Author

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

hero member
Activity: 578
Merit: 501
How big of an impact is it that there are several nodes out there still running on versions older than 16? After looking at a few different node scanners, I found nodes running versions as old as version 13 and some of these nodes have hash rates as high as 100TH/s.
legendary
Activity: 3164
Merit: 2258
I fix broken miners. And make holes in teeth :-)
Count me in for 0.1 BTC! Cheesy
Anybody else want to join?

Thanks Coin Cadence! Love your site.
Sure, I'll pledge .1 BTC. Let's get .3 more and do this.
hero member
Activity: 578
Merit: 501
Was not long blocks (((
Who can restart the main node !?
After the latest updates no block (((

I am not really sure what you are asking.
newbie
Activity: 3
Merit: 0
Was not long blocks (((
Who can restart the main node !?
After the latest updates no block (((
newbie
Activity: 55
Merit: 0
Count me in for 0.1 BTC! Cheesy
Anybody else want to join?

Thanks Coin Cadence! Love your site.
legendary
Activity: 1258
Merit: 1027
...

Maybe we just need to make that a possibility for Bitcoin donations. Give the average Joe (a non-miner) a chance to donate to P2Pool and have that evenly distributed among the miners, this improving decentralization for everyone?

...


The ability to fairly do what you are talking about already exists in the patron_sendmany endpoint, you can read about it here: https://en.bitcoin.it/wiki/P2Pool#Donating_to_P2Pool_miners

Here is an example output of the endpoint:  http://minefast.coincadence.com:9332/patron_sendmany/10

It can be called from any P2Pool node.

There used to be a web based interface that set up a donation address and the transaction, but it's been gone for a while.

If someone was to commit to a 1 BTC donation to patron_sendmany I'll add a new web based version to CoinCadence
newbie
Activity: 55
Merit: 0
You're spot on - Patience with the variance of P2Pool is always he tricky part.

Here's what has always surprised me: Almost everyone in the US is against the centralization of Bitcoin, especially when it comes to mining.  I'm in full agreement. It just surprises me the Bitcoin community will donate thousands of $$$ to support hosted mining of Classic vs. Core blocks. I don't have the link handy, but there are still thousands of donated dollars hosting mining of classic nodes. Wouldn't donation of these $$ directly to P2Pool make a much bigger impact? I.E. - Switch 2 P2Pool and the financial incentive is there.

Maybe we just need to make that a possibility for Bitcoin donations. Give the average Joe (a non-miner) a chance to donate to P2Pool and have that evenly distributed among the miners, this improving decentralization for everyone?

Yup...I'm still a newbie, so go easy on me. Just trying to contribute to the awesome community you studs have created!
hero member
Activity: 818
Merit: 1006
I've being out of the loop for a little while what's being going on just started mining again now being going 2 weeks and not one single btc last time it was every 4-5 days unless I've mucked something up again
P2pool is pretty small nowadays. Due to the size, it's expected for p2pool to find one block every two weeks on average. Sometimes we'll get multiple blocks in a single week, and sometimes we'll go a month or longer in between blocks. Unfortunately, you have to either be patient or switch pools.
legendary
Activity: 1258
Merit: 1027
Will we get one last block at 25 BTC?  ✨ Here's to hoping 👍🏻

Luck has been crap lately, but the only thing I know that holds true about luck is that it's bound to change Smiley

Happy halving P2Poolers!
newbie
Activity: 30
Merit: 0
I've being out of the loop for a little while what's being going on just started mining again now being going 2 weeks and not one single btc last time it was every 4-5 days unless I've mucked something up again
newbie
Activity: 55
Merit: 0
Will we get one last block at 25 BTC?  ✨ Here's to hoping 👍🏻
full member
Activity: 213
Merit: 100
Nice im going to throw some hash rate towards p2pool!
Glad this hump is over. Now hope we can gain back some of that lost hashrate.

73.182.147.206:9332

Above is my node. I'll try keeping this up for people who may want to use it.

I'm In Hartford, Connecticut.
Donation node to p2pool with 6TH.     Hope others decide p2pool is worth saving.

Miner General Configuration

URL:  73.182.147.206:9332
Worker: YOUR BITCOIN ADDRESS
PASSWORD:ANY

View stats with link above
This can be used as a backup or for mining till you get your node up.



newbie
Activity: 58
Merit: 0
We need an automatic implementation of this function as currently it seems to be manual...?  There should be a way to support both versions of peers until majority has reached and maintained the consensus threshold, and then the older peers are banned from the network and the new version is fully enforced.  This would prevent what is occurring and seems to occur every hardfork. :s

https://github.com/p2pool/p2pool/pull/314

Awesome work. That was fast!  I'll test out that PR Smiley
hero member
Activity: 578
Merit: 501
I am trying to get p2pool working on my computer. I am having the following problem:

When I load the user interface I get these errors:



My user interface also looks like this:

https://s31.postimg.org/mfpyr77wb/p2pool_problem_2.png

1) I have NO CLUE how to use python. The installation instructions are completely useless as far as I am concerned. The setup guide obviously assumes I know more about python/p2pool than I know.

2) the instructions need to list an exact file name so that when I go to download the files needed, I download the correct file

3) the install instructions are not clear enough for some one that is not a developer to get p2pool working

Getting p2pool working is nothing short of reinforcing my believe that linux users have an ego they need to stroke by making things hard to use.

You guys need to make it you're number 1 priority to make the install of p2pool 1 click. thanks for wasting my time...

You should be using git to clone into both bitcoin and p2pool. You should not need to do anything special with python other than running the script. From start to finish, I used the following on a clean install of debian linux:

Code:
//as root type
apt-get install sudo
adduser YOURUSERNAME sudo

//login to YOURUSERNAME
sudo apt-get install git
sudo apt-get install build-essential libtool autotools-dev automake pkg-config libssl-dev libevent-dev bsdmainutils
sudo apt-get install libboost-all-dev
sudo apt-get install libminiupnpc-dev

git clone https://github.com/bitcoin/bitcoin

cd bitcoin
./autogen.sh
./configure --disable-wallet --without-gui
make
sudo make install

bitcoind -daemon

sudo apt-get install python-twisted python-argparse
sudo apt-get install curl
sudo apt-get install ncurses-dev
sudo apt-get install libffi-dev

cd ~/

git clone https://github.com/forrestv/p2pool

cd p2pool
make

python ~/p2pool/run_p2pool.py --give-author 0 --fee 0 --address YOURBITCOINPOOLADDRESSHERE

You should probably also make changes to your bitcoin.conf.

e.g.

daemon=1
server=1
rpcuser=bitcoinrpc
rpcpassword=YOURRPCPASSWORD
rpcallowip=127.0.0.1
rpcport=8332
blockmaxsize=1000000
mintxfee=0.00001
minrelaytxfee=0.00001
newbie
Activity: 17
Merit: 0
I am trying to get p2pool working on my computer. I am having the following problem:

When I load the user interface I get these errors:

https://s31.postimg.org/5gbhvmowr/p2pool_problem_1.png

My user interface also looks like this:

https://s31.postimg.org/mfpyr77wb/p2pool_problem_2.png

1) I have NO CLUE how to use python. The installation instructions are completely useless as far as I am concerned. The setup guide obviously assumes I know more about python/p2pool than I know.

2) the instructions need to list an exact file name so that when I go to download the files needed, I download the correct file

3) the install instructions are not clear enough for some one that is not a developer to get p2pool working

Getting p2pool working is nothing short of reinforcing my believe that linux users have an ego they need to stroke by making things hard to use.

You guys need to make it you're number 1 priority to make the install of p2pool 1 click. thanks for wasting my time...

newbie
Activity: 55
Merit: 0
Thanks @squidicuz  Wink Smiley
member
Activity: 107
Merit: 10
We need an automatic implementation of this function as currently it seems to be manual...?  There should be a way to support both versions of peers until majority has reached and maintained the consensus threshold, and then the older peers are banned from the network and the new version is fully enforced.  This would prevent what is occurring and seems to occur every hardfork. :s

https://github.com/p2pool/p2pool/pull/314
newbie
Activity: 58
Merit: 0
Is it possible we have a bona fide fork in the p2pool share chain? That is, someone generated a share that was incompatible with v16, causing v16 nodes to reject it and fork away. That v15 chain continued building, and is the reason we're seeing massive influx of invalid shares on v16 nodes. New pools starting up now have a (small) chance of picking up the old v15 chain, which causes the v15 shares to get propagated to the network. As independent nodes connect to both v15 and v16 nodes, the poor performance we see starts to happen - massive lumps of shares appear, requiring huge CPU time to process, since they don't integrate neatly with the existing share chain. In the end, the incompatible shares are rejected, but they still take time to handle. (To be clear, this is just a guess at what's going on in terms of the big picture. Jtoomim seems to have a handle on the technical aspects of why the performance is poor.)

That is sort of pretty much what is going on..  The current upgrade process is that once the majority of the network is upgraded to the next version, a new version is released that bans the old peers and restores performance to the majority network.  Currently the remaining old version peers are spamming the majority network with invalid shares.

We need an automatic implementation of this function as currently it seems to be manual...?  There should be a way to support both versions of peers until majority has reached and maintained the consensus threshold, and then the older peers are banned from the network and the new version is fully enforced.  This would prevent what is occurring and seems to occur every hardfork. :s


The fix has been merged into master.  Upgrade to the latest git version to restore performance to your node.
sr. member
Activity: 295
Merit: 250
Is it possible we have a bona fide fork in the p2pool share chain? That is, someone generated a share that was incompatible with v16, causing v16 nodes to reject it and fork away. That v15 chain continued building, and is the reason we're seeing massive influx of invalid shares on v16 nodes. New pools starting up now have a (small) chance of picking up the old v15 chain, which causes the v15 shares to get propagated to the network. As independent nodes connect to both v15 and v16 nodes, the poor performance we see starts to happen - massive lumps of shares appear, requiring huge CPU time to process, since they don't integrate neatly with the existing share chain. In the end, the incompatible shares are rejected, but they still take time to handle. (To be clear, this is just a guess at what's going on in terms of the big picture. Jtoomim seems to have a handle on the technical aspects of why the performance is poor.)
hero member
Activity: 818
Merit: 1006
- P2Pool.in: Downloaded Windows binary version 16.0, installs and runs fine. P2Pool Pool Rate: approx. 140 TH/s
- Github Master Branch: Downloaded and installed master branch code from Github P2Pool. Includes 16.0 update (I assume) P2Pool Pool Rate: approx. 900 TH/s.
I don't use Windows for my mining servers, so I have no familiarity with the p2pool.in binaries. The github master branch is the one true source for p2pool code, so I would recommend using that.

I don't see why the different software distributions would connect you to a different network with a different hashrate. It's possible that you just weren't able to acquire enough peers the first time you tried, and so you didn't get to see the whole network.
Pages:
Jump to: