Bitcoin Forum
November 28, 2022, 04:56:53 AM *
News: Reminder: do not keep your money in online accounts
 
   Home   Help Search Login Register More  
Pages: « 1 ... 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 [153] 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 ... 1155 »
  Print  
Author Topic: [4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool  (Read 4380582 times)
Lambontae
Newbie
*
Offline Offline

Activity: 17
Merit: 0


View Profile
June 21, 2011, 09:22:18 PM
Last edit: June 21, 2011, 09:33:50 PM by Lambontae
 #3041

Phoenix miners working, both GPUs.... must be GUIMiner. Gonna delete, then re-extract.

[edit] Fixed. had to create new openCL miners and re-extract. Seems some settings got jumbled up
1669611413
Hero Member
*
Offline Offline

Posts: 1669611413

View Profile Personal Message (Offline)

Ignore
1669611413
Reply with quote  #2

1669611413
Report to moderator
Remember that Bitcoin is still beta software. Don't put all of your money into BTC!
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1669611413
Hero Member
*
Offline Offline

Posts: 1669611413

View Profile Personal Message (Offline)

Ignore
1669611413
Reply with quote  #2

1669611413
Report to moderator
1669611413
Hero Member
*
Offline Offline

Posts: 1669611413

View Profile Personal Message (Offline)

Ignore
1669611413
Reply with quote  #2

1669611413
Report to moderator
1669611413
Hero Member
*
Offline Offline

Posts: 1669611413

View Profile Personal Message (Offline)

Ignore
1669611413
Reply with quote  #2

1669611413
Report to moderator
slush (OP)
Legendary
*
Offline Offline

Activity: 1386
Merit: 1070



View Profile WWW
June 21, 2011, 10:18:53 PM
 #3042

Phoenix miners working, both GPUs.... must be GUIMiner. Gonna delete, then re-extract.

[edit] Fixed. had to create new openCL miners and re-extract. Seems some settings got jumbled up

Hm, really crazy. Great that you fixed it.

CanaryInTheMine
Donator
Legendary
*
Offline Offline

Activity: 2436
Merit: 1055


between a rock and a block!


View Profile
June 22, 2011, 04:25:27 AM
 #3043

How come there are two entries for block 132473???

This looks fishy...
CanaryInTheMine
Donator
Legendary
*
Offline Offline

Activity: 2436
Merit: 1055


between a rock and a block!


View Profile
June 22, 2011, 04:42:16 AM
 #3044

And for block 132468 also?

What's going on here?
nomnomnom
Sr. Member
****
Offline Offline

Activity: 313
Merit: 250



View Profile
June 22, 2011, 05:31:14 AM
 #3045

weird, I see this too.
But they point to different blockexplorer addresses, and one shows no such block. Huh

Something else:
Is there still ddos attacks going on? because sometimes my miners stop for a moment
with workque empty. I am not sure if this is maybe my internet connection.
scooter
Member
**
Offline Offline

Activity: 100
Merit: 10


View Profile
June 22, 2011, 05:54:59 AM
 #3046

I have no reward from the last 6 blocks.
Granted I only mine at 200 M/hash but usually I get something...
scooter
Member
**
Offline Offline

Activity: 100
Merit: 10


View Profile
June 22, 2011, 06:23:11 AM
 #3047

I have no reward from the last 6 blocks.
Granted I only mine at 200 M/hash but usually I get something...

7 blocks with no reward now.. any idea what is going on?
scooter
Member
**
Offline Offline

Activity: 100
Merit: 10


View Profile
June 22, 2011, 06:56:08 AM
 #3048

I have no reward from the last 6 blocks.
Granted I only mine at 200 M/hash but usually I get something...

7 blocks with no reward now.. any idea what is going on?

Ok finally getting rewards
nosfera2
Newbie
*
Offline Offline

Activity: 42
Merit: 0



View Profile
June 22, 2011, 08:31:50 AM
 #3049

Sometimes, when blocks are found in a few seconds, most pool miners end up not getting anything at all for that block and a few lucky ones get to keep all the loot (rewards as high as a full bitcoin or more). It's just a matter of pure luck who manages to send in a share or two in such a short time.

See entries 5896 and 5898 in this screenshot for an example.

Since the idea of pooling is to eliminate luck and distribute the rewards of mining as fairly as possible, I'm proposing that in these cases, when a block is found sooner than say 30 seconds (admins can better determine the best time to use from their logs) the reward is shared out according to the share proportions of the previous + current blocks, so that everybody gets something.

The only possible 'downside' to this is that if someone happens to leave the pool in the few seconds it takes to find the last block they still get a share. However that is surely fairer than not rewarding all those who have been mining for the previous blocks and denying them the lucky strike that balances out the longer mining times on other blocks.

What do you guys think?


slush (OP)
Legendary
*
Offline Offline

Activity: 1386
Merit: 1070



View Profile WWW
June 22, 2011, 10:11:37 AM
 #3050

I have no reward from the last 6 blocks.
Granted I only mine at 200 M/hash but usually I get something...

7 blocks with no reward now.. any idea what is going on?

It takes some time to calculate everything, reward of last found block can change few times.

slush (OP)
Legendary
*
Offline Offline

Activity: 1386
Merit: 1070



View Profile WWW
June 22, 2011, 10:12:40 AM
 #3051

How come there are two entries for block 132473???

This looks fishy...

It's well known bug, but only cosmetic one. Link to blockexplorer is correct.

slush (OP)
Legendary
*
Offline Offline

Activity: 1386
Merit: 1070



View Profile WWW
June 22, 2011, 10:26:28 AM
 #3052

About blocks #5898 and #5896; They were very short, but both are invalid.  Probability of finding two solutions by two pool backends at same time (and twice in the row) is extremely small, but as you see, it may happen.

Pool backends are independent machines, which synchronize data as soon as possible, but broadcasting bitcoin block information is pretty complex stuff, so it may take one or two seconds. In those two blocks, two miners found solution too fast in a row and backends didn't notice that there is already valid solution for this block, so they decide to accept this solution, too. This leads to two 'invalid' blocks, but no (or only very small fraction) of mining power was wasted. I know that two 'invalid blocks' in a row looks weird, but there's not a simple solution to fix this issue and reject invalid block solution when another machine just found valid one.

Roland68
Member
**
Offline Offline

Activity: 103
Merit: 10



View Profile
June 22, 2011, 12:15:57 PM
 #3053

check hardware ....!!!! Huh

pool brocken again Huh
cosurgi
Sr. Member
****
Offline Offline

Activity: 298
Merit: 250


View Profile
June 22, 2011, 12:25:38 PM
 #3054

check hardware ....!!!! Huh
if you get "check hardware" errors, it means that solutions found by your GPU do not pass a short & simple verification by CPU. This means that your GPU is doing mistakes in calculation. You need to:

1) check temperature of your GPU, if it's above 85 C, you need to downclock it
2) if you overclocked your card, you need to downclock it
3) if none of above, you need to RMA your card, because it's broken.

