[ANN] US/North American Bitfury sales NEW STOCK ***NOW SHIPPING***

[Micky25]

if you bought from BFSB

[mo_mo]

Has anyone received an email from Dave for the compensation for the late Aug. deliveries?

[skrazy]

Has anyone received an email from Dave for the compensation for the late Aug. deliveries?

Yes but it did not include any details on how much we'd receive for either option.

"Hello and thanks for your patience while we sorted out our supply issues for starter kit M-boards.

Now that the kits have all shipped out for August delivery purchases, I need to send you the coin we mined on your behalf during the period your hardware was delayed.

Please follow these instructions carefully in order to insure you get paid.

#1 Please don't reply to this email - Yvonne is collecting payment addresses and organizing them for me.
#2 Send your BTC payment address *from the email on your account* - please make sure to follow this one.  If your payment address arrives from any other email, we will ignore it.  Send the payment address to sales@megabigpower.com
#3 You can choose store credit if you prefer.  I'll give an extra BTC of store credit value to anyone who chooses this option.

Thanks again for all your patience and support through our August ship cycle!  We learned a lot and plan to leverage that experience to improve our October shipfest coming soon.

All the best and thank you so much for being customers!
Dave Carlson
megabigpower.com"

[dresdenreader]

Thanks again for all your patience and support through our August ship cycle!  We learned a lot and plan to leverage that experience to improve our October shipfest coming soon.

Can't wait = )

[tom99]

   My miner stop working 6 hrs ago and I found out SD card gone bad.  I am going to dowload SD image that suck.

ps: 3.7Gb filesystem cant mount in Ubuntu that why image gone bad.  I am back to mining now and I had to start write new image to sd card then changed ip address.

[zurg]

   My miner stop working 6 hrs ago and I found out SD card gone bad.  I am going to dowload SD image that suck.

ps: 3.7Gb filesystem cant mount in Ubuntu that why image gone bad.  I am back to mining now and I had to start write new image to sd card then changed ip address.

Huh, mine went bad on Friday.., had to reload the card.
Now even after formatting and reloading it popped an error on the prompt
https://dl.dropboxusercontent.com/u/10948184/BF-Pi-Error.jpg
Maybe they got a batch of soon to be faulty cards? Either way I bought 2 cards and a spare Raspberry Pi at Microcenter yesterday just in case.

[superduh]

so august shipping was end of august beginning of sept and oct shipping is going to be sometime in beginning.
can't please everyone in bitcoin world but you can def hurt people. if oct ships in beginning august orders were substantially overpriced

[-Redacted-]

Bull crap.  October shipping is October shipping, whether it's the 1st, or the 30th.  Not relevant to people that bought September shipping - they either got shipped in September at the price they agreed to buy at, or didn't.  Nothing in October has anything whatsoever to do with September shipping...

[nullspot]

so august shipping was end of august beginning of sept and oct shipping is going to be sometime in beginning.
can't please everyone in bitcoin world but you can def hurt people. if oct ships in beginning august orders were substantially overpriced

Are we doing this again? You can't "hurt" people who have already received their products by shipping other orders on time or early. Everyone who placed orders for *any* batch took a calculated risk, not knowing the future. The prices reflected the opportunity, nothing more.

Hypothetically, if every August batch order had shipped exactly on Aug. 31st, but the October batch orders didn't ship until November 15th, due to typhoons disrupting Asian supply routes -- or a cockroach got stuck in a PCB machine, disrupting production, would you also claim that the October customers were "hurt" by the on-time delivery of August batch? Bullshit. You don't penalize one set of customers unnecessarily just to "spread the misery" because another set of customers had unfortunate luck.

[dacman61]

Kit #1:   3 cards:
1: 30.609GH/s
9: 31.339GH/s
13: 29.335GH/s

Kit#2:  2 cards:
Bank 1
1: 30.723GH/s
9: 30.093GH/s


i penciled the resistor to about 1230ohms.


Should I have done that or go lower?

I was able to do 1.18k Ohm... I've been steady at around 33Gh/s.

[superduh]

so august shipping was end of august beginning of sept and oct shipping is going to be sometime in beginning.
can't please everyone in bitcoin world but you can def hurt people. if oct ships in beginning august orders were substantially overpriced

Are we doing this again? You can't "hurt" people who have already received their products by shipping other orders on time or early. Everyone who placed orders for *any* batch took a calculated risk, not knowing the future. The prices reflected the opportunity, nothing more.

Hypothetically, if every August batch order had shipped exactly on Aug. 31st, but the October batch orders didn't ship until November 15th, due to typhoons disrupting Asian supply routes -- or a cockroach got stuck in a PCB machine, disrupting production, would you also claim that the October customers were "hurt" by the on-time delivery of August batch? Bullshit. You don't penalize one set of customers unnecessarily just to "spread the misery" because another set of customers had unfortunate luck.

you are 100% (not even a fraction less) wrong about this. no point trying to explain to you since it seems you can't understand. it was implied several times that october orders were going to be shipped towards the end of october. this is a *zero-sum game* and you are 100% wrong - i'm surprised you can't even see the actual logic behind this.

also, your example about delays doesn't even make any sense. the people hurt by that delay would be oct orders and not august orders at all since people in october knew with certainty about delivery of august units first. yikes.

if you read my post correctly you will see that i'm not demanding or asking for anything i'm just stating facts.

[klondike_bar]

Kit #1:   3 cards:
1: 30.609GH/s
9: 31.339GH/s
13: 29.335GH/s

Kit#2:  2 cards:
Bank 1
1: 30.723GH/s
9: 30.093GH/s

i penciled the resistor to about 1230ohms.

Should I have done that or go lower?

I was able to do 1.18k Ohm... I've been steady at around 33Gh/s.

I tuned down to 1.165k, getting around 35Ghash, and 33Ghash/noncerate at the pool. Amazingly, chip #13 which was running at ~300mhash with tons of errors now works just fine.

[-Redacted-]

so august shipping was end of august beginning of sept and oct shipping is going to be sometime in beginning.
can't please everyone in bitcoin world but you can def hurt people. if oct ships in beginning august orders were substantially overpriced

Are we doing this again? You can't "hurt" people who have already received their products by shipping other orders on time or early. Everyone who placed orders for *any* batch took a calculated risk, not knowing the future. The prices reflected the opportunity, nothing more.

Hypothetically, if every August batch order had shipped exactly on Aug. 31st, but the October batch orders didn't ship until November 15th, due to typhoons disrupting Asian supply routes -- or a cockroach got stuck in a PCB machine, disrupting production, would you also claim that the October customers were "hurt" by the on-time delivery of August batch? Bullshit. You don't penalize one set of customers unnecessarily just to "spread the misery" because another set of customers had unfortunate luck.

you are 100% (not even a fraction less) wrong about this. no point trying to explain to you since it seems you can't understand. it was implied several times that october orders were going to be shipped towards the end of october. this is a *zero-sum game* and you are 100% wrong - i'm surprised you can't even see the actual logic behind this.

also, your example about delays doesn't even make any sense. the people hurt by that delay would be oct orders and not august orders at all since people in october knew with certainty about delivery of august units first. yikes.

if you read my post correctly you will see that i'm not demanding or asking for anything i'm just stating facts.

No.  YOU are the one 100% wrong here.   Sorry.   It's too bad you feel like you are being hurt because you choose to interpret October shipping in a particular manner.  And BTC is not a zero sum game - just because someone else gets one doesn't mean that you get zero.   

[Ridicuss]

i penciled the resistor to about 1230ohms.

Should I have done that or go lower?

I was able to do 1.18k Ohm... I've been steady at around 33Gh/s.

I tuned down to 1.165k, getting around 35Ghash, and 33Ghash/noncerate at the pool. Amazingly, chip #13 which was running at ~300mhash with tons of errors now works just fine.

Interesting observation on the chip 13. Maybe similar to Asic miner Blade issues.  Unless there is a bad lane on Blades you can usually get a non functioning chips running with a bit more voltage. On the old blades that is.

[murraypaul]

And BTC is not a zero sum game - just because someone else gets one doesn't mean that you get zero.

BTC mining is a fixed-sum game, so the constant race to increase hashpower is a zero-sum game.
For you to get an increased proportion of the 25 BTC plus transaction fees, everyone else must get a slightly decreased proportion.

[skrazy]

Kit #1:   3 cards:
1: 30.609GH/s
9: 31.339GH/s
13: 29.335GH/s

Kit#2:  2 cards:
Bank 1
1: 30.723GH/s
9: 30.093GH/s

i penciled the resistor to about 1230ohms.

Should I have done that or go lower?

I was able to do 1.18k Ohm... I've been steady at around 33Gh/s.

I tuned down to 1.165k, getting around 35Ghash, and 33Ghash/noncerate at the pool. Amazingly, chip #13 which was running at ~300mhash with tons of errors now works just fine.

I had a similar issue with one chip on an h-card. When I changed the resistance to 1.2k the chip went from ~0.100 to 2.000. That said I did need to clock it lower than the rest of the chips to achieve a reasonable error rate. At 53 it throws about 4% errors.

[goxed]

  My miner stop working 6 hrs ago and I found out SD card gone bad.  I am going to dowload SD image that suck.

ps: 3.7Gb filesystem cant mount in Ubuntu that why image gone bad.  I am back to mining now and I had to start write new image to sd card then changed ip address.

My second SDcard got screwed as well. Had to connect the first SD card to make an image and then re-mage the second one. Since I didnt' have a SD card reader, used my digicam as one

[superduh]

so august shipping was end of august beginning of sept and oct shipping is going to be sometime in beginning.
can't please everyone in bitcoin world but you can def hurt people. if oct ships in beginning august orders were substantially overpriced

Are we doing this again? You can't "hurt" people who have already received their products by shipping other orders on time or early. Everyone who placed orders for *any* batch took a calculated risk, not knowing the future. The prices reflected the opportunity, nothing more.

Hypothetically, if every August batch order had shipped exactly on Aug. 31st, but the October batch orders didn't ship until November 15th, due to typhoons disrupting Asian supply routes -- or a cockroach got stuck in a PCB machine, disrupting production, would you also claim that the October customers were "hurt" by the on-time delivery of August batch? Bullshit. You don't penalize one set of customers unnecessarily just to "spread the misery" because another set of customers had unfortunate luck.

you are 100% (not even a fraction less) wrong about this. no point trying to explain to you since it seems you can't understand. it was implied several times that october orders were going to be shipped towards the end of october. this is a *zero-sum game* and you are 100% wrong - i'm surprised you can't even see the actual logic behind this.

also, your example about delays doesn't even make any sense. the people hurt by that delay would be oct orders and not august orders at all since people in october knew with certainty about delivery of august units first. yikes.

if you read my post correctly you will see that i'm not demanding or asking for anything i'm just stating facts.

No.  YOU are the one 100% wrong here.   Sorry.   It's too bad you feel like you are being hurt because you choose to interpret October shipping in a particular manner.  And BTC is not a zero sum game - just because someone else gets one doesn't mean that you get zero.  

dude, you seem intelligent in certain ways but not all ways. it was initially stated/hinted that october deliveries would be towards the end of month (fact).  i'm not interpreting i'm just repeating facts of what was mentioned. and yes the last fucking sentence you say is true  in a way that - the more *other people* getting btc the chance of august orders getting btc approaches zero.. how many people on here don't have any clue about economics or math or statistics or just basic 1+1 skills. i'm right, you're wrong, get over it and let me say my facts without badly conceived
harassment.

i also assume people here don't understand what this idea is for some odd reason - http://en.wikipedia.org/wiki/Zero-sum_game

let's not spend time trying to distort reality. instead focus on the future- regardless, October will likely not ROI either
btw, out of pure curiosity i wonder how many people knew about 200th from bitfury 's private pool coming online.

[klondike_bar]

Kit #1:   3 cards:
1: 30.609GH/s
9: 31.339GH/s
13: 29.335GH/s

Kit#2:  2 cards:
Bank 1
1: 30.723GH/s
9: 30.093GH/s

i penciled the resistor to about 1230ohms.

Should I have done that or go lower?

I was able to do 1.18k Ohm... I've been steady at around 33Gh/s.

I tuned down to 1.165k, getting around 35Ghash, and 33Ghash/noncerate at the pool. Amazingly, chip #13 which was running at ~300mhash with tons of errors now works just fine.

I had a similar issue with one chip on an h-card. When I changed the resistance to 1.2k the chip went from ~0.100 to 2.000. That said I did need to clock it lower than the rest of the chips to achieve a reasonable error rate. At 53 it throws about 4% errors.

hmm sounds like the exact same issue. i have that chip tuned at 53 now with 6% errors

However, i now find that after some operation 1 chip (usually random, but 6 or 7 seem slightly more common) will drop to 0 hashrate until i stop and start the webgui. What could cause this? I am wondering if the chip is being shut off due to the increased voltage. With all 16 chips i see ~37Ghash and 34Ghash noncerate. with 15 its 35Ghash and 32.5ghash noncerate

temperatures seem okay. they are only slightly warmer then the original was before heatsinks and modding, and have significant airflow. (i read that fan/airflow vibrations can cause issues - is this actually a thing or an annecdote?)

[-Redacted-]

let's not spend time trying to distort reality. instead focus on the future- regardless, October will likely not ROI either
btw, out of pure curiosity i wonder how many people knew about 200th from bitfury 's private pool coming online.

I knew and bought in for some shares - nothing big, just a small piece.   I'm really starting to think this might end up being the way that BTC mining goes in the near future...