Topic: mining.BitcoinAffiliatenetwork.com-0% PPS + 1 Hour (or higher) Payout Interval - page 32. (Read 83345 times)

Seems like payouts are still around 15% short, not including the bonus..  Will these be fixed soon?

Let me elaborate on the situation for you:

First they/he ordered 31 S3's - these were to be the backbone of a new pool setup. Then, they/he set up various fake user accounts on this forum & signed them up to their/his newly created pool & waited for new users to appear, but it was a bit slow to catch on. So, they/he then decided to start a free giveaway of one S3 to a "user" of the pool every day for a month in the hope that this would attract new & unsuspecting users to the pool, gleefully posting the UPS delivery confirmation of the aforementioned 31 S3's as "proof of prizes" waiting to ship. They/he then started the draw, awarding the S3's to the fake user accounts they/he had set up earlier, then logging on here with the fake accounts and confirming that their S3 had arrived as expected & how wonderful everything was. The beauty of this was that no expense was needed to ship them out to anyone, as they weren't actually going anywhere, and no proof of posting/delivery was needed either. Perfect plan, almost.

A couple of people started asking questions, then a few more, but no answers were forthcoming.......

The rest, as they say, is history.

Let me elaborate on the situation for you:

First they/he ordered 31 S3's - these were to be the backbone of a new pool setup. Then, they/he set up various fake user accounts on this forum & signed them up to their/his newly created pool & waited for new users to appear, but it was a bit slow to catch on. So, they/he then decided to start a free giveaway of one S3 to a "user" of the pool every day for a month in the hope that this would attract new & unsuspecting users to the pool, gleefully posting the UPS delivery confirmation of the aforementioned 31 S3's as "proof of prizes" waiting to ship. They/he then started the draw, awarding the S3's to the fake user accounts they/he had set up earlier, then logging on here with the fake accounts and confirming that their S3 had arrived as expected & how wonderful everything was. The beauty of this was that no expense was needed to ship them out to anyone, as they weren't actually going anywhere, and no proof of posting/delivery was needed either. Perfect plan, almost.

A couple of people started asking questions, then a few more, but no answers were forthcoming.......

The rest, as they say, is history.

If someone with anymore information could elaborate a bit more on this subject that would be great. Is everything going to be re-drawn? Will the people accused of cheating be eliminated and the rest still win? I was pretty excited to win something. And I know if the legitimate winnners will still receive a item that I have nothing to worry. If its all in doubt, that's a bummer, for me at least.

I don't understand this part? So will the winners that were chosen still get their prize?

One thing I wish would have happened if they did the drawing daily as I have been mining here since almost the beginning of the contest when there were very few people but as the pool grew it became unfair to hold the drawings with so many days passed as people who were not here still had a chance to win from all those days past.

Did I word that right?

Anyway what is going to happen now and what was possibly unfair about the latest drawing?

Thanks

Dear BAN Miners,

At this time, we are having to take the unfortunate step of temporarily suspending any further Antminer S3 drawings. For the sake of transparency, we will tell you that we are investigating some possible improprieties in how the last group of winners was chosen, and until we are certain that this contest is 100% random, we are temporarily suspending any additional drawings.

At this time, the BAN staff has not received an official position from s0br on this, we've heard he has been without internet access due to some weather issues. As such, we are taking the steps we feel are appropriate to bring the current situation to light until more investigation takes place and we can speak to s0br. Please note again that this is temporary.

Thank you for your understanding.

BAN Support

This also could explain why I coudn't get my miners hashing on nicehash either.

Reserved for updates and FAQ


FAQ

1. Will S3 support p2pool?

The simple answer is we will. Bitmain has a very sincere interesting with p2pool, and we have invest human resource into this area. Sadly our firmware may not be able to give you a firm yes that we support p2pool right now, but we promise we will contribute much more to the p2pool mining idea than most of those who support p2pool mining well already.

Edit: AntMiners support p2pool. Static difficulty configuration recommended.
Since p2pool adjusts the difficulty frequently, therefore would bring hash rate loss when the difficulty changes at any time. As a result is that AntMiners' hash rate may be a little lower than that released officially when they are mining in p2pool.
We suggest you configure a static difficulty for AntMiner, when you mine in p2pool. Recommended difficulty is 256 or 512.

2. How to configure a static diff when AntMiner mines in p2pool?
Through ‘Status->Miner Configuration‘, configure Pool Worker as 'BTC address/256+256' or 'BTC address+256'.

3. Will there be S1/S2 upgrade kit and what is your plan?

Yes, there will be upgrade kit for both S1 and S2 customers. But we need some time to design and test it. After we have finished the homework, we will announce the plan publicly.

4. Beeper rings randomly?
We set a beeper ring alert in the first version of firmware, to alert users when there is no immediate hashing work due to bad pool configuration.
However this alert will be removed in the later version of firmware.
Users can download new version firmware on July 25.



UPDATES


2014-7-8: The bulk PCB will be arriving tonight, and we will start first batch production tomorrow. First batch usually takes a longer time than later. We may ship the S3 -B1 on or before 14th.

So would you say it's a minor miner issue?



Seriously though, that would be annoying.  Maybe Kano will fix the S2 firmware, but I don't have high hopes for it at this time.  

The p2p thing would make sense, and the elegius thing makes sense. So, yeah. It looks like a miner issue perhaps, not a pool issue effecting some people. =/ explains why I lost so much hash without explanation.

I imagine it's related to what Kano posted a little while back (see below).  I know that my S1s ran fine with Kano's firmware and when I point my S3s at the pool, I have less than a 1% reject rate.

   You don't say?  This is just hilarious - what timing, the day before the scam accusation goes up - you pull the plug. Brilliant idea!!

I just love those words you use - "transparency", "improprieties", "investigation".....as in "we've lost all records of shipping, and so have UPS by the way", or "this is a pic of the miner I won - and so is this, so what if they're completely different labels - it's the truth I tell you".  I wonder, will you be "investigating" yourself for openly bullshitting to everyone, or telling users to "fuck off & grow some"?

Somehow I doubt it  

And this:


More lies, he has been online almost every day - I've been checking, in fact he was online yesterday - everyone can see that, he's just been keeping quiet & not saying a thing - why?  Who the hell is running this show anyway?

This is just too funny - keep it coming guys, this will be the pool scam all time classic

    You don't say?  This is just hilarious - what timing, the day before the scam accusation goes up - you pull the plug. Brilliant idea!!

I just love those words you use - "transparency", "improprieties", "investigation".....as in "we've lost all records of shipping, and so have UPS by the way", or "this is a pic of the miner I won - and so is this, so what if they're completely different labels - it's the truth I tell you".  I wonder, will you be "investigating" yourself for openly bullshitting to everyone, or telling users to "fuck off & grow some"?

Somehow I doubt it 

And this:


More lies, he has been online almost every day - I've been checking, in fact he was online yesterday - everyone can see that, he's just been keeping quiet & not saying a thing - why?  Who the hell is running this show anyway?

This is just too funny - keep it coming guys, this will be the pool scam all time classic

It's only a BAN issue because a bunch of us were talking about it in the BAN IRC channel. It's also a BAN issue, because the current Invalid Shares count includes the 66 million I was writing about. Let's not start trying to tell folks where and when they can write things, and let others decide for themselves what is worthwhile.

The link you've provided is exactly the file that I had used; because it is supposed to fix it. That is why I tried it. That is why I am advising others not to.

You are running bitmain's S2 driver. Don't do that on p2pool. Also don't do that with bitmain's S1 driver.

Bitmain does some terrible things in their driver including ... discarding stale work in the driver before passing it to the work validation code.
This means on p2pool that if you find a stale block that is still a valid network block, it will be discarded. Oh well.

Use my driver for S1 if you don't want to throw such valid blocks away on p2pool.

My S2 driver is still in development - I'm still trying to work out why the device thinks it's a good idea to have >8000 work items queued in it - more than 30s of work - and to work out how to reduce that without letting it get idle - so I'm still waiting on source code from bitmain.

My blackarrow minion RPi driver is able to handle > 2TH/s of work at 1diff verifying every share returned at 1diff.
The S2 driver, on a faster BBB, should be able to handle 1TH/s of work at 1diff also. It doesn't. So I need to work out how to fix that - but I need the SPI kernel driver code bitmain wrote, for me to work that out.

Dear BAN Miners,

At this time, we are having to take the unfortunate step of temporarily suspending any further Antminer S3 drawings. For the sake of transparency, we will tell you that we are investigating some possible improprieties in how the last group of winners was chosen, and until we are certain that this contest is 100% random, we are temporarily suspending any additional drawings.

At this time, the BAN staff has not received an official position from s0br on this, we've heard he has been without internet access due to some weather issues. As such, we are taking the steps we feel are appropriate to bring the current situation to light until more investigation takes place and we can speak to s0br. Please note again that this is temporary.

Thank you for your understanding.

BAN Support

BAN staff has not received an official position from s0br on this, we've heard he has been without internet access due to some weather issues.

This isn't really a BAN issue.  The default S1/2 cgminer has this bug.  For anyone who buys an Antminer S1-3, I would recommend updating to the most recent firmware from Antminer directly, and then Kano's actual firmware.  I've linked them below.  

Official Antminer Firmware from Bitmain: https://www.bitmaintech.com/support.htm
S1: https://www.bitmaintech.com/support.htm?pid=00720140411033846942qQqjOD460695
S2: https://www.bitmaintech.com/support.htm?pid=00720140413044945482bs4xshkh072D
S3: https://www.bitmaintech.com/support.htm?pid=007201407180243004432lBQW28O0633

Kano's S1 CGminer: https://github.com/kanoi/cgminer-binaries/tree/master/AntS1
Kano's S2 CGminer: https://github.com/kanoi/cgminer-binaries/tree/master/AntS2
You can search through this forum for postings by Kano himself mentioning his own firmware to verify.
Kano's CGminer actually fixes this bug, but there are some people who have posted fake firmware to scam people out of their mining.

Hi,

    For all my fellow BAN pool miners that are using Antminer S2s, I thought I'd give you a heads up on a couple of things we were talking about in the IRC chat over this past weekend.

    The default firmware file leaves an open security hole for folks to exploit, and hijack your miner to work for them. So far, this has happened to me, with a miner using the name "benutzer" (German for "user"... apropos, right?) at BTC Guild. I don't blame BTC Guild for this one bad apple, but I did try to appeal to them to drop this guy. I don't think I made any progress on that part. I'm sure that they might be good people, with one bad apple.

    Well, what I found was a firmware file that was not from Bitmain, but specific for the S2, initramfs.bin.SD-Kano-20140611145346.tar... Avoid it!!! I tried it, and I had 60 million invalid shares in just a moment. What a mess!!!  

    If your miners are not behind a firewall, for now, all I can advise is that for you to make sure /etc/cgminer.conf.factory has api-allow set as something like this:

        "api-allow": "W:127.0.0.1,R:0/0",

    It allows you to modify the configurations locally, or via the web interface.