|
The expected generation output, from 1000 Mhps, at current difficulty 1155038.3339636, is 0.8708 BTC per day or 0.0363 BTC per hour.
0,8708 btc >> 61 WMR
|
|
|
|
|
SMPPS or ESMPPS method this pool runs?
|
|
|
|
can you strip miner code from cgminer, auto-over/under/clocking and fan management looks useful for gaming
Well there's already AMDOverdriveCtrl for Linux that does this on it's own. Are you sure there aren't already plenty of standalone windows apps that do that also? games are for windows  well I haven't seen such a combination - auto-fan speed + dynamic overclocking to maintain target GPU temp, most tools are for setting static overclock and fiddling with fan profiles  |
|
|
|
|
you could get appointed CEO of apple if you quit your current job - Victim of Internet
if you have problems with your ego, quit reading forums and visit your shrink
|
|
|
|
|
I was running 0.3.2x something, but 10 to 20 connections is too low, no idea how v0.4.0 is done, but I was getting like at least 50 to 70 at a time
|
|
|
|
|
why don't you get it - that pool script is SHIT, ram walls with your head, damn twit
|
|
|
|
|
IMHO that script is crap, see, you have 6% server load with 1,6Ghash/s, with 100Ghash/s you will have ... OOOPS server going down
|
|
|
|
|
can you strip miner code from cgminer, auto-over/under/clocking and fan management looks useful for gaming
|
|
|
|
|
I had no problems with 10 miners/about 4Ghash/s with server ip put in DMZ, read some logs, it could be memory failure, overheating cpu, bad NIC, bad NIC drivers, missconfigured router, lack of free space on c:
|
|
|
|
|
do you see small spikes, those are full time miners having connection problems, changing prop method will screw their average payouts if pool is too small
|
|
|
|
The only inconvinience is that the wallet password must be supplied every time when starting bitcoin client, not only when sending coins. Which totally defeats the purpose of wallet encryption. If you're going to do it that way, you might as well just encrypt on backup only (which would be a very nice feature anyway...) The encryption of only private keys are no solution either. Just wait until victim sends the coins to someone, then recover the password using keylogger. It can only protect against trivial attacks such as grabbing the wallet.dat file right away. There is no real way of securing the wallet.dat file on compromised computer. But if I use encryption, I would like the whole wallet.dat to be encrypted, so even if shit hits the fan and my wallet.dat is leaked, all my adresses are not disclosed to attacker. put virtual keyboard in client, so user picks letters/symbols with a mouse and keyloggers defeated |
|
|
|
Variance is probably the biggest factor, but there are some things to consider.
If your pool is being abused by poolhoppers than your income is probably taking a massive hit. Avoid this - don't give away your money to pool hoppers.
not true, see how itzod ran from hoppers, see bitp, I can add some shut down pools too all miners are hoppers, they join lucky pools and quit unlucky, no matter proportional or some-twisted-shit method pool ops use. |
|
|
|
|
your survey is invalid, 80% of those who didn't vote obviously do not want any changes otherwise they would vote, rest who voted are 54% vs. 46%
if you want a change - do it, but don't claim it was voted for, let's see what happen with those 80% that haven't voted, will they leave or stay?
|
|
|
|
|
why are you complaining then, maybe that 13M shares block is close and you know it.
|
|
|
|
By the way, I am kinda disappointed to see quite a few miners leave after the queue went from positive to negative and instant rewards have gone for now.
read #65 & #66, and next time ask yourself some simple questions - "what if ..." |
|
|
|
|
pool luck meter formula is wrong
Average shares per block: 1670916 (-5.1%)
Average in last 24 hours: 2011670 (+12.7%)
(1 - 1670916/1755425)*100= -4.81%
(1 - 2011670/1755425)*100= +14.59%
|
|
|
|
The shitty thing is that if you have a decent CPU the "CPU big" is costing a lot of wasted wattage.
Restricting CGMiner to a single core (@ 100%) reduced power consumption at the wall by 40W. Make me think we would save another ~10W if it had no CPU bug.
Is there any way to setup an "automatic CPU afinnity?". i.e. anytime program "CGMINER.EXE" launches it is restricted to core #3?
for win7, use shortcut like that: C:\Windows\System32\cmd.exe /c start /affinity 2 /d C:\bitcoin\phoenix-1.60 C:\bitcoin\phoenix-1.60\phoenix.exe -u http://user:pass@localhost:8332 -k phatk DEVICE=0 VECTORS AGGRESSION=12 BFI_INT WORKSIZE=256 -q 1 affinity 2 is 3rd core |
|
|
|
|
count shares per day, 3 days shares would be even more accurate
|
|
|
|
|
I don't want to create accounts, or even make one share for each account
if I have 90% of all shares, I could win only once, totally unfair for accounts with large computing power, that is the reason your pool won't grow, you have to be average or you will be penalized...
|
|
|
|
|
Show Posts
