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

[pmorris]

Has anyone read about Matt Corallo's new "bitcoin backbone project" - https://bitcoinfoundation.org/2014/08/a-bitcoin-backbone - would it make sense to connect bitcoind from a P2Pool set up to this low latency backbone.

My take was that what Matt is doing is very cool and when blocks are several MB in size something like this or Gavin's alternative proposal for eliminating retransmission of transactions with every block will be important.

For me, each of my nodes has a connection which p2pool and bitcoind never come close to utilising. So I didn't think the block size was a particularly big deal at the moment from a speed perspective. Don't know if that's been actively researched.

If Matt's built it and it works then I see no reason not to connect to one of his nodes to gain the benefit of it.

[1713573221]

1713573221

[1713573221]

1713573221

[windpath]

Has anyone read about Matt Corallo's new "bitcoin backbone project" - https://bitcoinfoundation.org/2014/08/a-bitcoin-backbone - would it make sense to connect bitcoind from a P2Pool set up to this low latency backbone.

My take was that what Matt is doing is very cool and when blocks are several MB in size something like this or Gavin's alternative proposal for eliminating retransmission of transactions with every block will be important.

For me, each of my nodes has a connection which p2pool and bitcoind never come close to utilising. So I didn't think the block size was a particularly big deal at the moment from a speed perspective. Don't know if that's been actively researched.

If Matt's built it and it works then I see no reason not to connect to one of his nodes to gain the benefit of it.

I'll be adding Coin Cadence to his east coast relay on the next restart.

[xyzzy099]

Has anyone read about Matt Corallo's new "bitcoin backbone project" - https://bitcoinfoundation.org/2014/08/a-bitcoin-backbone - would it make sense to connect bitcoind from a P2Pool set up to this low latency backbone.

My take was that what Matt is doing is very cool and when blocks are several MB in size something like this or Gavin's alternative proposal for eliminating retransmission of transactions with every block will be important.

For me, each of my nodes has a connection which p2pool and bitcoind never come close to utilising. So I didn't think the block size was a particularly big deal at the moment from a speed perspective. Don't know if that's been actively researched.

If Matt's built it and it works then I see no reason not to connect to one of his nodes to gain the benefit of it.

I'll be adding Coin Cadence to his east coast relay on the next restart.

If you are running bitcoin-qt, you don't need to wait for a restart - you can just type:

Code:

addnode public.us-east.relay.mattcorallo.com add

in the debug console.

[windpath]

Has anyone read about Matt Corallo's new "bitcoin backbone project" - https://bitcoinfoundation.org/2014/08/a-bitcoin-backbone - would it make sense to connect bitcoind from a P2Pool set up to this low latency backbone.

My take was that what Matt is doing is very cool and when blocks are several MB in size something like this or Gavin's alternative proposal for eliminating retransmission of transactions with every block will be important.

For me, each of my nodes has a connection which p2pool and bitcoind never come close to utilising. So I didn't think the block size was a particularly big deal at the moment from a speed perspective. Don't know if that's been actively researched.

If Matt's built it and it works then I see no reason not to connect to one of his nodes to gain the benefit of it.

I'll be adding Coin Cadence to his east coast relay on the next restart.

If you are running bitcoin-qt, you don't need to wait for a restart - you can just type:

Code:

addnode public.us-east.relay.mattcorallo.com add

in the debug console.

Thanks.

[bitcoinbearhk]

Just a thought after mining for some time on p2pool...

it takes 30 seconds to get a share across the p2pool network, so it's roughly 20 times faster than the block finding speed ....

but is 30 seconds enough ? ......

It is getting so hard now to get a share even when we are only at 2~3 PH/s , what would it be like if we get up to 20PH/s (i.e. like 10% network share only) ...... it would take people days to even get 1 share.

Now we are back to the problem with solo mining, high variance and no payout for many of the days for the regular small miners.


Should we be developing some like a p2pool 2.0, with share speed much reduced to like 1 second or something like what other pool does, each "share" on the machine is just a share, and divide it smaller

[mdude77]

Just a thought after mining for some time on p2pool...

it takes 30 seconds to get a share across the p2pool network, so it's roughly 20 times faster than the block finding speed ....

but is 30 seconds enough ? ......

