Jcw188
|
 |
May 16, 2013, 09:12:51 PM |
|
are we down? update please
|
|
|
|
|
|
|
|
The Bitcoin software, network, and concept is called "Bitcoin" with a capitalized "B". Bitcoin currency units are called "bitcoins" with a lowercase "b" -- this is often abbreviated BTC.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
juhakall
|
 |
May 16, 2013, 09:28:18 PM |
|
There have been a few outages today, lasting only a minute or so. Works ATM.
|
|
|
|
philipma1957
Legendary
Online
Activity: 3766
Merit: 5735
|
 |
May 16, 2013, 10:00:23 PM |
|
My 7870xt arrived early  Signed up for bitminter, I tried using the Java client, it kept crashing when starting mining with gpu, but worked when mining with cpu. I'm familiar with Guiminer, so I went back to that for now, using the basic flags -v -w 128 Gpu core Oced to 1100mhz mem stock 1500 I'm getting 450Mhash/s which is within range of normal for this card. Using BTC-e as a wallet for both BTC and NMC I've got more reading to do but any tips on anything BTC? If you are mining bitcoin you don't need beefy memory speeds, thats more a litecoin thing. For bit I run engine at 1200 and mem at 1050. (Sapphire 7950's, Linux, cgminer 3.1.1 & 3.0.0) If you are in windows you can downclock the memory speed even more using third party apps. Downclocking memory might give you some extra wiggle room to bump the engine speeds up a bit more, or just help lower card temps/fan speeds. CORRECT if your card lets you go to 900 memory do it. I run my miner only 7970's with 700 memory and lower the ram volts to 1.5. I also underclock the hd7970's to .92 volts for the core and set the core to 885 yeah it hashes less maybe only 500 or 520 and not 650 but the summer is coming and it is getting hot. the lower setting really drops power use down. All my hd7790's are locked for volts I set them at 1050 core and 800 memory they hash at a max of 300 and pull 80 watts.
|
|
|
|
GuiltySpark343
Member

Offline
Activity: 98
Merit: 10
|
 |
May 16, 2013, 10:41:15 PM |
|
I'm confused by the prepay donation/perk.
If you read the perk, it states that "Immediate pay for bitcoin blocks. No waiting for 120 confirmations. No lost coins if the block is later orphaned. Note: does not apply to stale blocks."
Yet, if you read the Blocks (income) page, at the top it states "If the block is orphaned upon creation it will be listed as stale."
So ... one page says if a block is orphaned, it is listed as stale. The other page states that prepay does not apply to stale blocks yet no lost coins if block is orphaned?!? I'm going around in circles here ...
|
|
|
|
matt4054
Legendary
Offline
Activity: 1904
Merit: 1026
cryptoscaper.com
|
 |
May 17, 2013, 12:21:32 AM |
|
I'm confused by the prepay donation/perk.
If you read the perk, it states that "Immediate pay for bitcoin blocks. No waiting for 120 confirmations. No lost coins if the block is later orphaned. Note: does not apply to stale blocks."
Yet, if you read the Blocks (income) page, at the top it states "If the block is orphaned upon creation it will be listed as stale."
So ... one page says if a block is orphaned, it is listed as stale. The other page states that prepay does not apply to stale blocks yet no lost coins if block is orphaned?!? I'm going around in circles here ...
There is a simple answer, though I'm not 100% sure about this: orphaned upon creation != orphaned later on. The latter are listed as 'orphaned' in the block list, and they are quite rare compared to the former (orphaned upon creation == stale).
|
|
|
|
juhakall
|
 |
May 17, 2013, 01:20:48 AM |
|
I believe a block is marked stale if it gets rejected by BitMinter's bitcoind. That could happen if the server that's handing out work tries to submit a block without being made aware of a new block just received by the bitcoind. That delay should be very small, but it's still something. Latency between the work server and actual miners is obviously bigger. If a miner submits a block that's known to be stale by the work server, the server should just discard the block without trying to submit it to bitcoind. Do those kind of blocks get marked stale, too?
An orphan block gets distributed to the network at least partly, until it's later abandoned because some other block minted at roughly the same moment got distributed faster or just got plain lucky. A stale block is totally unseen by all nodes.
|
|
|
|
rnaodm
Member

Offline
Activity: 61
Merit: 10
|
 |
May 17, 2013, 02:22:24 PM |
|
About 48hrs straight mining, 515Mhash/s only sitting .021 BTC, This about right? Seems real low.
|
|
|
|
fredtrader
Newbie
Offline
Activity: 56
Merit: 0
|
 |
May 17, 2013, 02:30:07 PM |
|
About 48hrs straight mining, 515Mhash/s only sitting .021 BTC, This about right? Seems real low.
Sounds about right, I believe difficulty went up quite a bit recently
|
|
|
|
rnaodm
Member

Offline
Activity: 61
Merit: 10
|
 |
May 17, 2013, 02:38:47 PM |
|
About 48hrs straight mining, 515Mhash/s only sitting .021 BTC, This about right? Seems real low.
Sounds about right, I believe difficulty went up quite a bit recently hm thanks, at this rate it'll be 100 days before I earn one BTC, Pretty disappointing. The only ones making money are pool owners and ASIC miners, Whats to keep BTC afloat if 95% of current miners no longer find it viable
|
|
|
|
fredtrader
Newbie
Offline
Activity: 56
Merit: 0
|
 |
May 17, 2013, 02:57:35 PM |
|
About 48hrs straight mining, 515Mhash/s only sitting .021 BTC, This about right? Seems real low.
Sounds about right, I believe difficulty went up quite a bit recently hm thanks, at this rate it'll be 100 days before I earn one BTC, Pretty disappointing. The only ones making money are pool owners and ASIC miners, Whats to keep BTC afloat if 95% of current miners no longer find it viable I think mining will become more and more centralized, the only thing breaking this tendency is small ASIC's like the USB ones sold by friedcat, but in the long term the only ones with access to cost affordable ASICs will be those buying in bulk.
|
|
|
|
redtwitz
|
 |
May 17, 2013, 03:01:57 PM |
|
About 48hrs straight mining, 515Mhash/s only sitting .021 BTC, This about right? Seems real low.
515,000,000 hashes/s = 515,000,000 / 2^32 shares/s = 0.119907781 shares/s = 20,720 shares/48h At the current difficulty, ignoring pool fee and tx fees, that should be about 20,720 / 11,187,257.4614 * 25 BTC = 0.04630268 BTC.
|
|
|
|
rnaodm
Member

Offline
Activity: 61
Merit: 10
|
 |
May 17, 2013, 03:03:59 PM |
|
About 48hrs straight mining, 515Mhash/s only sitting .021 BTC, This about right? Seems real low.
Sounds about right, I believe difficulty went up quite a bit recently hm thanks, at this rate it'll be 100 days before I earn one BTC, Pretty disappointing. The only ones making money are pool owners and ASIC miners, Whats to keep BTC afloat if 95% of current miners no longer find it viable I think mining will become more and more centralized, the only thing breaking this tendency is small ASIC's like the USB ones sold by friedcat, but in the long term the only ones with access to cost affordable ASICs will be those buying in bulk. If BFLabs actually catches up, and has units available to sell, a $275 gpu will do 600Mhash, a $275 ASIC will do 5Ghash/s
|
|
|
|
rnaodm
Member

Offline
Activity: 61
Merit: 10
|
 |
May 17, 2013, 03:05:38 PM |
|
About 48hrs straight mining, 515Mhash/s only sitting .021 BTC, This about right? Seems real low.
515,000,000 hashes/s = 515,000,000 / 2^32 shares/s = 0.119907781 shares/s = 20,720 shares/48h At the current difficulty, ignoring pool fee and tx fees, that should be about 20,720 / 11,187,257.4614 * 25 BTC = 0.04630268 BTC. So by your math I'm making less then Half then I should be, bleh.
|
|
|
|
fredtrader
Newbie
Offline
Activity: 56
Merit: 0
|
 |
May 17, 2013, 03:09:54 PM |
|
About 48hrs straight mining, 515Mhash/s only sitting .021 BTC, This about right? Seems real low.
515,000,000 hashes/s = 515,000,000 / 2^32 shares/s = 0.119907781 shares/s = 20,720 shares/48h At the current difficulty, ignoring pool fee and tx fees, that should be about 20,720 / 11,187,257.4614 * 25 BTC = 0.04630268 BTC. So by your math I'm making less then Half then I should be, bleh. According to http://www.bitcoinx.com/profit at the current difficulty you should make 0.0232 per 24h and I believe that doesn't count pool fees.
|
|
|
|
rnaodm
Member

Offline
Activity: 61
Merit: 10
|
 |
May 17, 2013, 03:18:19 PM |
|
About 48hrs straight mining, 515Mhash/s only sitting .021 BTC, This about right? Seems real low.
515,000,000 hashes/s = 515,000,000 / 2^32 shares/s = 0.119907781 shares/s = 20,720 shares/48h At the current difficulty, ignoring pool fee and tx fees, that should be about 20,720 / 11,187,257.4614 * 25 BTC = 0.04630268 BTC. So by your math I'm making less then Half then I should be, bleh. According to http://www.bitcoinx.com/profit at the current difficulty you should make 0.0232 per 24h and I believe that doesn't count pool fees. yea, I know that my 7870 isn't a beastly miner and I came back to bitcoin way too late, a bit disappointing all around. thanks for that link, Ill keep a close eye on future profits.
|
|
|
|
juhakall
|
 |
May 17, 2013, 09:13:05 PM |
|
Assuming normal luck all the time, you will never reach 100% expected payout while mining. That's because of the delay in PPLNS, and the delay in block confirmations if you disabled the prepay perk. You will only reach 100% expected payout after you have stopped mining and received all the delayed payouts. This delay is pretty close to 1 day if you have the prepay perk disabled. I heard it's enabled by default now, though.
|
|
|
|
GuiltySpark343
Member

Offline
Activity: 98
Merit: 10
|
 |
May 17, 2013, 11:44:07 PM |
|
@DrHaribo Can you please add Idle Worker Notification to Bitminter? 
|
|
|
|
Zillions
|
 |
May 18, 2013, 03:13:19 AM |
|
Hey would it be possible once AISC's take over BTC mining that Mitminter could release a LTC version of the mining client? I find all the scrypt mining really unweildly and I don't trust the proxy that alot require.
|
|
|
|
GuiltySpark343
Member

Offline
Activity: 98
Merit: 10
|
 |
May 18, 2013, 03:26:43 AM |
|
Proxy is only required for miner clients that don't support stratum. CGMiner supports stratum for scrypt, so just use that.
|
|
|
|
DrHaribo (OP)
Legendary
Offline
Activity: 2716
Merit: 1034
Bitminter.com Operator
|
 |
May 18, 2013, 09:31:12 AM |
|
I believe a block is marked stale if it gets rejected by BitMinter's bitcoind. That could happen if the server that's handing out work tries to submit a block without being made aware of a new block just received by the bitcoind. That delay should be very small, but it's still something. Latency between the work server and actual miners is obviously bigger. If a miner submits a block that's known to be stale by the work server, the server should just discard the block without trying to submit it to bitcoind. Do those kind of blocks get marked stale, too?
That's right. Orphaned blocks at BitMinter are what other pools show as orphan or "invalid". The stale blocks at BitMinter are of a type not shown at any other pools as far as I know. Yes, when a worker sends in stale work that could have created a block, that's listed as a stale block. Perhaps this is only demoralizing and should be hidden from the users, like other pools do. A lot of miners don't understand that BitMinter has one of the very highest payouts you can get from a pool. If the payouts are among the very best but some users think they are among the worst, then I definitely need to do something about how data is presented on the website. Assuming normal luck all the time, you will never reach 100% expected payout while mining. That's because of the delay in PPLNS, and the delay in block confirmations if you disabled the prepay perk. You will only reach 100% expected payout after you have stopped mining and received all the delayed payouts. This delay is pretty close to 1 day if you have the prepay perk disabled. I heard it's enabled by default now, though.
Yeah, getting 20 confirmations takes about 20 hours. That's needed if you have the prepay perk turned off. Also there is the PPLNS delay. For your work to be fully paid the shift they are recorded in must be finished, plus 10 more shifts. An average of 10.5 shifts. Currently shifts take about 27 minutes, so that's a delay of about 4 hours and 40 minutes from the work is done until it is fully paid. So yes, without prepay the total delay from doing work to getting full pay is currently 24 hours and 40 minutes. Having half the expected income when half your work has been paid sounds correct. Can you please add Idle Worker Notification to Bitminter?  Yep, that's coming soon.
|
|
|
|
|