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

I believe it should connect after a while.

Worked for me with both the options.

in ~/.bitcoin/bitcoin.conf


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


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


 
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:

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?

Yes, RelayNodeClient.jar is nice.

Add node option can be checked with=>


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

then,

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.

Change MyNetworkInterface respectively with your network interface.

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

Cheers,

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:


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.

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,

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,

This was my suggestion:

https://bitcointalksearch.org/topic/m.7873313

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

M

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

Thanks.

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


in the debug console.

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

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.

Geez, it's like deja-vu:

https://bitcointalksearch.org/topic/m.8442518

I'm not saying I'm developing code for this in p2pool... I'm simply saying what Matt did/is doing is similar to the thought I had brought in that post.

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.

There have been a couple donations the last week through the tool here: http://www.blisterpool.com/p2pdonate, it may have come from that?

cool thanks , i was thinking about learning python as a start as well!!! I will take your advice seriously 

If your desire, long term, is to contribute to p2pool; learning python is a good place to start. p2pool is written in python, and has its own version of the blockchain (share chain) and uses the same p2p design as the bitcoin network so studying bitcoind would help as well.

What others have said is true...

After a year or so you may be able to build a go-cart, but your not in the NASCAR league...

There is just way to much advanced technology flying around the bitcoin space for any individual to ever become an expert in it all. That being said, if you pick a focus area and learn how bitcoin works from a technical standpoint you would be able to contribute to p2pool (in its current state) if you knew python...

Here is the kid gloves version:

http://www.codecademy.com/en/tracks/python

OK so the "3 days" logic comes from this:

[source: https://en.bitcoin.it/wiki/P2Pool]
-------------------------------------------------------------------------------------------------
Payout logic

Each share contains a generation transaction that pays to the previous n shares, where n is the number of shares whose total work is equal to 3 times the average work required to solve a block, or 8640 (= 24 hours of shares), whichever is smaller. Payouts are weighted based on the amount of work each share took to solve, which is proportional to the p2pool difficulty at that time.

The block reward (currently 25BTC) and the transaction fees are combined and apportioned according to these rules:

A subsidy of 0.5% is sent to the node that solved the block in order to discourage not sharing solutions that qualify as a block. (A miner with the aim to harm others could withhold the block, thereby preventing anybody from getting paid. He can NOT redirect the payout to himself.) The remaining 99.5% is distributed evenly to miners based on work done recently.

In the event that a share qualifies as a block, this generation transaction is exposed to the Bitcoin network and takes effect, transferring each node its payout.
-------------------------------------------------------------------------------------------------

First of all, should 8640 shares = 3 days of shares instead??? is there something wrong with the Wiki???

With this amendment, I would translate the logic as follows in common language:

Whenever a block is found on p2pool, payout will be proportionally distributed to:
- shares generated during the past n hours, where n hours is the expected time to generate 3 blocks (i.e. if expected time to generate 1 block is 12 hours, n = 36 hours = 1.5 days)
- however the maximum value for n is 3 days, meaning if a share is over 3 days old, it's basically too old to generate any income

Is my understanding correct???

Thanks for the advice  

I understand what I was saying was bold. I know I will not be able to contribute much in the short term, but I am really interested and considering to take formal education on this direction, either part-time school, or buying books for self education.

I have 2 bachelor and 1 master degrees, in civil engineering and law (I know it's totally unrelated to computer ...) and am currently having enough rest to start another line of study ~~~ I have recently completed a short 40 hour course on webpage design, and have some basic idea of HTML5 and CSS3 ....

So ... for all those learnt coders out there, may I ask in what direction should I head to from scratch, if I wish to learn all about coding Do I need something like BEng(Computer) or are there easier stuffs like diploma or self educating books that I can read to acquire the skill??  Continuous learning is just my hobby