With current network hash rate, would that not being closer to 400,000 to 1 ?
Hashrate: 336 Average generation time for a block (solo): 4 years, 338 days = 1798 days 1798 / 30 = 59.93 Right ? Every day independent trial. Each block independent trial. Mining for 30 days just 30 iterations of one block in 1798 days or 1 chance to find block in every 431,520 next blocks over and over again. Not additive. No more chance to find block after 1 year of mining as when starting - being actually much less because of weekly difficulty increases. Not as likely as you might be thinking - could easily mine for 25 years and not be finding block. Finding block solo at that rate about 3.5 sigma event. Difference between 3.5 and 4 sigma events is being very small difference in probability-wise but large time-wise - from once every six years to possibly twice in a lifetime and not difficult to stretch out to sigma 4.5 making once every 4 centuries. Can only say results not being average after 1.4 million years of testing - should find block within 6 sigma - if not, average calculation probably wrong. In meantime straight PPS should paying in your pocket about 18 BTC over same period you mentioning.
|
|
|
With current network hash rate, would that not being closer to 1 in 400,000 ?
|
|
|
Placing pre-order for 10 more units. Not being a problem sending to my brother's address in USA, right?
|
|
|
Am be putting in pre-order for 5. If it would be helping, I could be preordering another 10. Could also be picking up any units from first batch that pre-order person not taking.
|
|
|
Pool has go crazy? Negative hash rates? Block length -1 day 22 hours? Scores 20 digits long?
|
|
|
At least peoples are having some credit on block 18218. Am receiving NOTHING for that block even when mining for whole time. Then being back to normal on next: 18218 2013-05-25 22:58:32 0:25:35 3754815 none none 237928 25.00650000 18219 2013-05-25 23:31:47 0:33:15 4923475 818 0.00425312 237930 25.21042000 then missing ALL BUT ONE shares on 18223. WTF 18223 2013-05-26 09:16:33 1:24:44 12500488 1 0.00000000 237996 25.10896011
|
|
|
Is some issue with score not resetting to zero at start of 18221 round or problem with estimated? Estimated score for this round being about 1/40 normal, .00010 instead .0044 ever since starting.
Ah. I see it is happening with the present block. I'm back up to almost 50% of normal as it slowly fixes itself. Slowly fixing self little bit over last 1/2 hour. Maybe back close to normal if block going another 1/2 hour or longer.
|
|
|
Is some issue with score not resetting to zero at start of 18221 round or problem with estimated? Estimated score for this round being about 1/40 normal, .00010 instead .0044 ever since starting.
|
|
|
In essence each share gets a "score". The score is highest at the round end, and earlier shares get lower scores. The older the share the lower the score. And that progression is not linear but exponential, so score goes down to almost zero very quickly. From observations I think the cut-off is about an hour - for shares older than an hour you get absolutely no score.
Not argue, you are correct. Just giving information about cut-off also being based on observation: Cutoff not exactly being one hour or based on time. Cutoff depending on total Slush pool hash rate and when score being renormalized after hitting 14 significant digits. Renormalize used be happening just over one hour when hash rate was about 9Tb. With current hash rate renormalize happening about each 52 minutes. Am thnking is why some rewards suddenly crash to .00000007 if being no shares submitted exactly between renormalize and round ending. Few shares at normal rate in seconds after renormalize taking reward back to full for next scoring period, but scores in round also decrease very quickly by not submitting shares at constant rate all time.
|
|
|
Started a new miner and it says io errors -1, tolerance 2
Is often happen with GUIminer. Check if another already running. They hide - not showing in taskbar but in notification icons.
|
|
|
I love your accent
Am knowing not speaking American very well but not liking me speak Russian here. Thank you.
|
|
|
Not complicated. Just needing this information. http://stratum.bitcoinz.com (or stratum2 or stratum3) your worker name your worker password Appearing like so in config file under pools: { "url" : " http://stratum.bitcoin.cz:3333", "user" : "rsbriggs.worker1", "pass" : "*******" } First time running cgminer, it will prompt for URL, user, and password. Please be learning by trying first, then asking questions if not understanding something. Answers not useful if asker not first understanding question they asking. Nearly all else in normal cgminer config file will depending on your graphics card hardware, being GPU related and not relevant. Defaults in config file should be sufficient to start. Anything else ASIC related needing, see file in cgminer directory: ASIC-README.txt
|
|
|
I have noticed my average has gone down a bit lately. Is this because we have more miners on lately or did the difficulty change or is it just my bad luck?
It also appears that I got the short end of the stick on a couple blocks. Not sure if it is on my end or not.
Anyone else notice the same or is it me?
Be going back 10 pages and reading. Or back 15, 20, 30, or even 50 pages and reading....
|
|
|
What are your guys pings to the server, i feel i get less shares on this new server then the previous on short blocks (granted difficulty has got up 1-2 times since then) Im from ontario, canada just for refrence.
stratum1.bitcoin.cz i ping about 75ms
api.bitcoin.cz:8332 i ping about 120ms
i obvously use stratum address, i also tried directly towards some of the listed ip address's its the same as stratum address.
with a tracert to the server i get some timing out after it hits amazons servers, anyone else?
Probably disabling ICMP packets like ping as anti-DOS measure, or just not wanting to allow spying on architecture.
|
|
|
cgminer 3.1.1 says for this entry: Pool 1 invalid URL. Trying many IPs - not work. Have 10 hostnames in cgminer.conf - all working fine.
Am thnking Windows cgminer not taking IP addresses. Am also thinking is Windows issue having different gethostbyname() function call to UNIX:
gethostbyname Function in the API
The gethostbyname function uses the WSALookupServiceBegin function to query SVCID_INET_HOSTADDRBYNAME as the service class GUID. ... Returns addressing information from HOSTENT in CSADDR_INFO structures, port information is defaulted to zero. Note that this routine does not resolve host names that consist of a dotted IPv4 address.
That BOLD part is saying you cant use direct IP's. I am not familiar with cgminer in the unix environment so cant help beyond that. However if you know UNIX you can edit the hosts which is generally located in /etc aka vi /etc/hosts and add something like 54.225.68.97 ip1.slush.local 54.225.117.74 ip2.slush.local may have to hup inetd. then use ip1.slush.local in cgminer script. see if that works. I haven't messed with unix resolving in a long time so I am just going by memory. Am familiar with UNIX/Linux and variants but using Windows7 to mine. Edited c:/windows/system32/drivers/etc/hosts file, added list. Can use ip1-9.slush.com now to specify IP. # localhost name resolution is handled within DNS itself. # 127.0.0.1 localhost 54.225.116.174 ip1.slush.com 54.225.117.74 ip2.slush.com 54.225.116.40 ip3.slush.com 54.215.3.101 ip4.slush.com 54.215.3.102 ip5.slush.com 54.225.116.221 ip6.slush.com 54.225.68.97 ip7.slush.com 54.215.3.103 ip8.slush.com 54.215.3.100 ip9.slush.com
|
|
|
cgminer 3.1.1 says for this entry: Pool 1 invalid URL. Trying many IPs - not work. Have 10 hostnames in cgminer.conf - all working fine.
Am thnking Windows cgminer not taking IP addresses. Am also thinking is Windows issue having different gethostbyname() function call to UNIX:
gethostbyname Function in the API
The gethostbyname function uses the WSALookupServiceBegin function to query SVCID_INET_HOSTADDRBYNAME as the service class GUID. ... Returns addressing information from HOSTENT in CSADDR_INFO structures, port information is defaulted to zero. Note that this routine does not resolve host names that consist of a dotted IPv4 address.
|
|
|
Can be using IP addresses directly in cgminer? How config file entry look?
|
|
|
I also experienced a near 80% rewards drop for block 237575. Until Slush chimes in, we can only speculate that some sort of hardware error occurred during that window of time including blocks 237573 and 237574. It's a shame to see BTC just vanish into oblivion.
Am also having big drop - almost 2 orders magnitude - for 237575. Average reward being .0045 Reward for 237575 being .000084421. Similar situation blocks 237642 and 237540. Work for 237574 gone disappeared. Rewards on before and after sides of problem blocks seeming normal.
|
|
|
To be quoting American TV hero Homer Simpson ....D'oh.... Original correct - block missing.
|
|
|
|