It is getting so hard now to get a share even when we are only at 2~3 PH/s , what would it be like if we get up to 20PH/s (i.e. like 10% network share only) ...... it would take people days to even get 1 share.

Now we are back to the problem with solo mining, high variance and no payout for many of the days for the regular small miners.


Should we be developing some like a p2pool 2.0, with share speed much reduced to like 1 second or something like what other pool does, each "share" on the machine is just a share, and divide it smaller

This was my suggestion:

https://bitcointalk.org/index.php?topic=18313.msg7873313#msg7873313

I'd give it a try if I had the time for it.

M

[linuxforyou]

Pool rate: 2.02PH/s (14% DOA+orphan) Share difficulty: 9760000
Local rate: 2.37TH/s (2.7% DOA) Expected time to share: 4.9 hours
Shares: 4 total (0 orphaned, 0 dead) Efficiency: 115.8%
Current block value: 25.03892975 BTC Expected time to block: 14.1 hours

P2Pool node URL=http://blr.zapto.org:9332
Location=India.


Any inputs/Feedback?

Cheers,

[linuxforyou]

Anyone want's to try P2Pool node=>

http://blr.zapto.org:9332/

Fee is 0, can expect some downtime. Would be arranging power supply for p2pool node based on user's interest.

Cheers,

[hamburgerhelper]

Has anyone read about Matt Corallo's new "bitcoin backbone project" - https://bitcoinfoundation.org/2014/08/a-bitcoin-backbone - would it make sense to connect bitcoind from a P2Pool set up to this low latency backbone.

My take was that what Matt is doing is very cool and when blocks are several MB in size something like this or Gavin's alternative proposal for eliminating retransmission of transactions with every block will be important.

For me, each of my nodes has a connection which p2pool and bitcoind never come close to utilising. So I didn't think the block size was a particularly big deal at the moment from a speed perspective. Don't know if that's been actively researched.

If Matt's built it and it works then I see no reason not to connect to one of his nodes to gain the benefit of it.

I'll be adding Coin Cadence to his east coast relay on the next restart.

If you are running bitcoin-qt, you don't need to wait for a restart - you can just type:

Code:

addnode public.us-east.relay.mattcorallo.com add

in the debug console.

Thanks.

From my brief bit of experimentation, the above doesn't work. It looks like you can't connect bitcoind directly to the Relay Network. You need to run RelayNodeClient which connects to the Relay Network and your local bitcoind.

So you would do:

Code:

java -jar RelayNodeClient.jar public.us-east.relay.mattcorallo.com 127.0.0.1:8333 

That worked for me and I saw transactions and blocks passed to my bitcoind. Then you'd just have to get the RelayNodeClient application running in a persistent way (upon startup, with a watchdog, etc.). That will vary based on your operating system. I'll be getting a systemd unit file ready to run on CentOS 7, which is what my node uses. If anyone's interested, I'd be happy to share it.

[linuxforyou]

Yes, RelayNodeClient.jar is nice.

Add node option can be checked with=>

Code:

host public.us-east.relay.mattcorallo.com

which gives IP=>
public.us-east.relay.mattcorallo.com has address 162.243.69.180

then,

Code:

netstat  -lant | grep 162.243.69.180 

Should give established connection between local IP and 162.243.69.180

To check actual traffic between local node and 162.243.69.180 tcpdump can be used.

Code:

 tcpdump -neivv -i MyNetworkInterface host 162.243.69.180 

Change MyNetworkInterface respectively with your network interface.

0 packet captured means something is wrong, else should be fine.

Cheers,

[hamburgerhelper]

Yes, RelayNodeClient.jar is nice.

Add node option can be checked with=>

Code:

host public.us-east.relay.mattcorallo.com

which gives IP=>
public.us-east.relay.mattcorallo.com has address 162.243.69.180

then,

Code:

netstat  -lant | grep 162.243.69.180 

Should give established connection between local IP and 162.243.69.180

To check actual traffic between local node and 162.243.69.180 tcpdump can be used.

Code:

 tcpdump -neivv -i MyNetworkInterface host 162.243.69.180 

Change MyNetworkInterface respectively with your network interface.

0 packet captured means something is wrong, else should be fine.

Cheers,

