Bitcoin Forum
November 18, 2018, 09:45:20 PM *
News: Latest Bitcoin Core release: 0.17.0 [Torrent].
 
   Home   Help Search Login Register More  
Pages: « 1 ... 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 [355] 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 »
  Print  
Author Topic: [1050 TH] BitMinter.com [1% PPLNS,Pays TxFees +MergedMining,Stratum,GBT,vardiff]  (Read 834530 times)
Newar
Legendary
*
Offline Offline

Activity: 1344
Merit: 1000


https://gliph.me/hUF


View Profile
July 21, 2014, 05:00:23 PM
 #7081

[...] Can i turn off under Bitminter mining for Namecoins, i think i just want all my power for BTC Mining [...]

Merged mining NMC is free for you at no computational, power or financial cost. If you do not want your NMC, consider to move the slider for NMC donations to the pool to 100%.

OTC rating | GPG keyid 1DC91318EE785FDE | Gliph: lightning bicycle tree music | Mycelium, a swift & secure Bitcoin client for Android | LocalBitcoins
1542577520
Hero Member
*
Offline Offline

Posts: 1542577520

View Profile Personal Message (Offline)

Ignore
1542577520
Reply with quote  #2

1542577520
Report to moderator
1542577520
Hero Member
*
Offline Offline

Posts: 1542577520

View Profile Personal Message (Offline)

Ignore
1542577520
Reply with quote  #2

1542577520
Report to moderator
1542577520
Hero Member
*
Offline Offline

Posts: 1542577520

View Profile Personal Message (Offline)

Ignore
1542577520
Reply with quote  #2

1542577520
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1542577520
Hero Member
*
Offline Offline

Posts: 1542577520

View Profile Personal Message (Offline)

Ignore
1542577520
Reply with quote  #2

1542577520
Report to moderator
1542577520
Hero Member
*
Offline Offline

Posts: 1542577520

View Profile Personal Message (Offline)

Ignore
1542577520
Reply with quote  #2

1542577520
Report to moderator
1542577520
Hero Member
*
Offline Offline

Posts: 1542577520

View Profile Personal Message (Offline)

Ignore
1542577520
Reply with quote  #2

1542577520
Report to moderator
DrHaribo
Legendary
*
Offline Offline

Activity: 2520
Merit: 1020


Bitminter.com Operator


View Profile WWW
July 21, 2014, 05:40:12 PM
 #7082

Makes sense. But what about the case in which I'm brute forcing a private key. And my machine is the only one working on the problem. At some point in time a million bajillion years from now I would expect to have been able to try all possible combinations. Now assuming there is only one matching private key, it would be possible to find that key on the very last sequence tried. What is the CDF? Would 50% CDF be half that time, in this case?

Hmm, yeah ok, I was a bit quick there. You're hashing an 80 byte bitcoin header. Of that you'll just want to change the 4 byte nonce and the 32 byte merkle root (determined by the transactions you include). So that's 36 bytes, or 288 bits, you change while hashing. That's 2 to the power of 288 possible permutations, which is 4.9732323640978664E86. If we round it up a bit the number of possible headers you can hash is 5 followed by 86 zeroes. As a second passes you can update the time field and you get that many new headers to try.

If you had a lot of hashing power I guess you could compute all those before everyone else, basically buying all the lottery tickets.

It's also possible that at some point, with a certain previous block hash, difficulty, and time value, that there is no valid solution until the time field has advanced months or years. It's just not very likely. It's actually more likely that Slender Man lives under your bed. So check on that first.

50% CDF means 50% of blocks are found with this amount of work or less at the difficulty in question. At 99% CDF only 1% of blocks take more work, so that's pretty unlucky. On average it happens with 1 out of 100 blocks though, so it's not like some people think; "bad luck like this is impossible, something must be wrong". Mining is like a lottery and on average 1 out of 100 blocks will take that much work. If you expect that to never happen, it's your thinking that is wrong.

