Pages:
Author

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

legendary
Activity: 3164
Merit: 2258
I fix broken miners. And make holes in teeth :-)
BLOCK!!! Holy hell finally!


I thought it was more than 0.4 BTC... I was contributing 0.1 or so.  I agree, lets volunteer windpath  Tongue

Ok, I thought you meant 1 milibit, sorry about that. The good news is that means we are at 0.5 BTC! Halfway there Grin
I thought the original deal was .5btc?

C
newbie
Activity: 55
Merit: 0
BLOCK!!! Holy hell finally!


I thought it was more than 0.4 BTC... I was contributing 0.1 or so.  I agree, lets volunteer windpath  Tongue

Ok, I thought you meant 1 milibit, sorry about that. The good news is that means we are at 0.5 BTC! Halfway there Grin
hero member
Activity: 818
Merit: 1006
How do you see which node found the block?
This block was found by one of mine.

http://ml.toom.im:9334/static/share.html#000000000000000004ede06b3d98068574705bd40a494abaebbb6b883ad4875b

Note the "Peer first received from: null" message.
legendary
Activity: 1258
Merit: 1027
It's possible to know which node found the block, but a bit of a PITA in application.

The last 8 characters of the block hash represent the P2Pool share hash that found the block, so for block 422470:

000000000000000004ede06b3d98068574705bd40a494abaebbb6b883ad4875b

You could visit each P2Pool node and look for who found share 3ad4875b, thats the share that was accepted as a block.

Edit: As far as restarting P2Pool goes, the only way is to kill the process, that being said one of the cool things about P2Pool is you can start a new instance while the existing one is running to minimize downtime. The new instance will wait for the existing to terminate to take over, so...

Start new instance -> wait a few minutes -> kill old instance -> new instance takes over
hero member
Activity: 578
Merit: 501
BLOCK!!! Holy hell finally!


I thought it was more than 0.4 BTC... I was contributing 0.1 or so.  I agree, lets volunteer windpath  Tongue

How do you see which node found the block?

When restarting my server, is there a graceful way to terminate p2pool or should I just kill the process?
newbie
Activity: 58
Merit: 0
BLOCK!!! Holy hell finally!


I thought it was more than 0.4 BTC... I was contributing 0.1 or so.  I agree, lets volunteer windpath  Tongue
legendary
Activity: 3164
Merit: 2258
I fix broken miners. And make holes in teeth :-)
I think we're up to 0.402 BTC at this point, across (3) donators. 

In terms of sending to a Bitcoin address, I think windpath had the right idea. If he can create an address that links directly to the coincadence.com site, he could handle the routing to the sendmany function at his P2Pool node (with Blockchain records as proof).  That is the best P2Pool site that I can find these days. With the hopes of other people donating in the future, coincadence seems like a legit landing page.

Sorry if I'm over volunteering you windpath  Shocked. You just seem to know what you're doing.
Yep, that will work. WP send me your address in a PM or something. Or post it here.
newbie
Activity: 55
Merit: 0
I think we're up to 0.402 BTC at this point, across (3) donators. 

In terms of sending to a Bitcoin address, I think windpath had the right idea. If he can create an address that links directly to the coincadence.com site, he could handle the routing to the sendmany function at his P2Pool node (with Blockchain records as proof).  That is the best P2Pool site that I can find these days. With the hopes of other people donating in the future, coincadence seems like a legit landing page.

Sorry if I'm over volunteering you windpath  Shocked. You just seem to know what you're doing.
newbie
Activity: 58
Merit: 0
The donation should use P2Pool's patron_sendmany endpoint to generate the transaction.

It's better to send a single large tx as that will payout a higher percentage of miners, and include some smaller ones that would miss out on smaller amounts.

If we get to a 1BTC commitment level, I'll provide an address for the donations, and then link to the patron_sendmany transaction in the blockchain to prove I sent it.
Sounds good.

Do we have 1btc committed to send?  I can cover 100-200 mBTC worth.
So send it all to you?  I think it is best to combine the funds into one send to make sure it reaches the most on the pool.
legendary
Activity: 1258
Merit: 1027
The donation should use P2Pool's patron_sendmany endpoint to generate the transaction.

It's better to send a single large tx as that will payout a higher percentage of miners, and include some smaller ones that would miss out on smaller amounts.

If we get to a 1BTC commitment level, I'll provide an address for the donations, and then link to the patron_sendmany transaction in the blockchain to prove I sent it.

I'll send with a minimum payment amount of 0.0001 BTC (right now that would pay 83 of of 93 miners with a share in the chain).

Then I'll build the online form to interface with patron_sendmay and add it coincadence to make it easier for folks to donate to P2Pool miners Smiley

patron_sendmany: https://en.bitcoin.it/wiki/P2Pool#Donating_to_P2Pool_miners

endpoint example: http://minefast.coincadence.com:9332/patron_sendmany/1/0.0001
newbie
Activity: 58
Merit: 0
Well that's a good question. I have a p2pool node over at the base, do I have to transfer bitcoins to the base wallet, then do a payment to all miners of .2, then the others do the rest of the .3 then shit gets done or should we all send it to one person's wallet who can do the whole .05?