Thanks for that info. The reason I didn't think a direct connection from bitcoind to the Relay Network worked for me is because after I did the "addnode" I checked bitcoind with the "getaddednodeinfo" command. I got the following output:

Code:

[
    {
        "addednode" : "public.us-east.relay.mattcorallo.com",
        "connected" : false,
        "addresses" : [
            {
                "address" : "162.243.69.180:8335",
                "connected" : "false"
            }
        ]
    }
]

Also, the number of bitcoin peers from "getinfo" stayed the same. Thus I concluded that something was wrong and I went down the RelayNodeClient path. I would prefer to connect bitcoind directly to the Relay Network and save the RAM that RelayNodeClient uses, but its not a big deal (30 MB of RAM, I believe) either way. Has anyone else had success connecting bitcoind to the Relay Network without RelayNodeClient?

[linuxforyou]

Worked for me with both the options.

in ~/.bitcoin/bitcoin.conf

Code:

addnode=public.us-east.relay.mattcorallo.com:8335

As well as with Relay RelayNodeClient.jar.

After updating bitcoin.conf you should restart bitcoind daemon.

Checkout in debug.log?

Make sure your node is able to make a connection to public.us-east.relay.mattcorallo.com on port number 8335

Code:

echo test | nc public.us-east.relay.mattcorallo.com 8335

Code:

echo $?

0 means successful connectivity. or simply you can check with telnet too

Code:

telnet public.us-east.relay.mattcorallo.com 8335

 
Cheers,

[Polyatomic]

Code:

Polyatomic@3.16.1-ck1+:~$ bitcoind getaddednodeinfo true
[
    {
        "addednode" : "public.au.relay.mattcorallo.com:8335",
        "connected" : true,
        "addresses" : [
            {
                "address" : "128.199.219.92:8335",
                "connected" : "outbound"
            }
        ]
    }
]

I believe it should connect after a while.

[nreal]

Smaller shares are no good, this is mining industry. Theres nothing more stupid than dust payment. And if some people loose their beauty sleep because not donating and thinking a solutiont to that, i give you a hint - dont mine here go ahead mine with Eligius or Ghash. Its the makers wish to have some income for the work he has done - if it doesnt suit you move on.
Stupid people talking about taking this software because lack of devel. If something works why would you fix it?

Its not a dev prob if someone cant use his software as its supposed. Hey this is a free world.

[PatMan]

.......if it doesnt suit you move on. Stupid people talking about taking this software because lack of devel......

 

Guess I'm stupid then   If all the "stupid people" did what you suggest, p2pool would have died over a year ago.