▶▶▶ Bitminter.com - Your trusted mining pool since 2011.
DrHaribo
Legendary
*
Offline Offline

Activity: 2520
Merit: 1020


Bitminter.com Operator


View Profile WWW
July 21, 2014, 05:51:44 PM
 #7083

There is Stratum protocol on port 443. This is the most efficient option.
There are getwork and getblocktemplate protocols on port 80.
Eventually I want to get completely rid of getwork, so please don't use it.

http://mint.bitminter.com:80

At home this adress works fine but in office it does not work Sad

Maybe you need to connect through a proxy at work?


The adress: stratum+tcp://mint.bitminter.com:443 does not work at home nether in office

Some mining client interfaces don't like the stratum+tcp prefix. I can't remember if Antminer S1 is one of those. You could try with just: mint.bitminter.com:443


Does every Antminer working unit need an extra name e.g. Biosman_Worker01, Biosman_Worker02 etc or is one name for all Antminer enough e.g. Biosman_Worker?

That's up to you. You can run all your hardware on one worker. New users get a worker named "1" which is configured as a default worker. That means you can mine with just your user name and it will pick the default worker. On the other hand if you want separate stats and slow worker emails then it can be handy to create multiple workers, especially if you have machines on separate physical locations and one of them stop working. You can do this under "my account" -> "workers" in the website menu.

What are these settings and do i have to change something?

Quote
Default worker    
Minimum difficulty    
Work submits per minute    Default Override:
Low hashrate warning    Off Threshold: Mhps
Stratum extranonce2    Default Override: Bytes
Merged mining stale flush
   


There's a short tooltip text that appears if you hold the mouse pointer over the underlined words, that can help a bit. Ask if there's something specific you want to know about. Most of those settings will do fine with the defaults. The most useful thing is probably low hashrate warnings. You can choose a minimum MH/s there and if your worker goes below that you will receive an email alert.

▶▶▶ Bitminter.com - Your trusted mining pool since 2011.
DrHaribo
Legendary
*
Offline Offline

Activity: 2520
Merit: 1020


Bitminter.com Operator


View Profile WWW
July 21, 2014, 05:54:44 PM
 #7084

Does every Antminer working unit need an extra name e.g. Biosman_Worker01, Biosman_Worker02 etc or is one name for all Antminer enough e.g. Biosman_Worker?

There doesn't appear to be any user named Biosman on Bitminter. I guess this was just an example you were using, but if not, make sure you use the correct user name - it's displayed in the upper right corner of the website when logged in.

▶▶▶ Bitminter.com - Your trusted mining pool since 2011.
rockby11
Newbie
*
Offline Offline

Activity: 35
Merit: 0


View Profile
July 22, 2014, 02:26:10 AM
 #7085

stratum+tcp://mint.bitminter.com:3333 works just fine with s1
rockby11
Newbie
*
Offline Offline

Activity: 35
Merit: 0


View Profile
July 22, 2014, 02:33:19 AM
 #7086

on the s1 under miner configuration tab use:
Pool 1             stratum+tcp://mint.bitminter.com:3333
Pool 1 worker  yourusernameonthatsite.workername

on the site just workername as the above.
Jayjay04
Legendary
*
Offline Offline

Activity: 1379
Merit: 1000



View Profile
July 22, 2014, 04:31:22 AM
 #7087

The better way to improve and fasten payouts is to add hashing power.

And maybe I have an idea that you should consider to attract bigger hashers...

It could be wise to give a reward to the block finder in addition to his payout.

The amount is to be consider, but if the blockfinder could received, maybe 0,25 btc + his payout, this would probably attract more user to the pool. Bringing more hashpower, bringing more regularity, but in that case, losing 1/10 of revenue for each user....

                    ▄▄▄
                   █████
             ▄▄▄    ▀▀▀       ▄▄████╕
            █████          ▄▄███████▌
     ▄▄▄     ▀▀▀        ╓████████▀▀
    █████               ██████▀▀       ▄███▄
     ▀▀▀        ▄███▄    ▀▀▀           ▀███▀
                ▀███▀        ▄▄████╕
       ▁▄▄███▄           ▄▄████████▌
   ▁▄▆████████       ▄▄█████████▀▀       ▄███▄
 ▄█████████▀▔    ▄▄█████████▀▀           ▀███▀
