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

Look for:


in index.html and try setting that...

If anyone is thinking of buying a Antminer S2 from Bitmain in the next couple of weeks I have a couple of US$400 off vouchers I can donate, you need an account with Bitmain so I can transfer them over.

Andrew 

right, now the https://github.com/johndoe75/p2pool-node-status runs fine on the node but won't display anything when run from an external web server even when the url is entered in the Config file.

Has anyone run this on a separate web server successfully? anything special you had to do?

thanks for clarifying!

Uptime and share count are cleared when u reset. Hashing data (graphs) are stored, shares too.

what directory?

"p2pool folder"/data? it is writable and there is data in it but it still seems to reset after you restart the node.

There's already a db afaik
Maybe your directory isn't writable

great thanks. I saw the extended and default front end but not the node status stuff. will check it out.

Agreed on the uptime points, but whenever I kill my existing node process (having started a new instance of P2Pool first) it still takes a minute for my miners to connect on the new process, your right, it would be great to figure out a way to persist incoming hash power across instances of P2Pool on the same server.

The main graph is from the "Node Status" front end:

Live: http://mining.coincadence.com:9332/static/node-status/

Source: https://github.com/johndoe75/p2pool-node-status

The "miner stats" graph, which includes expected payout was put together by jonnybravo0311

Edit:

I keep the 3 major open source front ends live on my server (unedited), both as a reference for my development and a way for existing P2Pool miners to see a confirmation of what they are familiar with.

Default front end: http://mining.coincadence.com:9332/static/original/
Source: https://github.com/forrestv/p2pool/tree/master/web-static

Node Status front end: http://mining.coincadence.com:9332/static/node-status/
Source: https://github.com/johndoe75/p2pool-node-status

Extended front end: http://mining.coincadence.com:9332/static/extended/
Source: https://github.com/hardcpp/P2PoolExtendedFrontEnd

They are all publicly available in the footer link....

ok sure uptime maybe not but if you run another instance of p2pool up along side and it comes up immediately then your stats still reset and your uptime is still 100%. mainly though the shares, efficiency etc is what I want to keep. I was also looking to the server stats and considering presenting server uptime as well as node uptime to show users that the server has been 100% available and it was only the node that was restarted.
how did you get that nice smooth looking graph? keen to make mine a bit nicer.

Uptime needs to reset when you restart the node, that's a basic principle of "uptime", you have to be "up" the whole time...

I have not gotten to setting up MySQL yet, and all the data you want exists; my node displays data from 4 sources; Network data from P2Pool and Bitcoind, Recent P2Pool blocks from BlockChain.info, and miner shares from P2Pool's log file.

Node stats page: http://mining.coincadence.com/

Individual miner stats page: http://mining.coincadence.com/miner.php?id=19vXrwKGUhK4cCU8tA4kWZgbChcmh9a6qj

There is still lots of work to do, but I'll take progress over perfection

is there any way to store stats in a db or even flat file so that when you restart a node you don't loose the share, uptime and hashing stats of the pool?

I imagine we could pull the json feeds into a db table then make the front end pull those stats from there but hoping there is a simpler way.

I am very sad, every time I see less and less the p2pool's hashrate proportion of the whole network

        BLOCK_EXPLORER_URL_PREFIX='',
        ADDRESS_EXPLORER_URL_PREFIX='',
   TX_EXPLORER_URL_PREFIX='',

what would i set these with?? i tried the two block explorers i found for the coin but neither work came back with a parsing error.

from bitcoin folder network.py-  http://pastebin.com/y12UXAcL

thanks for helping thus far :-)

Bravo!!!... we need to spread the message in just this way.

If it wasnt for using my pc for gaming and dual booting linux i would have a p2pool node up iv had an xjo node online 24hrs stable. Only one muner tho atm. Not sure how many i could handle

would like to say thanks to you guys whe helped n provided me the info to get set up

I can help setting up nodes if anyone needs help.

Hey guys, I hope you can all get behind this:

https://bitcointalksearch.org/topic/decentralization-required-ongoing-problem-help-needed-609069

Let me expand upon that just a little bit to hopefully help qumqats understand what you mean.  Finding shares in p2pool is equivalent to solving a block.  Your miners, when they find one, are announcing to the p2pool network that they have found a low enough hash to satisfy requirements and are thus adding a new block to the chain.  An orphan share means that somebody else also found a solution that satisfied the requirements and announced their solution to the network.  Unfortunately for you, their solution was accepted and added to the chain prior to yours.

You're not completely out of luck, though, because your solution might also satisfy the Bitcoin network's requirements.  In that case, your orphaned share would solve the BTC block, and everyone gets their share of the reward.

Take a look at the following contrived example to see how it might work:

You find a share of difficulty 10,000,000,000
Another miner finds a share of difficulty 1,000,000,000

Both of you submit your work.  His is accepted as a share and yours becomes orphaned.  Yours is, however, accepted by the BTC block chain as a valid solution.  The block is added to the chain, 25BTC are generated and distributed to the miners in p2pool, along with transaction fees from the generated block.

Dead shares work similarly, except for the fact that they never make it out of your local environment.  Whereas an orphan share means you announced to the p2pool network that you found a solution, a dead share you don't even bother announcing because you have already been informed by the network that the share is invalid (i.e. the block height is lower than the current block being mined).  Just like with an orphaned share, your solution might be a valid solution to the BTC network, and if so, it solves the block and everyone gets paid.

Aside from best practice what advantages does it bring. How and what is bluematts backbone network?