Topic: Announcement: Bitmain launches AntMiner solution, 0.68 J/GH on chip - page 2. (Read 368343 times)

Before.

But the PPS/TH Earnings line in the chart is AFTER or BEFORE maintenance?

A small sample.

Payout Total(BTC)
41.01489779

Maintenance(BTC)
21.49802663


Maintenance/Payout(PPS)  is today  not important at all

Hasnest pays per PPLSN
Mining Revenue Distribution

1.     Mining revenues generated from Hashnest mining contracts will be paid out using the PPLSN (Pay Per Last N Shares) method.

Does the "PPS/TH Earnings" number in the HashNest website already factor in maintenance or is it mining revenue BEFORE maintenance expenses?

Same question on the cumulative "Payout Total" number.

I've seen it asked how to solo mine with an AntS1

The solution:
1) Update the cgminer in the AntS1
Bitmain's cgminer is quite old and doesn't contain the fixes that are in my version to repair the problems they put in their version.
See the post above for details.

Then:

2) You can solomine to your own bitcoin by passing extra options to cgminer in your AntS1
The trick here is that the bitmain script that starts cgminer simply copies what you put in the pool info and passes that to cgminer
So, you can add extra cgminer options by editing a "PoolX password" field under the Status/Miner Configuration tab

In my miner I set the name the API shows for my Ant by setting "Pool1 password" to "pass --api-description Ant"
You must enter a password, and put a space after it, then you can add other cgminer options.

Firstly lets assume your bitcoind is running in standard settings.
You'll need to know the IP address of it, but lets guess it might be 192.168.0.10 <- of course you need to work out what it is and change it below - it's the IP address of the computer running bitcoin
Next you need to know the bitcoin configured Username and Password in the bitcoin.conf and put them in the highlighted places below
The Username and Password in the bitcoin.conf are the 2 lines:

rpcuser=Username
rpcpassword=Password

You also need to allow the Ant to mine to it, so you may need to add a line like this to your bitcoin.conf

rpcallowip=192.168.0.199

if 192.168.0.199 is the IP address of your Ant

Lastly you need a payout address to mine to - like 1xxxx - of course you need to use your address, not 1xxxx

To solo mine directly to your local bitcoind set the Pool1 settings as so (without the quotes ")
"Pool1" "http://192.168.0.10:8332"
"Pool1 worker" "Username"
"Pool1 password" "Password --btc-address 1xxxxx"

The settings don't need to be Pool1, you can use Pool2 or Pool3 and have solo as a backup.
You can also set the password field like follows so it mines to all 3 pools at the same time:
"Pool1 password" "Password --btc-address 1xxxxx --load-balance"

I've updated it for an api-allow bug that most wouldn't have noticed
https://github.com/kanoi/cgminer-binaries/tree/master/AntS1

4.9.1c-e6ad32a

BITMAIN - please work with luke-jr to get him what he needs to program BFGminer to support the U3. CGminer is too unstable for long term operation.

Great Kano thanks for your work.

Their miners are almost certainly talking to a local proxy. Satellite probably only connects proxy to the bitcoin network, miners never see anything but < 1ms ping. This is a no issue, except in unlucky event of some extreme weather storm/heavy rain which could block the satellite fora few hours which is very, very rare event. Of course, any business should try to switch back to optics as soon as possible just to be safe.

+1. assuming that each individual location acts as a local pool (which would be the best way to operate, and likely the case), then the ping time for a satellite connection should be irrelevant so long as the datacenter is still receiving new work.  Bitmain mentioned it is a main datacenter, which i assume means >1PH of equipment. with a local pool/work distribution system, there should be less than 3% orphans from lag since theres still such computing power

non-sequitur - mining is still a game of odds.  If both a and b get a solution in exactly t time, then yes, t_delay matters, as whoever has a lower t_delay stands a much larger chance of winning out.  But if a finds a solution in 5 minutes while b takes 8 minutes, t_delay can be up to 3 minutes before it matters.  Yes, the trend over the long term is important as those with a lower t_delay will win out on average - see also HF traders - but this is a problem in search of a short term solution while planning for a long term one.  And in that, a high latency internet is still preferable over no internet.

Sure, the signal can only go from Earth to orbit and back so fast - but that doesn't mean there aren't different providers with different contract levels giving different latency.  I was referring to that difference, not the difference with direct lines or The Postman.

I'll leave it to Bitmain to answer if they've considered that option - though I suspect that if you can get a modem going (and I can only presume you're thinking 28k8-era 'modem'), you've already got the base infrastructure for much better connectivity.  Whether it's worth throwing money at getting the endpoints to go along with that, instead of throwing money at replacing the fiber and using satellite in the interim, would be a follow-up question.

If the miners are mining to a local pool, and the pool is connecting to the bitcoin network over satellite, then the lag will be minimal. Trying to actually mine over satellite would be awful.

Not as far as mining goes - & satellite is absolutely the worst for mining, no matter who the provider is - it's a trait of satellite. Expect a flood of orphans/rejects - they'd be better off using a modem......

Depends on the provider - plus it's one of the more expensive options, so I'd imagine they ruled out cellular or line of sight solutions on the short term already.  Pingtastic internet is still better than no internet

Satellite internet? You do realise that this is the worst possible connection type for mining due to it's ultra-high latency right?

DOH!! 

Mining farms notice

In the past few days, a couple of our mining farms have been affected by unfortunate circumstances that were beyond our control. One of our main farms is located near a hydroelectric power station, and due to a fire in the nearby woods, the fiber-optic cable connecting the farm to the internet was damaged beyond repair. We have already set up a satellite internet connection in its place, and this farm is already back to normal. This loss of connectivity is the reason for Antpool's sudden loss of hashpower several days ago.

Another one of our farms (a small one) experienced a short circuit in the electrical transformer on site. Fewer than 2PH/s of hashrate were affected by this. Repairing this transformer could take more than a week. Users with mining contracts on Hashnest.com who have incurred any losses because of these two issues will be compensated by Hashnest and Bitmain.

Bitmain
April 8th, 2015

yes, we are under attack at this moment.  Connections to antpool from external site may experience a dead pool status.  All miners on hashnest or hosted miners are hashing normal in our internal network.

If you have any questions, please email [email protected]

The last DDoS attack (that I know of) was on kano.is just a couple of days ago, and I am sure it is from the same guy, who has also targeted other pools. here's the guy's profile: https://bitcointalksearch.org/user/d-d-4-b-c-411920
Look through his last posts and follow the threads he's posted to and you'll get the picture.

At least the S5 price hike might be put to good use in mitigating a claimed DDoS attack.