▐██████▀▀▔   ,▄█████████▀▀        ▄▄▄
 ▔▀▀▀▔    ▄▄████████▀▀           █████
      ▄▄████████▀▀       ▄▄██▄    ▀▀▀
   ▄█████████▀       ▄▄███████▌       ▄▄▄
  ▐██████▀▀      ▄▄█████████▀▔       █████
   `▀▀▀      ▂▄█████████▀▀    ,▄▄µ    ▀▀▀
          ▂▆████████▀▀    ,▄██████▌
          ██████▀▀     ▄█████████▀
           ▔▀▀        ███████▀"
                      "▀▀▀╙
Hello!
STAKER
.The Next Proof-of-Stake.
KSmart Contract Tokene.














christhegoth
Full Member
***
Offline Offline

Activity: 120
Merit: 100


View Profile
July 22, 2014, 06:09:37 AM
 #7088

I am adding a pair of s-3's  to the doc h team.  seems to be really nice gear so far.

Stock clock is freq 218  gives me 440 gh

I under clocked to freq 212  gives me 426 gh  for 1 machine   watts used with an evga 1300 psu are  640 for the 2 machines with a total gh of around 840

I also will be adding a pair of S3's next week.


I'll be running an experiment:


I'll be splitting my hash ( currently 900 GH/s) 50:50 between Doc & another pool I won't name ( out of respect to the good Dr ).

Gonna see if that helps to stabilise earnings/ luck a bit. Bitminter still averages over a month, but these peaks & troughs obviously spook some people.


I'll also be adding an S3 to my mining kit later, which will be moved between these 2 pools to chase the luck ( it's the only machine that will pool-jump ).

The idea is to go for max profit, without damaging Bitminter's block-creation abilities ( by moving too much hash away & thus destabilising the pool if enough people start pool-jumping ). Only 1/3 of my hash will be mobile.

It may well make no difference, but the next month ( before the S3 shows ) will be very interesting. I will keep you informed.
DrHaribo
Legendary
*
Offline Offline

Activity: 2520
Merit: 1020


Bitminter.com Operator


View Profile WWW
July 22, 2014, 07:05:17 AM
 #7089

I'll also be adding an S3 to my mining kit later, which will be moved between these 2 pools to chase the luck ( it's the only machine that will pool-jump ).

Do you realize that chasing luck is pointless? You'll be leaving a pool after there was bad luck and you already got a low payout, and you'll be joining a pool after there was good luck and everyone else got high payouts.

How do you plan to predict the future? Do you believe old luck causes the opposite luck in the future? Or that it causes more of the same luck? Both are popular superstitions.

In the past you could sometimes tell if future payouts would be low on some pools, pools that used the proportional reward system. And also Slush's score-based reward system, which can probably be abused still if they didn't switch reward system. This resulted in something called pool hopping. People would switch pools at the right time and get more than their fair share of the mining rewards, while 24/7 miners got less than fair pay. PPLNS, which Bitminter uses, is designed specifically to make this impossible.

It could be wise to give a reward to the block finder in addition to his payout.

It looks good on first glance, but this would just increase variance. Usually you get low payouts because someone else found the block, but sometimes you may find the block and get a high payout. Over a very long time it evens out, but in a shorter timespan it just creates variance. "Shorter" here means forever for small miners.

That's not to say it wouldn't work. Many miners don't understand variance, and there's also the psychological aspect of saying "you get paid a bonus if you find a block!" but not mentioning that you get a lower payout the rest of the time.

Worse is paying for stale work. It's a horrible idea. I think there are still some pools doing it, though. It just means that people with proper miners have to give some of their income to people with broken miners. If you have 1 TH/s and get 0.1% stales, and another user has 1 TH/s with 5% stales, you get the same payouts. Even though you contributed more to the mining effort. The other person was doing a lot of useless work, working on old data long after it was too late. So the effect is that some of your income is given to someone else. That's why you should not mine in such pools if your equipment is working properly. They are great if there is something wrong with your miners though, and they are producing a lot of stale work. Just like pool-hopping vulnerable reward systems, paying for stale work creates a pool where some users get more than their fair share, while others get less.

On the other hand, if the pool says "we pay for stale work, so you don't lose anything - it can be an extra 1% income!" then it sounds like a great thing. What you don't realize is that in reality you may be making 1% less than your fair share because your hardware, software and internet connection are actually working.

That's a lot of rambling. Anyway, that's why I don't add these two "features" that some pools have. I couldn't stomach marketing it as a good deal either.

▶▶▶ Bitminter.com - Your trusted mining pool since 2011.
christhegoth
Full Member
***
Offline Offline

Activity: 120
Merit: 100


View Profile
July 22, 2014, 07:16:39 AM
 #7090

I'll also be adding an S3 to my mining kit later, which will be moved between these 2 pools to chase the luck ( it's the only machine that will pool-jump ).

Do you realize that chasing luck is pointless? You'll be leaving a pool after there was bad luck and you already got a low payout, and you'll be joining a pool after there was good luck and everyone else got high payouts.

How do you plan to predict the future? Do you believe old luck causes the opposite luck in the future? Or that it causes more of the same luck? Both are popular superstitions.

In the past you could sometimes tell if future payouts would be low on some pools, pools that used the proportional reward system. And also Slush's score-based reward system, which can probably be abused still if they didn't switch reward system. This resulted in something called pool hopping. People would switch pools at the right time and get more than their fair share of the mining rewards, while 24/7 miners got less than fair pay. PPLNS, which Bitminter uses, is designed specifically to make this impossible.

It takes about 4-5 days for Bitminter to get up to speed when I add some hashes. The other pool was the same.

Bitminter's peaks and troughs ( the graph) last for 2-3 weeks from what I can see.


That's the test. Read the graph, make your choice, and then go from there. It's only 1/3 of my hash, so shouldn't be too big a gamble if I get it wrong.

However...


If you want people to hang around then you need to give them options should they panic over a week of bad luck. Or they'll see you as a bad pool. Mining techniques to smooth things out should help here. Using 2 pools is a basic ( it's nice & simple to understand) , but there will be profit-chasers as well.
Minor Miner
Legendary
*
Offline Offline

Activity: 1246
Merit: 1000


Blockchain with a Purpose


View Profile
July 22, 2014, 07:55:13 AM
 #7091

I'll also be adding an S3 to my mining kit later, which will be moved between these 2 pools to chase the luck ( it's the only machine that will pool-jump ).
Do you realize that chasing luck is pointless? You'll be leaving a pool after there was bad luck and you already got a low payout, and you'll be joining a pool after there was good luck and everyone else got high payouts.
How do you plan to predict the future? Do you believe old luck causes the opposite luck in the future? Or that it causes more of the same luck? Both are popular superstitions.
In the past you could sometimes tell if future payouts would be low on some pools, pools that used the proportional reward system. And also Slush's score-based reward system, which can probably be abused still if they didn't switch reward system. This resulted in something called pool hopping. People would switch pools at the right time and get more than their fair share of the mining rewards, while 24/7 miners got less than fair pay. PPLNS, which Bitminter uses, is designed specifically to make this impossible.
It takes about 4-5 days for Bitminter to get up to speed when I add some hashes. The other pool was the same.
Bitminter's peaks and troughs ( the graph) last for 2-3 weeks from what I can see
That's the test. Read the graph, make your choice, and then go from there. It's only 1/3 of my hash, so shouldn't be too big a gamble if I get it wrong.
However...
If you want people to hang around then you need to give them options should they panic over a week of bad luck. Or they'll see you as a bad pool. Mining techniques to smooth things out should help here. Using 2 pools is a basic ( it's nice & simple to understand) , but there will be profit-chasers as well.
I cannot even begin to understand what you are thinking but please stop trying to explain to the rest of us.
And you are splitting up your 1.5TH/s of miners to chase this luck?  Even if your theory was possible, the amount of hashing power you have does not really make it worth the effort you will put into this.


      ▄▄█████████▄▄██
   ▄███▀▀       ▀▀███▄██
  ██▀   ▄        ▄▄ ▀██▀
 ██    ██        ██   ██
██     ██        ██    ██
██     ██ ▄▄▄▄▄▄▄██    ██
██    ██  ▀▀▀▀▀▀██     ██
██    ██        ██     ██
 ██   ██        ██    ██
 ▄██▄ ▀▀        ▀   ▄██
 ██▀███▄▄       ▄▄███▀
    ██▀▀█████████▀▀
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
      ▄▄█████████▄▄██
   ▄███▀▀       ▀▀███▄██
  ██▀   ▄        ▄▄ ▀██▀
 ██    ██        ██   ██
██     ██        ██    ██
██     ██ ▄▄▄▄▄▄▄██    ██
██    ██  ▀▀▀▀▀▀██     ██
██    ██        ██     ██
 ██   ██        ██    ██
 ▄██▄ ▀▀        ▀   ▄██
 ██▀███▄▄       ▄▄███▀
    ██▀▀█████████▀▀
christhegoth
Full Member
***
Offline Offline

Activity: 120
Merit: 100


View Profile
July 22, 2014, 07:57:37 AM
 #7092

I'll also be adding an S3 to my mining kit later, which will be moved between these 2 pools to chase the luck ( it's the only machine that will pool-jump ).

Do you realize that chasing luck is pointless? You'll be leaving a pool after there was bad luck and you already got a low payout, and you'll be joining a pool after there was good luck and everyone else got high payouts.

How do you plan to predict the future? Do you believe old luck causes the opposite luck in the future? Or that it causes more of the same luck? Both are popular superstitions.

In the past you could sometimes tell if future payouts would be low on some pools, pools that used the proportional reward system. And also Slush's score-based reward system, which can probably be abused still if they didn't switch reward system. This resulted in something called pool hopping. People would switch pools at the right time and get more than their fair share of the mining rewards, while 24/7 miners got less than fair pay. PPLNS, which Bitminter uses, is designed specifically to make this impossible.




If you could average out a month's payments based on predictions etc you could create a perk that 'stabilises' people's payments.  So if you know someone at their present hash will earn 1 BTC over  a month based on your graphs then you can work out what an average payment would be per week, and then offer that.  Nice and stable, rather than Casino.

Charge for it to create a reserve to pay for any amounts up front that will be recouped later.  You might even squeeze a profit if your luck holds.

That's another way to stop people from jumping ship after a bad week or 2.  And may well attract investors.


Investors do not want 'Casino'.  They want risks kept to a minimum.  Bitminter is a small pool, and if you want to grow it you have to play the game.  If you give them Casino they'll go to a big pool that is good at hunting for blocks, and also more stable in it's payments ( if less lucky on a personal level due to how your luck is being shared with so many others ).  That's why GHash is the man now.  Profits are fairly dull ( not very exciting ), but they are reliable.  There's no Casino.  So investors will sink cash into a datacenter loyal to GHash.  You need to find a way to make Bitminter look as reliable on return to get these people to come to you.

So talking Casino is a real bad plan here ( even if it is true ).  You need to think of a way to show stability both on the graphs and in the payments sent to people.

Your perk system is good.  But you need a 'payment averaging' one for those sitting there looking at an s3 and wondering whether to get the Credit Card out.  As I've said before I know VERY few people who can afford to take £400 and just set it on fire ( for example ), and in a Casino you can lose everything.


I'm happy to help if I see anything Smiley
christhegoth
Full Member
***
Offline Offline

Activity: 120
Merit: 100


View Profile
July 22, 2014, 08:06:31 AM
 #7093

I'll also be adding an S3 to my mining kit later, which will be moved between these 2 pools to chase the luck ( it's the only machine that will pool-jump ).
Do you realize that chasing luck is pointless? You'll be leaving a pool after there was bad luck and you already got a low payout, and you'll be joining a pool after there was good luck and everyone else got high payouts.
How do you plan to predict the future? Do you believe old luck causes the opposite luck in the future? Or that it causes more of the same luck? Both are popular superstitions.
In the past you could sometimes tell if future payouts would be low on some pools, pools that used the proportional reward system. And also Slush's score-based reward system, which can probably be abused still if they didn't switch reward system. This resulted in something called pool hopping. People would switch pools at the right time and get more than their fair share of the mining rewards, while 24/7 miners got less than fair pay. PPLNS, which Bitminter uses, is designed specifically to make this impossible.
It takes about 4-5 days for Bitminter to get up to speed when I add some hashes. The other pool was the same.
Bitminter's peaks and troughs ( the graph) last for 2-3 weeks from what I can see
That's the test. Read the graph, make your choice, and then go from there. It's only 1/3 of my hash, so shouldn't be too big a gamble if I get it wrong.
However...
If you want people to hang around then you need to give them options should they panic over a week of bad luck. Or they'll see you as a bad pool. Mining techniques to smooth things out should help here. Using 2 pools is a basic ( it's nice & simple to understand) , but there will be profit-chasers as well.
I cannot even begin to understand what you are thinking but please stop trying to explain to the rest of us.
And you are splitting up your 1.5TH/s of miners to chase this luck?  Even if your theory was possible, the amount of hashing power you have does not really make it worth the effort you will put into this.

I think you are mis-judging the intelligence of some of your miners.

Considering how nice a Pool Bitminter is ( the nice GUI and decent USB client etc ) have you not wondered by you are so small compared to others?

Do you want to grow or not?  Keep talking Casino and you won't grow by much.

And before you say anything I'm an engineer with a corporate background ( including Legal, Finance, & Management ) and 20 years of reading under my belt.  Investors do not want Casino.  They want stability, so that they can stick their feet up and let someone else do the running around.  Casino is not an attractive investment; stability is.  Hence why the big pools do so well.   They may be boring ( no real cut & thrust ), but they do have a reliable ( enough ) return that means you can budget.


If I can find a pattern that The Doc can use to improve stability then a lot more people will reach for a Credit Card and add an s3 to this pool.  Which is what we want.

It's simple business.


Spreading your bets over 2 pools is the first stabiliser.  I'm simply testing whether pool-jumping is still possible if you crunch the figures once a week ( which isn't much effort I assure you ).
SgtMoth
Hero Member
*****
Offline Offline

Activity: 909
Merit: 1003


buy silver!


View Profile
July 22, 2014, 09:16:21 AM
 #7094

How long have you been mining?
christhegoth
Full Member
***
Offline Offline

Activity: 120
Merit: 100


View Profile
July 22, 2014, 09:22:12 AM
 #7095

So far it's as follows:

Bitminter.  Small & reliable.  Income fluctuates, and this scares some people.  1450 TH.

Eligius.  6000 TH and reliable. Income fluctuates less, but any good luck is spread out over a lot of people so will impact on how big your 'good luck' payment is.

GHash.  40000 TH.  So reliable in it's return that people are now buying life-time mining contracts on it ( getting a host to mine for them ).  The big data-centres come here too.  Income really does not fluctuate ( so no panics happen really ), but it's boring.  If you get any good luck you just won't notice, where it is spread across so many different people.


Bitminter has the best USB client ( it just works ), and also a VERY nice GUI.  The Perk System is also a real selling point.  And yet we're small.

If it's not the product ( and obviously it's not ) it must be the marketing.  So you need to check stuff out to see what you can say truthfully to show you are the best.

The only fly in the ointment is people panicking over luck ( there have been plenty of posts on this ), and that is why I am looking for ways to stabilise payments ( so that we appear as reliable as Eligius or GHash to someone who is new to mining ).

If we can look nice and reliable to a newb they may well get that Credit Card out and give Doc some more hashes.


Anyway, I'll let this chat cool down for now.  I know some are interested but others aren't.
christhegoth
Full Member
***
Offline Offline

Activity: 120
Merit: 100


View Profile
July 22, 2014, 09:24:03 AM
 #7096

How long have you been mining?


8 months near enough.  I started when BTC prices were low, saw the £1000 spike, saw people poop a brick, and then saw the '£300 period' where people started looking again.
AaronS
Newbie
*
Offline Offline

Activity: 28
Merit: 0


View Profile
July 22, 2014, 03:03:05 PM
 #7097

If you want stable payments, use a big pool, if you want some excitement, use a small pool.  If a system was  put in place to smooth out the payments and eliminate "casino", why not just move to a big pool?

Funny how you are asking for stable payments while just a few weeks back Philip was insisting the solution was to offer solo mining where things are pretty much all-or-nothing super-casino.
Biosman
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
July 22, 2014, 03:12:19 PM
 #7098

@DrHaribo: Thx for your answer but my problem is not solved and i don't know why.

In my office behind a firewall i have these IP connection on my laptop:

Works with DHCP-Server:
IP-Adress: 192.168.199.117
Subnetzmask: 255.255.255.0
Standardgateway: 192.168.199.41
DHCP-Server: 192.168.199.41
Lease erhalten: 14.07.2014 18:31:55
Lease läuft ab: 14.07.2014 20:31:55
DNS-Server: 192.168.199.41

I can give my laptop a static IP and it also works for example:
IP-Adress: 192.168.199.125
Subnetzmask: 255.255.255.0
Standardgateway: 192.168.199.41

Every thing is working, i can use Teamviewer, Skype, my dLAN adapter works etc.

But Antminer does not appear in the network when i control it with my port scanner, not with DHCP-Server or with a static IP. I think this is the first problem.

What do i have to do to get the Antminers in the office network, port forwarding or something like that and how?

I think this is the first problem, the other problem ist that only a few ports are openend:

Quote
SMTP: Port 25
HTTP: Port 80
POP3: Port 110
NNTP: Port 119
EPMAP: Port 135
Shared Network Folder: 139
IMAP: 143
HTTPS: 443

Does anyone knows a solution for my problem?
Thx for your help again

Gr€€tz Biosman

DrHaribo
Legendary
*
Offline Offline

Activity: 2520
Merit: 1020


Bitminter.com Operator


View Profile WWW
July 22, 2014, 03:31:36 PM
 #7099

But Antminer does not appear in the network when i control it with my port scanner, not with DHCP-Server or with a static IP. I think this is the first problem.

If you set it up with a static IP that is not used by anything else on the network (make sure), you are still not able to reach its web interface if you put that IP in the address field of the browser?

From the PC where you are trying to contact the Antminer, are you able to reach other machines on the network?

▶▶▶ Bitminter.com - Your trusted mining pool since 2011.
christhegoth
Full Member
***
Offline Offline

Activity: 120
Merit: 100


View Profile
July 22, 2014, 03:38:37 PM
 #7100

In response to the various 'chase luck' comments.


*rolls eyes*  Statistical probability does not work that way.


Ok, I'll explain:

Much as you cannot predict the future with 1 quarter being flipped 10 times you can make a safer guess if you flip 10 quarters at the same time for 10 times ( whilst gambling cash on them, which is the reality of how this one works ).

1 quarter, 1 gamble, 50% chance of winning.  And if you get an unlucky streak of 3-4 flips you lose it all.

10 quarters, 1 gamble per coin, 50% chance of winning per coin.  For all 10 quarters to go bad for 3-4 flips ( enough to empty your wallet ) is a lot rarer than for 1 quarter to go bad for 3-4 flips.  It's the difference between spreading your bet or going 'all or nothing' ( 1 coin is all-or-nothing, where-as 10 coins is bet-spreading ).


So...

You bet £25.00 on 1 coin coming up heads.  You flip 2 coins, so gamble £50.00.  If you get it right you get £25.00 per head ( simple 1:1 odds ).  If a tail comes up you lose the £25.00 on that coin.

For both to come up tails or heads the odds is 0.5 * 0.5.  So there is a 25% chance you'll win big, but also a 25% chance you'll lose it all.

For one to come up heads, and the other tails, is 0.5 * 0.5 ( 25% again ), but... there are 2 ways this can happen.  Coin 1 gets the head, or coin 2 gets the head.  So that doubles your chance to 50%.

Both tails and you lose £50 ( all you gambled ).
Both heads and you get your 50 back plus another 50.

A head and a tail? You pay out 25 on one, and get 50 back on another ( your stake plus the win bonus ).  But there are 2 chances of this happening.  So...

25% you lose it all.
50% chance you gain £0 over-all.
25% chance you gain £50 over all.

With just one coin you'd be looking at a 50% chance of losing £50, and a 50% chance of gaining £50.00.  Only 1 chance to make money, with no safety net.  All or nothing.

With 2 coins you have 1 chance to make money, 1 chance to lose it, and 2 for breaking even.


If you have modern mining kit like S3's you'll be making a small profit if the break even, and a larger profit if you win.  If you lose you may well break even.  Because s3's have a good power ratio.

An old S1 will see you running at a loss if you lose, breaking even if you break even, and making a small profit if you win.  Near enough.  As their power ratio is nothing impressive these days.


It's like betting on the horses.  Spread your bet and you will lose less if you get unlucky generally speaking.  Unless you're cursed and they all come in bad, but the odds of that happening are a lot less.

This is how you do it on the gee-gees:

Favourites Index

This is the forecast of how the favourite will perform in each race at a specific race meeting. Points are awarded for finishing in the first three in the following way: 25 points for win, 10 points for second and 5 points for third. If there are joint or co-favourites, we take the favourite as being the horse with the lower race card number.

Example

’At the Southwell Fibresand card consisting of seven races, our favourite’s prediction might be 62-65 points. If you believed that the favourites in all seven races stood a good chance you would buy at 65 for a stake of. When all the results are in the final tally is made up of 80. You would have therefore won 15 times your stake: (65 - 80) x your stake = 15 x £/€5 = £/€75. But, if the favourites index had made up at only 50 points, the same bet would have lost you 35 times your stake: (50 - 85 x your stake = -35 x £/€5 = -£/€175'


Or...

Don't put all your eggs in one basket.


For BTC if you mine 2 pools and one goes bad the other pool will still be there.  So you'll only lose half of your cash, instead of all of it.  The odds of 2 pools going bad at the same time are less than they are for one pool going bad.


This is why professional mining gear can mine 3 pools at once ( from one unit ).  It's a standard safety feature, just in case one pool goes bad for a bit.


And if a horse is having a winning streak it's very easy to read the results for it, it's competitors, and then make a judgement call on who to bet on.


There are no guarantees sure, but it also means if you lose you won't lose badly compared to an 'all or nothing' system ( where 3-4 bad rounds is you gone, as you're only flipping one coin instead of 10 per round ).


Doc wants s3's, and to do that he needs to make it look like a safer investment then a bunch of people yelling 'casino' because they did not do degree level math ( I'm sorry, but I have to be honest here ).

Just because you don't get how it works does not mean it does not exist.  An entire race industry, that's been alive for at least 2000 years, has tried and tested this one.  You never put all your eggs in one basket unless you can afford to lose big.



That's the math.  Think about that before you miss-sell Doc's pool to new people.
Pages: « 1 ... 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 [355] 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!