Roland68
Member
**
Offline Offline

Activity: 103
Merit: 10



View Profile
June 22, 2011, 12:32:42 PM
 #3055

check hardware ....!!!! Huh
if you get "check hardware" errors, it means that solutions found by your GPU do not pass a short & simple verification by CPU. This means that your GPU is doing mistakes in calculation. You need to:

1) check temperature of your GPU, if it's above 85 C, you need to downclock it
2) if you overclocked your card, you need to downclock it
3) if none of above, you need to RMA your card, because it's broken.

Thanks for reply ...

temp is 75 deg. (5830)

gpu is 1000 and mem 600

this was ok until now ...(280 Mh)

will check again later ... thanks
nosfera2
Newbie
*
Offline Offline

Activity: 42
Merit: 0



View Profile
June 22, 2011, 01:13:12 PM
 #3056

About blocks #5898 and #5896; They were very short, but both are invalid.  Probability of finding two solutions by two pool backends at same time (and twice in the row) is extremely small, but as you see, it may happen.

Pool backends are independent machines, which synchronize data as soon as possible, but broadcasting bitcoin block information is pretty complex stuff, so it may take one or two seconds. In those two blocks, two miners found solution too fast in a row and backends didn't notice that there is already valid solution for this block, so they decide to accept this solution, too. This leads to two 'invalid' blocks, but no (or only very small fraction) of mining power was wasted. I know that two 'invalid blocks' in a row looks weird, but there's not a simple solution to fix this issue and reject invalid block solution when another machine just found valid one.

Thanks for your reply. I see now that the blocks turned out to be invalid, but that if they were OK? The reward would be shared only by the lucky people who submitted shared to those blocks and in one of those cases, a maximum of 60 people would share 50 BTC that really belong to the whole pool. This is what I am trying to fix by suggesting that the rewards of extremely short block runs are shared according to the results of the previous block.
finnthecelt
Full Member
***
Offline Offline

Activity: 140
Merit: 100


View Profile
June 22, 2011, 01:16:25 PM
 #3057

About blocks #5898 and #5896; They were very short, but both are invalid.  Probability of finding two solutions by two pool backends at same time (and twice in the row) is extremely small, but as you see, it may happen.

Pool backends are independent machines, which synchronize data as soon as possible, but broadcasting bitcoin block information is pretty complex stuff, so it may take one or two seconds. In those two blocks, two miners found solution too fast in a row and backends didn't notice that there is already valid solution for this block, so they decide to accept this solution, too. This leads to two 'invalid' blocks, but no (or only very small fraction) of mining power was wasted. I know that two 'invalid blocks' in a row looks weird, but there's not a simple solution to fix this issue and reject invalid block solution when another machine just found valid one.

Thanks for your reply. I see now that the blocks turned out to be invalid, but that if they were OK? The reward would be shared only by the lucky people who submitted shared to those blocks and in one of those cases, a maximum of 60 people would share 50 BTC that really belong to the whole pool. This is what I am trying to fix by suggesting that the rewards of extremely short block runs are shared according to the results of the previous block.

Yes, of course my reward was very high for those blocks. Now invalid. Bummer.
slush (OP)
Legendary
*
Offline Offline

Activity: 1386
Merit: 1070



View Profile WWW
June 22, 2011, 05:39:56 PM
 #3058

I just released email confirmations for wallet changes on profile page.

Kuber
Newbie
*
Offline Offline

Activity: 25
Merit: 0


View Profile
June 22, 2011, 06:19:58 PM
 #3059

I just released email confirmations for wallet changes on profile page.

Thumps up Smiley
kerogre256
Full Member
***
Offline Offline

Activity: 161
Merit: 100


View Profile
June 22, 2011, 10:02:34 PM
 #3060

Hi how long its take to send coin ? or how to check it Smiley I  mine my 1 coin but it was not send to me ? Cry
Pages: « 1 ... 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 [153] 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 ... 1155 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!