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

[windpath]

Has anyone looked into using proxypool as a solution for smaller miners?

https://github.com/erkmos/proxypool
https://github.com/dogestreet/proxypool

proxypool  is a pool server that splits work from an upstream pool server and redistributes them to its miners, handling both share submission and sharelogging for it's patrons.

It was used for a while on http://doge.st/ with the dogecoin p2pool. I do not know the reasons why they shutdown.

I would investigate further but my time is limited :/

I have not tested it, but if I remember right, a hundred or so pages back it was proven incompatible.

I made a proxy that works with p2pool.  It needs some polishing before I release it though.  Also it really doesn't "help" with small miners ... you still need to hit the sharesize to get a share.

M

I would think what we would need to make a proxy work is some type of automated escrow. I.E. many small miners mine through a proxy, the proxy tracks the individual miner work and submits the combined work to P2Pool under a single address. A payout threshold would be set (say .005 BTC to start), and the proxy would issue payouts as the individual miner reward crossed the threshold.

Now where can I find a trust-less automated escrow system that can be integrated with a proxy?

[1713585294]

1713585294

[1713585294]

1713585294

[1713585294]

1713585294

[1713585294]

1713585294

[1713585294]

1713585294

[PatMan]

Oh? A proxy that will allow users with incompatible hardware to mine on p2pool?

This sounds interesting......

[CartmanSPC]

I would think what we would need to make a proxy work is some type of automated escrow. I.E. many small miners mine through a proxy, the proxy tracks the individual miner work and submits the combined work to P2Pool under a single address. A payout threshold would be set (say .005 BTC to start), and the proxy would issue payouts as the individual miner reward crossed the threshold.

That is similar to how this "proxypool" works but it keeps a local DB of the payouts. It also changes the payout method to miners using it to:

a Capped PPS with Recent Back Pay payout system, requires no registration, and threshold autopayout.

I am tempted to see if I can get it to work

[mdude77]

Oh? A proxy that will allow users with incompatible hardware to mine on p2pool?

This sounds interesting......

I didn't say that.  From what I've seen so far, with my limited hardware, is the incompatibilities are caused by the 30 second job restart.  A proxy won't fix that.  A proxy can help by forcing through the job id, but that'll only help if the hash is a block.  If it's a legit share, it'll get rejected because the rest of the pool is on the next job id.

M

EDIT: A proxy can also help if the hardware is choking on the protocol "language" from p2pool.  My proxy is stratum only .. if there's any "getwork" hardware out there, it won't work.

[mdude77]

I would think what we would need to make a proxy work is some type of automated escrow. I.E. many small miners mine through a proxy, the proxy tracks the individual miner work and submits the combined work to P2Pool under a single address. A payout threshold would be set (say .005 BTC to start), and the proxy would issue payouts as the individual miner reward crossed the threshold.

Now where can I find a trust-less automated escrow system that can be integrated with a proxy?

Someone tried that with p2poolmining, I believe.  It worked great until he was hacked and his account was emptied.

Basically you need a mini p2pool that points to the main p2pool instead of bitcoin.  How to get all those addresses in that main p2pool share, though, would be a challenge.

M

[Matt Corallo]

Hi Matt,

I noticed I had a couple of disconnects on my internet yesterday, and that the relay app seemed not to be able to reconnect again, even though netstat showed it as established, the scrolling had stopped completely. It was fine after I restarted it though - is this normal?

Thanks.

No . The only thing I can think of is if you were on a very old version. The nyc server moved from one provider to another due to bad packet loss, though I think I had waited until the DNS had propagated before turning the old one off, so the only case where it would have mattered is if you were on an old version that didnt automatically re-lookup the address after a disconnect.

Matt,

As P2Pool is basically its own relay network, and already has a large global presence, would it not make sense to integrate the relay network directly with P2Pool as well (or at least a few large nodes)?

Yes, this is why I'm trying to get people here to run it . Also, I'm rewriting the client in python, and hoping to get that integrated directly.

[phelix]

How often does p2pool query namecoind getblockaux? I would like to make sure the namecoind internal recalculation time step makes sense.

[windpath]

Also, I'm rewriting the client in python, and hoping to get that integrated directly.

That would be ideal

Thanks Matt

[Matt Corallo]

Also, I'm rewriting the client in python, and hoping to get that integrated directly.

That would be ideal

Thanks Matt

Check out https://github.com/TheBlueMatt/p2pool. Once I get some testing I'll pull request that and see if I can wake forrest from his drug-induced slumber.

[EErik]

Again need some help! Sorry i'm a noob ;-)

i'm loosing all my incoming nodes, i made 2 orphans.... what happened? is normal?

http://s22.postimg.org/s3vmzkvsd/Schermata_da_2014_08_29_14_32_27.jpg

thanks in advance E

[windpath]

...

...

Check out https://github.com/TheBlueMatt/p2pool. Once I get some testing I'll pull request that and see if I can wake forrest from his drug-induced slumber.

Your fork is up and running on my testing node.

