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

I am expecting to get out of the bitcoin mining business sooner that later.  At the same time, I am still a fan of p2pool and would be happy to continue to maintain p2pool.info long after I am no longer personally mining.  However, as I shut down my home mining operation and all the servers running in my house that support that operation, I'd like to remove the dependency p2pool.info has on server(s) running inside my house, and I'm hoping someone in the p2pool community can help.

What p2pool.info needs is access to a bitcoind server's RPC interface.  For security reasons, ideally this would be a bitcoind instance that had an empty wallet that had never been used.

These are the RPCs that p2pool.info uses:

* getblockcount
* getdifficulty
* getblockhash
* getblock
* getrawtransaction

As for bitcoin version, it needs to be at least 0.7 as some of the RPCs above were new in 0.7.  If it happens to be running a version of 0.8 or the GIT tree with the new optimized storage structure, it needs to be running with the txindex=1 configuration setting because p2pool.info needs to be able to look at all generation transactions for all blocks.

I'm hoping that someone here is already running bitcoind in a datacenter somewhere and would be willing to let p2pool.info's web server connect to it to watch for p2pool blocks.  If you have a bitcoind server whose RPC interface is accessible over the internet and that you'd be willing to give me access to, please let me know.

BTW,

see how memory usage grows with the same slope of the number of incoming connections...

spiccioli

forrestv,

memory and bandwidth: this bandwidth cannot be sustained on a home connection, this is a HDSL line with 3Mb up/down cap and not a standard ADSL.

look at this

http://p2pool.soon.it:9332/static/graphs.html?Day

Something went wrong and memory jumped from 200MB to 1GB overnight.

spiccioli

ps.

Try tune miner settings if you not have it done already.
In cgminer set in command line:
or in config file:
Default is 2 threads and 1 additional queue what can be source of unwanted doas. We have fast longpools there
Check also your GBT latency on node graph. It should be 0.5s top.

9% DOA isn't normal, 9% DOA + stale is better than avg (most of the time), 9% stale would be around the median

oh

i just looked at SS, so I guess those wouldnt be orphans, they'd be DOA?  yeah, that's high

I'v got ~9% invalid shares. Is this normal?

I observed odd thing (TRC node, but probably same thing on all other)
1. stop nodedelete saved sharechain, start node, allow to run over 24hrs = memory usage stops at 100MB
2. stop node and start it again (no delete) = just after start it is already 130MB just after start.
3. stop node, delete sharechain, allow to load it = around 70MB and slowly rising to 100MB over 24hrs.
Something is wrong in share storing imo..

Hello again Rav3n,

Yeah, installed the latest version. Tried it on two different Linux rigs as well as a windoze 7 64 setup - same thing. Thing is, it's only p2pool that gives me stratum issues, every other pool I use with stratum works perfectly....

Peace.

tbh, i would take my lucky ass back to p2pool, except i'm busy recouping fireducks 400 btc losses.  so far 2 blocks solved in about 20 btc of payments.

maxbtc?  2m+ difficulty before halving, 15 blocks solved, 400 payed out. 

some folks calls it a sling blade, Billy Bob Thornton calls it a kaiser blade

I call it Enhancements

oh, it's on

Mining proxy problem was fixed in https://github.com/forrestv/p2pool/commit/2dffea0 over month ago.
Do you have current version of p2pool? Or use updated public node?

I solved three blocks using Stratum on p2pool over the course of 2 weeks @ 3mill difficulty and 8ghash.  nothing wrong with it.

sorry for your shit luck and that i didnt use my extreme luck to solo mine instead

I think we should change the name of that "luck" graph to something more accurate, something like: "Three meaningless downward spiraling lines that indicate nothing, take no notice. Everything is fine.".........

I also think that anyone who even dares to suggest that there is anything wrong with anything should be cast out, ridiculed and burnt at the stake "witch style"....

Seriously though, as soon as the non-existing stratum problem is sorted I'll be mining again.

Good luck & Peace. 

okay..... no explanation, just the assumption, hypothesis, suggestion, supposition, guess, speculation

No need.p2pool is reading it form config file.
Wrong. user and pass can be anything, if you want mine to specyfic bitcoin address use it as username.
You need restart bitcoin after you edited bitcoin.conf file

Just wanted to make a d'oh note. I rebooted my computer and it works now.
I suppose it's because Twisted makes a registry edit and you need a reboot for that to take effect.

In other news, the above instructions will get you mining on P2Pool on Windows. (I'm using Win 8 x64)

I really have no idea. The GF count at the top tells you how many real disconnects you get. On a local machine it should pretty much never drop out, and on a local network it should only exceedingly rarely do so. On a remote pool with my fairly reliable connection (even through wifi!) I only get disconnects when the pool restarts their server or my  ISP has an outage, and that's something like 1 dropout a month.

Aaaaaaaaaaaaaaaaaaaaaaaaah! He said the L word!

Careful... might end up starting a religion down that path...

-- Smoov

Because...  it's luck?  You're looking for an explanation of why a random series of events occurred a certain way?

Hi ckolivas,

What do you think is causing the constant disconnects & restarts? I've tried every possible setting imaginable with cgminer, many hours, and I only get this problem with p2pool & stratum since 60 days or so. Thanks.