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

Eloquently put, my sentiments exactly - & there's that block! 

Absolutely, if you have the resources running your own node is the best way to mine on P2Pool.

While I don't think at 110 GH/s you can expect a share in every block, I think with patience you will do OK. I pulled an example from the active miner pool that is around 110 GH/s, take a look to get an idea of what your rewards might be:

http://minefast.coincadence.com/miner.php?id=1Cvq2vEsR2XVHLhnFT7HDG6Gq6KTEPYkA2

So I remember a while back I tried P2pool with my 110 gh/s "the new rbox" - I was using coincadence... there was some lag issue and I could never tell if I was actually contributing hashes or just burning electricity. Some post I read basically said if your hardware isn't pulling down X hash/sec, then p2pool isn't for you, due to this lag issue.

If I ran my own node (my own p2pool, I guess) am I right to think that I would avoid the lag issues? Because then I would just be essentially solo mining but sharing my block reward with others in the p2pool cooperative?

......

It's amazing how you seem to pop up whenever development comes up around here singing your doom and gloom story, anyway...


Yes, Forrest does not participate here, that is "The way it is".


By "pressure" do you mean the Lightcoin folks giving him a pile of bitcoin to work on a problem he never solved?


Actually, he explicitly stated he did not.


I did not characterize anything, I simply said that "is the way it is" with no characterization at all....

I do however think it's unfair for you to chime in with your 0.02 bits every time someone says they wish their was an active dev with your mischaracterizations that "everyone" "bullied" Forrest.

Many here proposed thoughtful ideas, raised money, and wanted to continue to work on a problem that remains difficult to solve.

If you have nothing to contribute, don't mine on P2Pool, and are only here to talk about how you think the community "killed" P2Pool (again) please go back to Bel Air Carlton, we have blocks to mine...

"The way it is"? I seem to remember that the p2pool developer, upon which everyone relied, was being unfairly pressurised in all sorts of ways. The man was bullied into a position where it couldn't possibly be worth the effort to deal with the demands that were made. He had a plan to make p2pool scale up more, no-one ever found out what that was.

Do not mischaracterise what happened there; the braying coyotes and their idiot lemmings killed p2pool development, not the p2pool developer.

I never used to have this problem on my old router. Perhaps this newer router I'm using is blocking the packets.

same here i have no incoming even after letting the ports through firewall.

btw,





i think the update is slow on the network ?

well just a short burst

8333 - bitcoin
9332-9333 - p2pool
7333 - nmc

make sure they not running, restart after port forward & it should work ....

I'm not getting any incoming peers. I am forwarding port 9333 on my NAT router. That's correct, right?

Agreed, but this is the way it is...

It is important to note however that while Forrest has stopped working on the code himself he has not abandoned the GitHub repository and other peoples changes have been merged over time.


Currently my guess is yes, you are the only one. I do recall it being discussed here in the past, and I ~believe~ that implementing pypy turned out to be pretty much neutral as far as performance goes, if forum search is ever re-enabled you might be able to find it in this thread...

In my experience the greatest improvements to performance come with GetBlockTemplate and peer latency tuning.

Last time the dev logged in here was Oct 2014, which might explain why it's so difficult finding answers....

Am I the only one here trying to run p2pool with pypy? Google has proven fruitless....

BTW, here's a list of ports I'm using for the merge mined coins:

 coin   /  port  /  rpc

Bitcoin: 8333 / 8332
Devcoin: 52333 / 6333
Fusioncoin: 8492 / 18491
Huntercoin: 8398 / 8399
i0coin: 7337 / 7338
iXcoin: 8337 / 8338
Namecoin: 7333 / 8336
Groupcoin: 51333/51332
Unobtanium: 65534/65535
Coiledcoin: 8368/8367

All seem to be working with blocks appearing in wallets. I've not been able to compile Geistgeld yet due to it using bdb 4.7, & there's a few more coins that might be merge mine-able (Vikingcoin was on 1st release - not sure about the re-launched version though).

Shame the dev doesn't participate here......can't be good for p2pool.

not that i know of but it'll be good if there's any improvement.

btw, c'mon guys, let's bump it up. due for blocks ! i've been bumping it last 2 days but running out of btc

Are there any plans to release a new version of p2pool?

Hmmmm...think I'll stick with 8336 stated by the website details, seeing as I can't find any certain confirmation for now. Am I right in thinking that as long as my rpc ports match up on both my coin.conf & p2pool start-up command I'm OK? I'm more concerned about the listening ports TBH, as they're the ones contacting the outside world.

I found a new thread for merge mining coins where domob is active (NMC & HUC dev):  https://bitcointalksearch.org/topic/merged-mined-coins-association-memica-1008100  so maybe I can get definate details there from the coin devs who are going to join the organisation - I've posted there also, let's see......

NMC port is 7333 others not sure as NMC is the only coin worth merge mining now but any extras is still an income

Hello everyone,

Long time lurker who finally decided to set up my own p2pool node after receiving my mining gear. I've read though this thread a few times (well, most of it!) but I have a few questions so maybe someone can enlighten me? I'm running Ubuntu Server 64bit + 32GB RAM with the Xfce4 desktop environment (my command line skills aren't up to complete headless operation yet I'm afraid) & have successfully installed all wallets for merge mining with the help of this excellent thread: https://bitcointalksearch.org/topic/how-to-run-your-own-p2pool-in-ubuntu-1404-lts-with-merged-mining-651819  - (NMC, DVC, I0C, HUC, UNO, GRP & FSC - mainly for my own education). I have p2pool up & running without errors in the console & all 7 coins reporting the "got new merge mining work" - not bad for a noob!  
While setting up port forwarding on my router, I noticed some conflicting views on some of the coins ports to forward, namely NMC & DVC:


However, I get error messages about permissions advising me to use the sudo -H flag when installing, resulting in failure. Are all the above commands done with sudo or exactly as written? My OS installation is a fresh install without any changes from standard & everything I've installed for p2pool including the different wallets has gone smoothly, so I've no idea as to why pypy is failing to install.......

Hope someone can clarify, thanks for reading  

Test my Bitcoin P2pool Node. The node is a german Node in Berlin (Datacenter) and permanent up. http://bitcoin.web-rss-verzeichnis.de:9332/static/

This happens when a dead/orphaned share satisfies the network difficulty and solves the block.  P2Pool doesn't record the share (because it was dead/orphaned) on the share chain.  Since there's no record of it on the share chain, the UI doesn't display the block it produced.

Windpath has it on his node because he scrapes the data from the blockchain.

I suspect my node url is due to i sent the node info to the moderator of the list before i set the domain name to the IP.  I registered the name 4 - 6 weeks after the node was up.