Anyway, back on topic. I added the eu relay a couple of days ago by adding it to the .conf file, no worries so far:

        "addednode" : "public.eu.relay.mattcorallo.com:8335",
        "connected" : true,
        "addresses" : [
            {
                "address" : "146.185.173.241:8335",
                "connected" : "outbound"

It is a cool idea though  

@ linuxforyou: Very good info - thanks!

[mdude77]

Smaller shares are no good, this is mining industry. Theres nothing more stupid than dust payment. And if some people loose their beauty sleep because not donating and thinking a solutiont to that, i give you a hint - dont mine here go ahead mine with Eligius or Ghash. Its the makers wish to have some income for the work he has done - if it doesnt suit you move on.
Stupid people talking about taking this software because lack of devel. If something works why would you fix it?

Its not a dev prob if someone cant use his software as its supposed. Hey this is a free world.

Someday dust may be valuable.  And regular dust payments add up.  They'd pay for it in trans fees anyhow.

M

[xyzzy099]

Has anyone read about Matt Corallo's new "bitcoin backbone project" - https://bitcoinfoundation.org/2014/08/a-bitcoin-backbone - would it make sense to connect bitcoind from a P2Pool set up to this low latency backbone.

My take was that what Matt is doing is very cool and when blocks are several MB in size something like this or Gavin's alternative proposal for eliminating retransmission of transactions with every block will be important.

For me, each of my nodes has a connection which p2pool and bitcoind never come close to utilising. So I didn't think the block size was a particularly big deal at the moment from a speed perspective. Don't know if that's been actively researched.

If Matt's built it and it works then I see no reason not to connect to one of his nodes to gain the benefit of it.

I'll be adding Coin Cadence to his east coast relay on the next restart.

If you are running bitcoin-qt, you don't need to wait for a restart - you can just type:

Code:

addnode public.us-east.relay.mattcorallo.com add

in the debug console.

Thanks.

From my brief bit of experimentation, the above doesn't work. It looks like you can't connect bitcoind directly to the Relay Network. You need to run RelayNodeClient which connects to the Relay Network and your local bitcoind.

So you would do:

Code:

java -jar RelayNodeClient.jar public.us-east.relay.mattcorallo.com 127.0.0.1:8333 

That worked for me and I saw transactions and blocks passed to my bitcoind. Then you'd just have to get the RelayNodeClient application running in a persistent way (upon startup, with a watchdog, etc.). That will vary based on your operating system. I'll be getting a systemd unit file ready to run on CentOS 7, which is what my node uses. If anyone's interested, I'd be happy to share it.

My bad - you do have to specify port 8335 - but you don't need to use anything but bitcoin-qt, as others have already related above.

[xyzzy099]

Has anyone read about Matt Corallo's new "bitcoin backbone project" - https://bitcoinfoundation.org/2014/08/a-bitcoin-backbone - would it make sense to connect bitcoind from a P2Pool set up to this low latency backbone.

My take was that what Matt is doing is very cool and when blocks are several MB in size something like this or Gavin's alternative proposal for eliminating retransmission of transactions with every block will be important.

For me, each of my nodes has a connection which p2pool and bitcoind never come close to utilising. So I didn't think the block size was a particularly big deal at the moment from a speed perspective. Don't know if that's been actively researched.

If Matt's built it and it works then I see no reason not to connect to one of his nodes to gain the benefit of it.

I'll be adding Coin Cadence to his east coast relay on the next restart.

If you are running bitcoin-qt, you don't need to wait for a restart - you can just type:

Code:

addnode public.us-east.relay.mattcorallo.com add

in the debug console.

Thanks.

From my brief bit of experimentation, the above doesn't work. It looks like you can't connect bitcoind directly to the Relay Network. You need to run RelayNodeClient which connects to the Relay Network and your local bitcoind.

So you would do:

Code:

java -jar RelayNodeClient.jar public.us-east.relay.mattcorallo.com 127.0.0.1:8333 

That worked for me and I saw transactions and blocks passed to my bitcoind. Then you'd just have to get the RelayNodeClient application running in a persistent way (upon startup, with a watchdog, etc.). That will vary based on your operating system. I'll be getting a systemd unit file ready to run on CentOS 7, which is what my node uses. If anyone's interested, I'd be happy to share it.

My bad - you do have to specify port 8335 - but you don't need to use anything but bitcoin-qt, as others have already related above.

It seems that this actually does not work.

It appears that the ADDNODE command in the console will always fail if you already have 8 outgoing connections.  It will eventually use the connection you added only if one of your 8 outgoing connections drops.

Sorry again for the misinformation.

[phelix]

Thanks JB, so it's not just me then. I'll investigate further........

Edit: I notice forrestv made a change to the p2poool repo ( !) 7 days ago, increased maximum worker difficulty 1000x, that wouldn't be the cause......would it?

Edit2: Tried running namecoin on rav3n_pl fork with the same results, so it's not a p2pool issue. Had to close the namecoin wallet as it was eating cpu as well. Oh well, that'll have to stay off then.......... Very strange.

There have been some huge blocks recently aggregating a mass of tiny inputs. This seems to lead to getauxblock taking a very long time. We are looking into it but it might take a while.

BTW: As far as I know Namecoin mining reward variance is very high with P2P. We would be happy to support any plans to improve this, maybe with a bounty.

The reason the variance is so high is because each node that is merge-mining is effectively trying to solo mine the blocks for the coins (NMC, DVC, etc).

It would be nice if the entire hashing power of the pool, or at least the hashing power of the nodes that are merge-mining, could be applied rather than individual nodes attempting to solve the blocks.

Yes. I'm sure if someone would work on a solution the involved altcoins, maybe also Bitcoin could come up with a bounty.

[drukoz2]

i am currently earning 0.035 - 0.04 btc everyday with 1.5 TH i wanted to know how much would i earned in p2pool and wicth pool would i use since there are lots of them or i don't get it would love some explanation