I see your public.us-east.relay.mattcorallo.com (168.235.65.115) is connected as a bitcoin peer (I used addnode in bitcoin.conf).

I do not see 168.235.65.115 as a peer in p2pool (which may not be where I should see it).

I looked through the p2pool console output for "RELAY NETWORK" and did not see it anywhere.

How can I verify p2pool has connected to the relay network?

Again, thanks!

[Matt Corallo]

Check out https://github.com/TheBlueMatt/p2pool. Once I get some testing I'll pull request that and see if I can wake forrest from his drug-induced slumber.

Your fork is up and running on my testing node.

I see your public.us-east.relay.mattcorallo.com (168.235.65.115) is connected as a bitcoin peer (I used addnode in bitcoin.conf).

I do not see 168.235.65.115 as a peer in p2pool (which may not be where I should see it).

I looked through the p2pool console output for "RELAY NETWORK" and did not see it anywhere.

How can I verify p2pool has connected to the relay network?

Again, thanks!

Remove the addnode and run p2pool with --relay-network public.YOUR_REGION.relay.mattcorallo.com

[bryonp]

Check out https://github.com/TheBlueMatt/p2pool. Once I get some testing I'll pull request that and see if I can wake forrest from his drug-induced slumber.

Your fork is up and running on my testing node.

I see your public.us-east.relay.mattcorallo.com (168.235.65.115) is connected as a bitcoin peer (I used addnode in bitcoin.conf).

I do not see 168.235.65.115 as a peer in p2pool (which may not be where I should see it).

I looked through the p2pool console output for "RELAY NETWORK" and did not see it anywhere.

How can I verify p2pool has connected to the relay network?

Again, thanks!

Remove the addnode and run p2pool with --relay-network public.YOUR_REGION.relay.mattcorallo.com

all I get with this is
unrecognized argument --relay-network
any advise?

[kgb2mining]

all I get with this is
unrecognized argument --relay-network
any advise?

Did you pull down Matt's full p2pool git repo and use that instead of the original source from forrestv?  If not try that.  If no, not sure.

[jonnybravo0311]

How often does p2pool query namecoind getblockaux? I would like to make sure the namecoind internal recalculation time step makes sense.

Can anyone answer this for phelix?  I haven't been able to dig through the code thoroughly to find any polling time. You can start in work.py to see the calls to get the merged work (around line 62):

Code:

       # MERGED WORK

        self.merged_work = variable.Variable({})

        @defer.inlineCallbacks
        def set_merged_work(merged_url, merged_userpass):
            merged_proxy = jsonrpc.HTTPProxy(merged_url, dict(Authorization='Basic ' + base64.b64encode(merged_userpass)))
            while self.running:
                auxblock = yield deferral.retry('Error while calling merged getauxblock on %s:' % (merged_url,), 30)(merged_proxy.rpc_getauxblock)()
                self.merged_work.set(math.merge_dicts(self.merged_work.value, {auxblock['chainid']: dict(
                    hash=int(auxblock['hash'], 16),
                    target='p2pool' if auxblock['target'] == 'p2pool' else pack.IntType(256).unpack(auxblock['target'].decode('hex')),
                    merged_proxy=merged_proxy,
                )}))
                yield deferral.sleep(1)
        for merged_url, merged_userpass in merged_urls:
            set_merged_work(merged_url, merged_userpass)

        @self.merged_work.changed.watch
        def _(new_merged_work):
            print 'Got new merged mining work!'

[bryonp]

all I get with this is
unrecognized argument --relay-network
any advise?

Did you pull down Matt's full p2pool git repo and use that instead of the original source from forrestv?  If not try that.  If no, not sure.

THANK YOU... that did it... will see what happens...

[kgb2mining]

THANK YOU... that did it... will see what happens...

Cool, glad it worked. 

It seems to be OK running on my node so far, let us know how it looks for you.

[kgb2mining]

Stupid question - is it possible to setup a custom list of outgoing peer nods to talk to?  I've got the default 6, but I'm wondering if I should start tinkering with adding more.  There's probably a bunch of nice close fast nodes I could add in.

[jonnybravo0311]

Stupid question - is it possible to setup a custom list of outgoing peer nods to talk to?  I've got the default 6, but I'm wondering if I should start tinkering with adding more.  There's probably a bunch of nice close fast nodes I could add in.

When you start your node, use --p2pool-node argument.  For example:

Code:

./run_p2pool.py --p2pool-node 54.235.94.19:9333

By the way, that's windpath's node (located in VA).

[kgb2mining]

Stupid question - is it possible to setup a custom list of outgoing peer nods to talk to?  I've got the default 6, but I'm wondering if I should start tinkering with adding more.  There's probably a bunch of nice close fast nodes I could add in.

When you start your node, use --p2pool-node argument.  For example:

Code:

./run_p2pool.py --p2pool-node 54.235.94.19:9333

By the way, that's windpath's node (located in VA).

Thanks...

Is there a way to add multiples?  Just string them together on the commandline, or is there a simpler way maybe to put them in a file and read it in on startup?