Topic: [1050 TH] BitMinter.com [1% PPLNS,Pays TxFees +MergedMining,Stratum,GBT,vardiff] - page 293. (Read 837101 times)

you're still alive)) 13 hours block!!!

Pool need PPS payment system too.

Yes, that will be in the API.

Off topic, but could you add an API to display worker hashrate and/or shares/min

Oh man this current block makes me cry. 9 hours and counting at 98.39% CDF... =//

Current rewards, i.e. balance/unconfirmed and historical rewards (i.e. sum of all payouts)

Thanks

No, there is only public data so far.

I am going to add an API with worker stats. What kind of data would you like to have accessible regarding earnings/payouts?

Is there no API for earnings/payouts?

When that day comes, I'd like to request a server in the Chicago area.

Hehe, I came home and looked at the screen, had to look twice to be sure I was reading the hashrate right. I've never seen a GPUMAX run that big before.

Thanks for doing such a big GPUMAX run, Fefox. It was a great test for the pool.

At 2.5 TH/s we had tiny memory usage, bandwidth usage with lots to spare and CPU usage barely above one core running full speed. The CPU has 4 cores + hyperthreading. So I feel fairly confident we can do well over 10 TH/s before reaching capacity.

What does this mean for ASICs? Maybe the server could handle ASICs as it is. I can't be sure as we now have many miners with big ASIC orders. But if we can "maybe" handle ASICs without changes, then we can handle them piece of cake once rollntime and higher difficulty work is up and running. Looking good!

Yes, we will add more servers in the future, but it's important to make the most of each server to keep costs down. Competition between mining pools is very tough.

Yes, it was a GPUMAX run, (No it was not a ASIC test) hehehe   just a stunt for race day and a test of the pool. that run @ 1.5 Th/s was so smooth...

got a bunch of private chats / msg's with people panicking that I was testing ASIC hahaha so I did a bit of teasing a few people claimed to have fallen out of their chair when they saw the hash rate...

so yes a great test, smooth as glass and Reject rates almost non-existent even after a block hits.

Congrats to both Bitminter and GPUMAX both are running perfect!  A++   

Looks to be a GPUMAX purchase.

Who is Fefox with 1.3TH? Holy Shit!

https://bitcointalksearch.org/topic/cryptostocks-bitbond-200ghs-105-pps-mining-bond-relaunched-75126

Absolutely this.

Although try telling p2Pool miners. I did a bunch of variance calculations in their thread for them showing a 95%CI effective hashrate for various actual hashrates and pool difficulties, but they're so focused on "enabling everyone to submit shares" they're ignoring how variance will affect them.

60 seconds per share will be way too infrequently if it's a static value. The variance will be painful. A minirig is the current highest hashrate device available and produces over 350 shares per minute. You would be setting current users to a difficulty of 350. The problem with that is the variance is the square of the difficulty so the variance will be much much higher and it would take weeks to get a stabilised return, when you are already capable of coping with hundreds of shares from the current minirig owners. To not make variance any more painful at high hashrates, make the share return rate proportional to the square root of the hashrate instead of a constant. So a 1 GH/s miner currently returns a share every 4.2 seconds - if you make the 1GH miners difficulty 10 as a baseline, then you make 10GH miners sqrt(10) * 10 ~ diff 30. And you make 100GH miners sqrt(100) * 10 ~ diff 100.

Yep, full rollntime support is coming first, then >1 difficulty work. These are the two simplest changes a pool can make to support higher hashrates. The more complex stuff will come later.

Higher difficulty work won't increase the efficiency of your hardware. It will reduce the number of requests you make to the server which is good. But it will also give you higher variance for your proofs of work. Your proofs of work per time (and hashrate estimate on website) will vary more than before. This can make it look like your hardware is running very quickly or very slowly (depending on luck) when watching the hashrate shown on the website.

I don't think it's a good idea to use difficulty 10 for everyone. Best is probably to set a goal for how often a miner should find a proof of work, and adjust the difficulty accordingly. It would be possible to let the user choose, but I think automating it makes things easier for the user. Maybe auto-adjust difficulty for each worker account so that you find a proof of work every X seconds on average?

At first I was thinking every 10 seconds, but maybe once every 60 seconds would be ok? Not sure if that creates too much variance for non-24/7 miners. If you are having a (network?) problem and you are watching the miner you also don't want to wait forever before something happens. But 60 seconds might be ok. It would totally break hashrate estimates on the website though. I think I'm talking myself into something like 10 seconds.

Nice to see old minters thinking about returning. I believe some already did as the hashrate went up. Low hashrate seemed to be the main reason that people left.

So, are you guys going to add rollntime support for cgminer? Because I'm using only cgminer  . Also, it appears that difficulty 10 shares increase the hardware efficiency, judging from what I get from mining on diff10 server at eclipse. Hope you guys would do something like that as well. Your pool was the first one I tested out with my gpu's, when I just found out about bitcoin  

P.S. Actually, could you please post here your server ip address, so I could try your pool =)

I remember seeing him on MaxBTC with (I think) ~80GH. Looks like he's down to ~10GH on there now.

Who is amazinggrando? he just showed up on minter looks like maybe a 3 Minirig setup?

and Giga is back! 

Almost at 1000GH!!