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

Looks like it, and both by Discus Fish...

Another orphan?

Is there anything new in the world of P2Pool? I haven't had mine running for the last 5 months.

He hangs out on IRC. You might want to try him there.

Here is where I'm at with the history, not sure I'll include all of it, but if anyone can remember anything signifigant I left out please let me know...

June 17, 2011  - The p2pool project and concept was announced by Forrest Voight and he releases a screenshot of P2Pool running on testnet

July 17, 2011 - P2Pool begins public testing on test net, source released on GitHub, the first test block was found July 18

July 19, 2011 - Forrest announces readiness to test on mainnet

July 26, 2011 - First Press; P2Pool reviewed on Bitcoin Miner “P2Pool Decentralized Pool Nearly Ready For Prime-Time” http://bitcoinminer.com/post/8101660461/p2pool-decentralized-pool

August 16, 2011- First Altcoins added to P2Pool (Namecoin and Ixcoin)

August 18, 2011 - First Namecoin block found

August 23, 2011 - P2Pool first Bitcoin block - 142312  - 50BTC - 0TX Fees - 17 miners - 1.8MM Diff

September 4, 2011 - P2Pool finds its 5th Bitcoin block, first block that includes transactions (p2pool was essentially not including any transactions, just the block reward) 143923 - 50BTC - .044 TX fees - 30 miners - 1.77MM Dif

January 18, 2011- P2Pool reaches 100 GH/s

March 28, 2012 - 100th block found

January 10, 2013 - 1,000th bock found

June 11, 2014 - Coin Cadence launches detailed web based statistics for p2pool including all found blocks and miner payouts since p2pools inception as well as a real time global statistics dashboard

August 28th, 2014 - 2,187 blocks found, over 77,000 BTC mined, 12,417 miners paid

 

Thx!

Ah right, sorry. You can leave all your existing addnode info there - no problem. Just make sure you remove the one you added previously for the relay 

Yeah, I know it's better, what I meant was do I have to change anything in my Conf since I'm using the Relay?

For instance, should I remove all or some of my existing addnode listings for various other Bitcoin nodes or should I leave them alone because it won't make a difference? If I remove them, should I adjust my peer limits so it only connects to the Relay or do I leave it with my previously tweaked settings?

According to Matt, the jar file is better. I started off using the conf - but now use the jar as it gives you info, although I have noticed that it sometimes struggles to re-connect on my dodgy internet connection....

Question for running Matt's RelayNodeClient:  Do I have to do anything special from my bitcoind conf side (other than the usual RPC credentials stuff), or is the setup just running the jar with the right params?  So far it looks like the Relay is working correctly, but I want to make sure it's feeding my bitcoind as needed.  I already have a few choice addnode listings.

Agreed, sent him an email... Hope to hear back but not optimistic

Getting a response from forrestv would be a bit of a milestone in itself......he's not even logged in for over a month.......

Old School P2Poolers...

I reached out to Forrest V for this, but in case he does not reply, or misses a key point; I'm working on putting together a brief history of P2Pool milestones for inclusion in the new P2Pool.org site (launching soon!).

The current planned format is a timeline, so if you know of a key P2Pool milestone/event you remember from the past please share it here so I can include it in the new site...

I would STRONGLY recommend against keeping any private keys on the pool machine.

Right, good idea! I'll do a daily auto-backup on a usb stick. Just copy the folder "data" or is it better that I do I copy the whole folder directly "p2p-master"?

With regard to the possibility that something bad happens :-(  I made start the pool with the option "--address" which, as far I understand, it sends the payout of the pool to another address different than the wallet of the pool. is that right?
This idea, however, I hold in consideration because surely could raise a bit of work to my poor toshiba...

I had think a laptop was sufficient to run the p2pool because I noticed that system requirements not too exorbitant, also consumes much less power than a standard desktop, the only thing I regret is not having put a ssd .. .

I hope and I plan it can become a public node, because in Italy there are few p2pool and with a very high ping, but for first I want to fix this glitch ... thanks to all for the help. Erik

Correct, you'll just chance losing a share if it were to happen during your restart.  Otherwise no worries.  I have done it multiple times where I just restart bitcoind without touching P2Pool and it recovers nicely.

Ok, that sounds fine.  I'm thinking the disk will really help with the GBT.  1s is not good, but it's workable for now especially if you're just testing it and have plans for something beefier later.  I would just caution you that if you are running the wallet on the same "server" you take plenty of backups... with only a single drive if it goes you'll lose everything if you don't have backups.

And, I would also suggest that if you are planning on opening your node to be public (and possible even if not), if you have the resources, run your wallet on a totally different machine.  This way if something bad were to happen (hack)  your wallet won't be compromised. 

ok and thanks for the reply, so if I understand it, restart your bitcoin wallet does not create any problem (apart from losing a share if it happens at the time of the reboot)


is an experimental configuration to see if it works, surely if all goes well I will invest some money in a faster computer.

The HD is 7200rpm, but I'm going to replace it with a ssd

Operating system is openSUSE linux, cpu utilization varies between 20% and 70%, I have 4 gb of ram in total and by now they are only used 2.6

Got mine up & running today - just a heads up though, there's been another update to it 

Laptop?

I would guess your issue is with the hard drive - although it's 7200RPM, it is only a single drive.  You might be better served by replacing it with an SSD, since the local blockchain transactions are disk intensive.

Also, what O/S?  If it's Windows you also might benefit from more than 4GB RAM as well.

CPU should be plenty tho.