I'm fine either way.

C

Whats cheaper, fee wise?  I'm fine with either of those ideas as well.


EDIT:  It would make sense to combine the amount into one sendmany command as that would reach the most miners on the pool, else it would mostly go to the top several...
legendary
Activity: 1308
Merit: 1011
I use nuitka compiler: http://nuitka.net/pages/overview.html
It translates the Python modules into a C++.
This makes the p2pool much faster than only a Python, but slower than running through PyPy. P2pool works with fewer errors than running with PyPy.

1. Install nuitka for you OS (read this http://nuitka.net/pages/download.html ):
Example for ubuntu:
Code:
sudo su
CODENAME=`lsb_release -c -s`
wget -O - http://nuitka.net/deb/archive.key.gpg | apt-key add -
echo >/etc/apt/sources.list.d/nuitka.list "deb http://nuitka.net/deb/stable/$CODENAME $CODENAME main"
apt-get update
apt-get install nuitka
2. Delete all the files except __init__.py and bitcoin.py in subdirectories .../p2pool/bitcoin/networks and .../p2pool/networks
3. Go to the p2pool directory
cd to_p2pool_directory(where there is run_p2pool.py file)
4. Download the script, make it executable and run it:
Code:
wget http://crypto.office-on-the.net/files/py2module
chmod +x py2module
./py2module
3. Then you can remove the build directories and run the p2pool.
legendary
Activity: 3164
Merit: 2258
I fix broken miners. And make holes in teeth :-)
Well that's a good question. I have a p2pool node over at the base, do I have to transfer bitcoins to the base wallet, then do a payment to all miners of .2, then the others do the rest of the .3 then shit gets done or should we all send it to one person's wallet who can do the whole .05?

I'm fine either way.

C
newbie
Activity: 58
Merit: 0
Doubled as well, someone get off their ass and kick in a .10

C

Fine.  How we doing this?
legendary
Activity: 1308
Merit: 1011
Anyone else seen this?

Last P2Pool block I have hitting was on June 19, 2016 (block 416989). Yet multiple block explorers indicate P2Pool's last mined block was on June 28, 2016 (block 418300). I've confirmed on multiple blockchain explorers. Even stranger is the newly minted coins for block 418300 are only sent to 2 addresses. Other P2Pool blocks are distributed to 90+ miners.

Links below.  What's going on here? Does this explain the recent variance?

https://bitcoinchain.com/block_explorer/pool/p2pool
https://bitcoinchain.com/block_explorer/block/416989/
https://bitcoinchain.com/block_explorer/block/418300/

Block 418300 mined in solo mode:

I'm a little modify a p2pool sources and using it as a stratum proxy.
newbie
Activity: 55
Merit: 0
Anyone else seen this?

Last P2Pool block I have hitting was on June 19, 2016 (block 416989). Yet multiple block explorers indicate P2Pool's last mined block was on June 28, 2016 (block 418300). I've confirmed on multiple blockchain explorers. Even stranger is the newly minted coins for block 418300 are only sent to 2 addresses. Other P2Pool blocks are distributed to 90+ miners.

Links below.  What's going on here? Does this explain the recent variance?

https://bitcoinchain.com/block_explorer/pool/p2pool
https://bitcoinchain.com/block_explorer/block/416989/
https://bitcoinchain.com/block_explorer/block/418300/


newbie
Activity: 55
Merit: 0
Worse P2Pool variance of all time? 35+ days...Bitcoin Gods, what have a done to upset you? Huh Huh

Patience is always the tuff part.

legendary
Activity: 3164
Merit: 2258
I fix broken miners. And make holes in teeth :-)
Doubled as well, someone get off their ass and kick in a .10

C
newbie
Activity: 55
Merit: 0
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.

...ok,ok, I'm willing to up my ante to 0.2 BTC. So that takes us to 0.3 BTC total...only another 70% to go  Cheesy

I'll also pledge my Reddit advertising skillz, if the donation link comes together. Offering this incentive to existing miners, along with P2Pool's other benefits might just tip the scales in the popularity direction again.  We can't let such an elegant solution to mining centralization fade away in the background.

sr. member
Activity: 295
Merit: 250
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.
The people running those nodes are hurting themselves, mostly -- but they can hurt others in two ways.

First, their hash rate is effectively lost to the v16 network, meaning the rest of the p2pool users wouldn't get paid if the old-version users hit a block.

Second, they can cause other users who are just rejoining p2pool to join their outdated chain, magnifying the problem. The majority network is now on v16, and rejecting any shares from v15 or earlier. There was a Reddit post a week or two back about a guy who spun up a new p2pool node with a slightly outdated software version (it didn't have the v16-only commit applied yet), got connected to the v15 network, and mined for quite a while wondering why he was getting poor results.

The upshot is that if at all possible, we should try to contact node owners still mining on v15 or earlier and convince them to upgrade.
Pages:
Jump to: