ANTMINER S3+ Discussion and Support Thread - page 282.

dsheaffer

member

Activity: 98

Merit: 10

Does anyone have an idea why one S3 miner would have 10X + the number of duplicates as my four other other S3 miners? All are Batch 5, all are configured identically.

PlanetCrypto

sr. member

Activity: 462

Merit: 250

Quote from: Biodom on August 10, 2014, 09:32:27 PM

Quote from: dsheaffer on August 10, 2014, 09:27:54 PM

Quote from: gallery2000 on August 10, 2014, 09:00:29 PM

Quote from: chadbu on August 10, 2014, 07:31:06 PM

I predict the next difficulty increase will be 20%

I predict it to be 11%

I predict 11.11%

jokes aside, it will be less than 20%, but higher than 11%, I choose 14-15%

I'm going with 13%-15% averaged out over time.

Biodom

legendary

Activity: 3892

Merit: 4331

Quote from: dsheaffer on August 10, 2014, 09:27:54 PM

Quote from: gallery2000 on August 10, 2014, 09:00:29 PM

Quote from: chadbu on August 10, 2014, 07:31:06 PM

I predict the next difficulty increase will be 20%

I predict it to be 11%

I predict 11.11%

jokes aside, it will be less than 20%, but higher than 11%, I choose 14-15%

dsheaffer

member

Activity: 98

Merit: 10

Quote from: gallery2000 on August 10, 2014, 09:00:29 PM

Quote from: chadbu on August 10, 2014, 07:31:06 PM

I predict the next difficulty increase will be 20%

I predict it to be 11%

I predict 11.11%

gallery2000

hero member

Activity: 784

Merit: 1000

Live Stars - Adult Streaming Platform

Quote from: chadbu on August 10, 2014, 07:31:06 PM

I predict the next difficulty increase will be 20%

I predict it to be 11%

itod

legendary

Activity: 1974

Merit: 1077

^ Will code for Bitcoins

Quote from: JennaK on August 10, 2014, 08:16:13 PM

Quote from: MoreBloodWine on August 10, 2014, 07:33:21 PM

Quote from: chadbu on August 10, 2014, 07:31:06 PM

I predict the next difficulty increase will be 20%

Already looking like it but can easily change...

Feel free to use this anywhere you'd like, it's from my personal node.

http://eojmarket.com/BTC-Node_Stat_Sig/BTC-Node_Stats.php

Thats depressing..
I'll never ROI!

Not all difficulty jump calculators are created equal. This one is almost always very accurate:
https://bitcoinwisdom.com/bitcoin/difficulty

JennaK

newbie

Activity: 42

Merit: 0

Quote from: MoreBloodWine on August 10, 2014, 07:33:21 PM

Quote from: chadbu on August 10, 2014, 07:31:06 PM

I predict the next difficulty increase will be 20%

Already looking like it but can easily change...

Feel free to use this anywhere you'd like, it's from my personal node.

http://eojmarket.com/BTC-Node_Stat_Sig/BTC-Node_Stats.php

http://eojmarket.com/BTC-Node_Stat_Sig/BTC-Node_Stats.php

Thats depressing..
I'll never ROI!

MoreBloodWine

legendary

Activity: 1064

Merit: 1001

Quote from: philipma1957 on August 10, 2014, 08:12:06 PM

Quote from: MoreBloodWine on August 10, 2014, 04:45:32 PM

My four S3's are still hashing stable for <48hrs now on stock all around ~440, so as soon as my collocation guys opens port 22 for me (he's very protective of outside traffic with what he does for a living) I can SSH in to the first miner to OC it. My ultimate goal is to see if I can get each one to ~500Gh/s which I should be able to since I seem to have good units hashing quite stable on stock freq.

I will bee playing it safe though and doing one miner at a time but I wont be going right to max though, I'll o first miner on 237.5, let run for 24hrs and if all looks good, bump it to 250 and let run another 24hrs. After that, it's on to the next machine.

if they run good at 237.5 be careful about the bump to 250.

I bumped them to 250 then ran well for a day then tanked. now they no longer like 237.5. they prefer 225.

Someone suggest I star with 237.5 so I may jus do that and leave it, if the gain @ 250 is only like 10-15gh per machine.

philipma1957

legendary

Activity: 4256

Merit: 8551

'The right to privacy matters'

Quote from: MoreBloodWine on August 10, 2014, 04:45:32 PM

My four S3's are still hashing stable for <48hrs now on stock all around ~440, so as soon as my collocation guys opens port 22 for me (he's very protective of outside traffic with what he does for a living) I can SSH in to the first miner to OC it. My ultimate goal is to see if I can get each one to ~500Gh/s which I should be able to since I seem to have good units hashing quite stable on stock freq.

I will bee playing it safe though and doing one miner at a time but I wont be going right to max though, I'll o first miner on 237.5, let run for 24hrs and if all looks good, bump it to 250 and let run another 24hrs. After that, it's on to the next machine.

if they run good at 237.5 be careful about the bump to 250.

I bumped them to 250 then ran well for a day then tanked. now they no longer like 237.5. they prefer 225.

MoreBloodWine

legendary

Activity: 1064

Merit: 1001

Quote from: chadbu on August 10, 2014, 07:31:06 PM

I predict the next difficulty increase will be 20%

Already looking like it but can easily change...

Feel free to use this anywhere you'd like, it's from my personal node.

http://eojmarket.com/BTC-Node_Stat_Sig/BTC-Node_Stats.php

chadbu

newbie

Activity: 28

Merit: 0

I predict the next difficulty increase will be 20%

visdude

legendary

Activity: 1081

Merit: 1001

Quote from: MoreBloodWine on August 10, 2014, 05:25:08 PM

Quote from: visdude on August 10, 2014, 05:16:10 PM

Quote from: MoreBloodWine on August 10, 2014, 04:45:32 PM

My four S3's are still hashing stable for <48hrs now on stock all around ~440, so as soon as my collocation guys opens port 22 for me (he's very protective of outside traffic with what he does for a living) I can SSH in to the first miner to OC it. My ultimate goal is to see if I can get each one to ~500Gh/s which I should be able to since I seem to have good units hashing quite stable on stock freq.

I will bee playing it safe though and doing one miner at a time but I wont be going right to max though, I'll o first miner on 237.5, let run for 24hrs and if all looks good, bump it to 250 and let run another 24hrs. After that, it's on to the next machine.

Most likely they will and hopefully they would. My units also perform within spec at stock clock. Just be aware that as you go up the frequency rung, the HW figures also increase; at least in my case anyway though they are still tolerable (highest at 0.28%). It's also possible to start getting some "x" on your chains; I got one eventually but didn't seem to affect hash rate on both sides. It seems the sweet spot for my units is at 237.5M with just the right increase in hash rate/power draw ratio and no "x" whatsoever. Good luck!

What do you average on all yours at 237.5 ?

478 GH/s @ 237.5M
42C and 398W at the wall @ 29C ambient with a Corsair CX500 80 Plus Bronze

Note: these are averages between two units but they are not far off from each other

MoreBloodWine

legendary

Activity: 1064

Merit: 1001

Quote from: Meech on August 10, 2014, 05:35:46 PM

Is there any difference in hashrate between the first couple batches and current ones? Sorry if this has been discussed before but I want to buy from Bitmain batch 6 and possibly batch 2 from Zoomhash.

If anything the diff's would just be firmware.

No even sure whats running my units.

Meech

hero member

Activity: 924

Merit: 1000

Is there any difference in hashrate between the first couple batches and current ones? Sorry if this has been discussed before but I want to buy from Bitmain batch 6 and possibly batch 2 from Zoomhash.

1Neptune

sr. member

Activity: 241

Merit: 250

Quote from: reactor77 on August 10, 2014, 04:45:17 PM

Quote from: JennaK on August 10, 2014, 04:40:13 PM

Quote from: nottm28 on August 10, 2014, 04:37:12 PM

Quote from: reactor77 on August 10, 2014, 04:26:21 PM

Quote from: Billbags on August 10, 2014, 04:24:59 PM

I've put in an email on my bookmarked Bitmain link. I asked if they would sell me some miners for USD bank transfer. I'll let you know what they say. Also, those emails you have sound like them, those are the questions they always ask me.

Ok,thanks.

Ive redacted your name and email address - here are the header details - can't really see anything wrong - anyone?

Code:

Return-Path: 
Delivered-To: REDACTED
Received: from mail-we0-f170.google.com (mail-we0-f170.google.com [74.125.82.170])
	by pmx.abv.bg (Postfix) with ESMTP id 1E1B5140514
	for ; Tue, 22 Jul 2014 11:03:04 +0300 (EEST)
Received: by mail-we0-f170.google.com with SMTP id w62so8586265wes.1
        for ; Tue, 22 Jul 2014 01:02:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=bitmaintech.com; s=google;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        bh=epYawXZT7KTmkpXIM8lA+Pbfc60ns+myvZg11iVLCxY=;
        b=UJAWrrqZFAZel8/Pg1kSpHRiOA32E9r13qb+ExbPdtGCBnUG67StiXUncJRgljf8W6
         oy5F5ZbmILMtck2kKQ9Mv37M+b2i9oKPWGtUCQmmBQwE/xIH5TwQc0vcviDKHTFtxz58
         w1AQSvAiBhRb9VoesDLIsBQh1VdO4HDKyDqRg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:mime-version:in-reply-to:references:from:date
         :message-id:subject:to:content-type;
        bh=epYawXZT7KTmkpXIM8lA+Pbfc60ns+myvZg11iVLCxY=;
        b=en6ppTgBjvrHZirC13yw5SQ/ZjnYk9KpX/gdpTIYpeyN6vGACHi523V3yWkG4QkCwu
         p0wletycU9z+90AlEU0z44+acZgAdEteCuP9hyESYH2DayTXTuqXApjwI/rHbFQNRGVp
         eOzAG7Ov/sN5Pv1qwZ39bEiT8y8m8YhVVxTHfG1pdxOQZKQ2aLY63D3cQUdULmu9RdEb
         DZUFy0VcCY6rmIg78rhRdhjFeGr/80EvbmO6g2F/rhZjuXS6NDVlMc6WpidV14oUdPfl
         R9s7fJrxG7NOYTvScdwsen0W8onM0t8A2Sl1giLetUDMzE3BvhuDrdADlKVPnMRNCXW8
         VeJg==
X-Gm-Message-State: ALoCoQn9KA9QvDgWw/R34qVP4c+dRECT5PnUiiO2HR9xxJ5RG/jvFB/yVv5oywGWddAUvK9b38h1
X-Received: by 10.194.60.35 with SMTP id e3mr31784901wjr.12.1406016179668;
 Tue, 22 Jul 2014 01:02:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.170.8 with HTTP; Tue, 22 Jul 2014 01:02:39 -0700 (PDT)
In-Reply-To: <[email protected]>
References: <[email protected]>
From: Bitmain Tech 
Date: Tue, 22 Jul 2014 16:02:39 +0800
Message-ID: 
Subject: Re: Ant S3
To: REDACTED 
Content-Type: multipart/alternative; boundary=047d7b86e8baf014a604fec3a69f

--047d7b86e8baf014a604fec3a69f
Content-Type: text/plain; charset=UTF-8

Hi,
1. besides bitcoins, we also accept USD wires.please feedback to us for
remittance info when you decide to place order.
2. ATX PSU is OK, there are 4 PCI-e connectors for +12V DC input, but it
only needs to connect two of them(total 30.5A) if without overclocking. FYI
http://www.enermaxusa.com/psu_revolution87+.php
3. Have you ever bought S3 from us before? do you have any coupon?
4. how many S3 do you plan to buy? we may request some discount if quantity
is large.


Best Regards

BITMAIN

This e-mail and its attachments contain confidential information from
BITMAIN TECHNOLOGIES LIMITED,  which
is intended only for the person or entity whose address is listed above.
Any use of the information contained herein in any way (including, but not
limited to, total or partial disclosure, reproduction, or dissemination) by
persons other than the intended recipient(s) is prohibited. If you receive
this e-mail in error, please notify the sender by phone or email
immediately and delete it! Thank you.

I double checked the email and there is zero inconsistencies.

Well,thats nice.I suppose,I just have to wait some more.maybe they dont answer in the weekends...Thanks for the help,everybody.

What concerns me:
1) The email headers at the start of the chain are nothing like the headers I have from confirmed email from bitmaintech when they send the shipment notice, which includes the order number, the address where btc payment had been sent, etc. In other words a scammer wouldn't know the details the email contains, and the tracking number matches the package I actually received when the S3's / S1's were delivered, so there's no doubt the email headers I used as a reference were legitimate. The starting header information in confirmed emails does not match the starting information cited above.
2) The abv.bg domain is in Bulgaria.
3) This: "[email protected]" and "Received: by 10.194.170.8 with HTTP" lead me to believe the email was actually sent from a spoofed address in a java script run by an html based client (web mail) and picked up by google mail then sent on through the rest of the email delivery systems at google and to the final destination.
4) This matches the confirmed email but could be due to the email already being in google's mail servers: "X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820;"
5) Your email header is missing the initial contact with an email server on the Internet: "Received: from bitmain01 ([119.9.72.212]) by mx.google.com...".

I hope you've not been scammed like I was. I have repeatedly reported to facebook the following is a scam, yet facebook still allows their page: https://www.facebook.com/pages/Bitmaintechcom/1445280845724880 ... and from some of the comments there I see they are still scamming people. Facebook should be held liable as they keep allowing and in effect supporting the fraud.

MoreBloodWine

legendary

Activity: 1064

Merit: 1001

Quote from: buy4crypto on August 10, 2014, 05:30:06 PM

470-475

Not bad, I'm hoping for 250 stability since if I can get it on all four miners and ~500 Gh will be a 240Gh bump.

buy4crypto

sr. member

Activity: 434

Merit: 250

freecrypto.top

Batch 5 machines

218.75 = 435-445
225 = 450-455
237.5 = 470-475
250 = 500-505

MoreBloodWine

legendary

Activity: 1064

Merit: 1001

Quote from: visdude on August 10, 2014, 05:16:10 PM

Quote from: MoreBloodWine on August 10, 2014, 04:45:32 PM

My four S3's are still hashing stable for <48hrs now on stock all around ~440, so as soon as my collocation guys opens port 22 for me (he's very protective of outside traffic with what he does for a living) I can SSH in to the first miner to OC it. My ultimate goal is to see if I can get each one to ~500Gh/s which I should be able to since I seem to have good units hashing quite stable on stock freq.

I will bee playing it safe though and doing one miner at a time but I wont be going right to max though, I'll o first miner on 237.5, let run for 24hrs and if all looks good, bump it to 250 and let run another 24hrs. After that, it's on to the next machine.

Most likely they will and hopefully they would. My units also perform within spec at stock clock. Just be aware that as you go up the frequency rung, the HW figures also increase; at least in my case anyway though they are still tolerable (highest at 0.28%). It's also possible to start getting some "x" on your chains; I got one eventually but didn't seem to affect hash rate on both sides. It seems the sweet spot for my units is at 237.5M with just the right increase in hash rate/power draw ratio and no "x" whatsoever. Good luck!

What do you average on all yours at 237.5 ?

visdude

legendary

Activity: 1081

Merit: 1001

Quote from: MoreBloodWine on August 10, 2014, 04:45:32 PM

My four S3's are still hashing stable for <48hrs now on stock all around ~440, so as soon as my collocation guys opens port 22 for me (he's very protective of outside traffic with what he does for a living) I can SSH in to the first miner to OC it. My ultimate goal is to see if I can get each one to ~500Gh/s which I should be able to since I seem to have good units hashing quite stable on stock freq.

I will bee playing it safe though and doing one miner at a time but I wont be going right to max though, I'll o first miner on 237.5, let run for 24hrs and if all looks good, bump it to 250 and let run another 24hrs. After that, it's on to the next machine.

Most likely they will and hopefully they would. My units also perform within spec at stock clock. Just be aware that as you go up the frequency rung, the HW figures also increase; at least in my case anyway though they are still tolerable (highest at 0.28%). It's also possible to start getting some "x" on your chains; I got one eventually but didn't seem to affect hash rate on both sides. It seems the sweet spot for my units is at 237.5M with just the right increase in hash rate/power draw ratio and no "x" whatsoever. Good luck!

MoreBloodWine

legendary

Activity: 1064

Merit: 1001

My four S3's are still hashing stable for <48hrs now on stock all around ~440, so as soon as my collocation guys opens port 22 for me (he's very protective of outside traffic with what he does for a living) I can SSH in to the first miner to OC it. My ultimate goal is to see if I can get each one to ~500Gh/s which I should be able to since I seem to have good units hashing quite stable on stock freq.

I will bee playing it safe though and doing one miner at a time but I wont be going right to max though, I'll o first miner on 237.5, let run for 24hrs and if all looks good, bump it to 250 and let run another 24hrs. After that, it's on to the next machine.

Topic: ANTMINER S3+ Discussion and Support Thread - page 282. (Read 710164 times)