|
Very nice work on this software. I love it and use it all day every day. Thank you for actually being one of those rare guys who support windows phone also. MultiMiner is the best mining software hands down.
|
|
|
|
I've now got all shares submitted by my node in a nice fast DB. They are reported for the node on the main page, and per miner on the miner dashboard page, below is a shot from the miner dashboard. I'm going to do the same for blocks next...  nice! care to share or collaborate on my front end? would love to be able to display more stats persisted over restarts etc. |
|
|
|
|
Www.norgzpool.net.au now has Sydney, Australia node up and functional for BTC. That means we now have Singapore for BTC and ltc as well as Sydney for BTC.
Australia au.norgzpool.net.au:9332
Singapore pool.norgzpool.net.au:9332
Singapore ltc pool.norgzpool.net.au:9327
Stats front end is now on github called p2pool fancy front end.
Servers are high spec, low latency hosted in tier 1 data centers.
All nodes are 0% fee!
|
|
|
|
I've uploaded my front end code to github. If you would like to use it please feel free to do so and if you really like the work I have done you can donate some Bitcoin to me 17HQeLJNp2r3WW99amE3hXcvEYR96jZoPJ I have called it p2pool fancy front end https://github.com/norgan/p2pool_fancy_front_end |
|
|
|
|
New node added in Sydney, Australia. au.norgzpool.net.au:9332
|
|
|
|
Just added a new Sydney, Australia node to my pool. www.norgzpool.net.au for those aussie miners out there. |
|
|
|
d3.json('http://pool.norgzpool.net.au:9332/global_stats', function(global_stats) {
d3.select('#pool_rate').text(d3.format('.3s')(global_stats.pool_hash_rate) + 'H/s');
d3.select('#pool_stale').text(d3.format('.2p')(global_stats.pool_stale_prop));
d3.select('#difficulty').text(d3.format('.3r')(global_stats.min_difficulty));
var time_to_block = local_stats.attempts_to_block/global_stats.pool_hash_rate;
d3.select('#time_to_block').text(d3.format('.3r')(time_to_block/3600) + " hours");
d3.select('#expected_payout_amount').text(d3.format('.3r')(local/global_stats.pool_hash_rate*local_stats.block_value*(1-local_stats.donation_proportion)));
/// ============================================
var data = [
['Local speed', local],['Local dead speed', local_dead], ['Global speed', global_stats.pool_hash_rate]
];
if (plot2) {plot2.destroy();}
$("#targetPlot2").remove();
$("#SpeedChart").append("<div id='targetPlot2'></div>");
plot2 = jQuery.jqplot ('targetPlot2', [data],
{
seriesDefaults: {
// Make this a pie chart.
renderer: jQuery.jqplot.PieRenderer,
rendererOptions: {
// Put data labels on the pie slices.
// By default, labels show the percentage of the slice.
showDataLabels: true
}
},
legend: { show:true, location: 'e' }
}
);
});
/// ============================================
var data = [
['Good', local_stats.shares.total - (local_stats.shares.orphan + local_stats.shares.dead)],['Dead', local_stats.shares.dead], ['Orphaned', local_stats.shares.orphan]
];
if (plot1) {plot1.destroy();}
$("#targetPlot1").remove();
$("#ShareChart").append("<div id='targetPlot1'></div>");
plot1 = jQuery.jqplot ('targetPlot1', [data],
{
seriesDefaults: {
// Make this a pie chart.
renderer: jQuery.jqplot.PieRenderer,
rendererOptions: {
// Put data labels on the pie slices.
// By default, labels show the percentage of the slice.
showDataLabels: true
}
},
legend: { show:true, location: 'e' }
}
);
});
/// pool speed grapg
plot_later(d3.select("#main-local"), "H/s", "H", [
{"url": "http://pool.norgzpool.net.au:9332/web/graph_data/local_hash_rate/last_" + period, "color": "#0000FF", "label": "Total"},
{"url": "http://pool.norgzpool.net.au:9332/web/graph_data/local_dead_hash_rate/last_" + period, "color": "#FF0000", "label": "Dead"}
],1000,300);
}I think that's the bit that does the graph. |
|
|
|
for btc mining it has no negative impact at all. you simply download the wallets and let them sync then add the .conf file as you would your Bitcoin.conf. just ensure you have the ports all different then use the --merged command when you start p2pool. --merged http://username:complexspassword@localhost:7333/ where 7333 is the port set for the coin you want to marge mine. |
|
|
|
|
that's the price we pay for being distributed. it does all work out even in the end apparently, just need some patience.
My first 2 weeks on p2pool have paid much more than I had got from larger pools and I'm only mining with 36gh/s! (again variance but it shows the p2pool can pay well even for small miners).
|
|
|
|
There are a lot of interesting files in ~/p2pool/data/bitcoin with intriguing names like graph_db and log and stats and such like.
I could just grab these files with sftp and extract the information I want once I have them here.
Where can I find documentation for the file formats?
that's its own databases for tracking shares etc after you restart a node. it'd be much easier to just pull the json files. Web interface
Lots of data and useful tools are available at http://127.0.0.1:9332/something:
/static/ - Lots of information from shares to graphs to payouts.
/rate
/users
/fee
/current_payouts
/patron_sendmany - Gives sendmany outputs for fair donations to P2Pool
/global_stats
/local_stats
/peer_addresses
/payout_addr
/recent_blocks
/uptime
/web/log - Some different stats collected over the last day
|
|
|
|
Does anybody know where p2pool puts its log files and what it calls them?
you need to specify that in the start up string. i.e. run_p2pool --logfile C:\p2pool-btc\logs\p2pool.log Aha. Thanks. Does it put the exact same stuff in the log file as it writes to the console? Yes it just dumps it's output. |
|
|
|
I have my nodes dashboard hosted on a separate web server and can access stats via standard http port. The code locally as well as remote does a json call.
All you need to do is reference the pools URL instead of local json sources. There is a bit of into on this and I've based my front end on the alternate front end on the githib page.
Have a look at the link in my sig and see if that's what you are after.
Let me know if you need more help with it.
That looks really slick, norgan! I had a look at the source code for your page... if there were any comments in it, I might be able to figure out what it does (my own code is at least half comments, otherwise I can't read it myself after a week or two). Care to explain it to me? haha yeah well it's a real mashup of the extended front end ( https://github.com/hardcpp/P2PoolExtendedFrontEnd) and some of my own code. It's pretty straight forward for the layout and the javascript is all from the goblin stats project. https://github.com/goblin/p2pool-stats/ |
|
|
|
Does anybody know where p2pool puts its log files and what it calls them?
you need to specify that in the start up string. i.e. run_p2pool --logfile C:\p2pool-btc\logs\p2pool.log |
|
|
|
|
quick question. when compiling how do you get the right version reported? I've compiled mine and it shows version f0eeb48. It should show 13.4-f0eeb48 or similar right?
|
|
|
|
Why don't you buy from bitmain directly?
I most likely will, they are great value. I guess I was just looking for someone cleaning out the closet as mentioned above. Miners hold value as long as they can roi and with low to no power cost I'm looking to roi within ~30 days. Thanks for everyone's input and to those who pm'd. Will make my decision this week and let you all know how I go. |
|
|
|
|
Amazon usually don't support shipping to Australia. Bitmain include shipping and are very good value. I was wondering if anyone was wanting to clear any that have already roi'ed and are just not feasible with power costs. I don't pay for power right now and hoping to squeeze some BTC out of them before they become completely useless.
|
|
|
|
|
Show Posts
