kano (OP)
Legendary
 Online
Activity: 4494
Merit: 1805
Linux since 1997 RedHat 4
|
 |
March 15, 2016, 01:14:19 AM |
|
Why am I getting an error when I try to input my payout address?
What error, what username ... |
|
|
|
|
|
|
|
|
The Bitcoin software, network, and concept is called "Bitcoin" with a capitalized "B". Bitcoin currency units are called "bitcoins" with a lowercase "b" -- this is often abbreviated BTC.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
RealMalatesta
Legendary
 Offline
Activity: 2338
Merit: 1124
|
|
March 15, 2016, 01:15:58 AM |
|
Well, that's a few pages of 'interesting' comments  I was just gonna do a quick click though all these pages since 'last night' since I'm working on the next 4 payouts that are overdue, but then decided I better post some more details rather than wait until after I finish processing the payouts. Yes I've sent out (and all but one person) has received the payouts for blocks 402342 and 402347 We confirmed the 2 payouts Over the last 2 days I've been doing a lot of work on the share tracking to determine if miners are doing the wrong thing (intentionally or unintentionally) This is of course related to the stuff organofcorti mentioned and I posted about his comments here also. I've found a few miners, 2 are pretty much certain, and the rest very likely, using hardware that doesn't mine properly. They all started mining in January, their total payouts since then have been less than 1 block. These are miners that have the same problem as that 'other' pool. I wonder if they just moved their hardware here, from there? The pool logs ALL sorts of information that I will go through later to see if there is any correlation between them all (and any other miners) Then I'll contact them some time after that ... At this point I'm going to stop all their payouts, so they end up in their 'dust', until they find blocks. Also, the block finding luck will need to be better than 100%, since they need to cover the pool's loss of their payouts they've received. i.e. they have about a 2/3 chance of finding a block in time to cover their ... actions. See, I see it as: if I ask for the BTC back, that they've been paid, I doubt anyone would give it back and blame their choice of hardware on ... well no idea ... but blaming it on the pool is not gonna work for me. If they run away, then the dust building up in their accounts will eventually be redistributed based on the payout it should have been in, back to everyone else as 'adjustments' later once that is possible. It's not a lot of BTC, single digits on each account, and total is, as I said, less than a block. This is also now the next code change I've got to do, a way to simply flag an account to be in this state of no 'auto' payout so I don't have to manually intervene with these accounts during the payout process. I'll post more details at some later time, but yeah I better get back to these 4 payouts overdue since last night. Thanks for the update. I assume it is rather hard to see what gear they were using...? |
|
|
|
|
|
wolfen
|
|
March 15, 2016, 01:24:02 AM |
|
Do we know if this is real miners or rentals doing bad things?
Maybe we should have rental accounts and hardware accounts.
|
For those about to block we salute you! AC->BTC
|
|
|
|
wolfen
|
|
March 15, 2016, 01:38:26 AM |
|
Kmstudio was last block paid
Kano, thanks for all your investigating, I know it is very time consuming.
|
For those about to block we salute you! AC->BTC
|
|
|
|
Crispyato
|
|
March 15, 2016, 01:40:28 AM |
|
Glad things are rolling again. Sounds like a shitty problem to troubleshoot. I mean you almost have to make it so the code prevents the issue full stop or lock out new accounts. Anyone can make a new pool identity and change IP addresses...
Let me know if you see any issues on my account. I can always end the rentals of any problem rigs. Sorry for being one the people bugging out, though I can't promise I won't be tripping again. I'll try to save a little coin so I have a bit more breathing room. I can't wait for the halving when I can get some new gear and be a real miner again. I just can't risk the ROI time on a profitable rig purchase right now.
|
|
|
|
|
kano (OP)
Legendary
Online
Activity: 4494
Merit: 1805
Linux since 1997 RedHat 4
|
|
March 15, 2016, 01:42:51 AM |
|
Yeah I'll delete any questions asking "Is it me?" If you are missing 4-6 payouts after the next 4 have been sent, which I still haven't completed yet, then you probably are one of them  If you are asking "Is it me?" just coz you want me to answer that question, don't. |
|
|
|
|
krisgt30
|
|
March 15, 2016, 01:43:00 AM |
|
Well, that's a few pages of 'interesting' comments I was just gonna do a quick click though all these pages since 'last night' since I'm working on the next 4 payouts that are overdue, but then decided I better post some more details rather than wait until after I finish processing the payouts. Yes I've sent out (and all but one person) has received the payouts for blocks 402342 and 402347 We confirmed the 2 payouts Over the last 2 days I've been doing a lot of work on the share tracking to determine if miners are doing the wrong thing (intentionally or unintentionally) This is of course related to the stuff organofcorti mentioned and I posted about his comments here also. I've found a few miners, 2 are pretty much certain, and the rest very likely, using hardware that doesn't mine properly. They all started mining in January, their total payouts since then have been less than 1 block. These are miners that have the same problem as that 'other' pool. I wonder if they just moved their hardware here, from there? The pool logs ALL sorts of information that I will go through later to see if there is any correlation between them all (and any other miners) Then I'll contact them some time after that ... At this point I'm going to stop all their payouts, so they end up in their 'dust', until they find blocks. Also, the block finding luck will need to be better than 100%, since they need to cover the pool's loss of their payouts they've received. i.e. they have about a 2/3 chance of finding a block in time to cover their ... actions. See, I see it as: if I ask for the BTC back, that they've been paid, I doubt anyone would give it back and blame their choice of hardware on ... well no idea ... but blaming it on the pool is not gonna work for me. If they run away, then the dust building up in their accounts will eventually be redistributed based on the payout it should have been in, back to everyone else as 'adjustments' later once that is possible. It's not a lot of BTC, single digits on each account, and total is, as I said, less than a block. This is also now the next code change I've got to do, a way to simply flag an account to be in this state of no 'auto' payout so I don't have to manually intervene with these accounts during the payout process. I'll post more details at some later time, but yeah I better get back to these 4 payouts overdue since last night. An approach like this, is exactly what I was saying should have been done by slush if he gave a crap at all about his miners, which I got flak for from his fanboys. Out the culprits, redistribute the btc, and all is made good in the world. You are doing it properly, and for this I commend you. Keep up the good work and let us know if there is anything specifically we should look out for (hardware, firmware revs, ip addresses to watch, etc) |
www.bcmonster.com Multi pool, pools for BTC, BCA, LCC, KMD, HUSH and ZEN -Donate:1QGZQBhXMo2jVc45wLEsp2bn5agF8SZSuY
|
|
|
hoosier_13
Member
Offline
Activity: 62
Merit: 10
|
|
March 15, 2016, 01:58:05 AM |
|
Well, that's a few pages of 'interesting' comments I was just gonna do a quick click though all these pages since 'last night' since I'm working on the next 4 payouts that are overdue, but then decided I better post some more details rather than wait until after I finish processing the payouts. Yes I've sent out (and all but one person) has received the payouts for blocks 402342 and 402347 We confirmed the 2 payouts Over the last 2 days I've been doing a lot of work on the share tracking to determine if miners are doing the wrong thing (intentionally or unintentionally) This is of course related to the stuff organofcorti mentioned and I posted about his comments here also. I've found a few miners, 2 are pretty much certain, and the rest very likely, using hardware that doesn't mine properly. They all started mining in January, their total payouts since then have been less than 1 block. These are miners that have the same problem as that 'other' pool. I wonder if they just moved their hardware here, from there? The pool logs ALL sorts of information that I will go through later to see if there is any correlation between them all (and any other miners) Then I'll contact them some time after that ... At this point I'm going to stop all their payouts, so they end up in their 'dust', until they find blocks. Also, the block finding luck will need to be better than 100%, since they need to cover the pool's loss of their payouts they've received. i.e. they have about a 2/3 chance of finding a block in time to cover their ... actions. See, I see it as: if I ask for the BTC back, that they've been paid, I doubt anyone would give it back and blame their choice of hardware on ... well no idea ... but blaming it on the pool is not gonna work for me. If they run away, then the dust building up in their accounts will eventually be redistributed based on the payout it should have been in, back to everyone else as 'adjustments' later once that is possible. It's not a lot of BTC, single digits on each account, and total is, as I said, less than a block. This is also now the next code change I've got to do, a way to simply flag an account to be in this state of no 'auto' payout so I don't have to manually intervene with these accounts during the payout process. I'll post more details at some later time, but yeah I better get back to these 4 payouts overdue since last night. An approach like this, is exactly what I was saying should have been done by slush if he gave a crap at all about his miners, which I got flak for from his fanboys. Out the culprits, redistribute the btc, and all is made good in the world. You are doing it properly, and for this I commend you. Keep up the good work and let us know if there is anything specifically we should look out for (hardware, firmware revs, ip addresses to watch, etc) Agree, I got screwed by Slush |
Bitrated user: TICH13.
|
|
|
|
Crispyato
|
|
March 15, 2016, 02:05:52 AM |
|
Do we know if this is real miners or rentals doing bad things?
Maybe we should have rental accounts and hardware accounts.
BTC Guild used to offer a private IP for rentals and higher hash rates. I know I've had to end 10 rentals in the past two days for bad stats and going offline too much. If I were mining my own they would be steady with almost no downtime. I was also screwed by slush, bigtime. Mining loyally 2012-2015. Held on way to long. |
|
|
|
|
|
wolfen
|
|
March 15, 2016, 02:09:59 AM |
|
I have the same firmware on all my s7's, four have hit blocks so that looks good.
Now rentals I have no idea.
|
For those about to block we salute you! AC->BTC
|
|
|
philipma1957
Legendary
Offline
Activity: 4116
Merit: 7849
'The right to privacy matters'
|
|
March 15, 2016, 02:14:00 AM |
|
I have the same firmware on all my s7's, four have hit blocks so that looks good.
Now rentals I have no idea.
when the time comes I would love to know if this is a rental issue |
|
|
|
|
wolfen
|
|
March 15, 2016, 02:19:21 AM |
|
One block please. Don't hold the mayo.
|
For those about to block we salute you! AC->BTC
|
|
|
|
bittalc1
|
|
March 15, 2016, 02:24:40 AM |
|
If they done this intentionaly i hope that they never get the BTC, i lost 0.7 on rentals during this bad luck period.
|
|
|
|
|
|
nhando
|
|
March 15, 2016, 02:34:43 AM |
|
So what block have been paid out thus far?
I only got up to
402347
|
Just "Mining" my own business.
|
|
|
|
Crispyato
|
|
March 15, 2016, 02:37:56 AM |
|
I have the same firmware on all my s7's, four have hit blocks so that looks good.
Now rentals I have no idea.
when the time comes I would love to know if this is a rental issue I'm really curious also. If it is I may seek renting a miner directly from someone instead of using a rental site or go with used rig hosted when using kano pool. I don't do NH because I don't know what's mining on what firmware. If I had 10 rigs with varying diffs and manufacturers I wouldn't put them on the same worker. The price is the only one worth it though, if kano says it doesn't hurt the pool I may try. I will say I hit a block here with a rental and 30 blocks in other pools in the past renting. The ones in the past were in better diff days... Phillip, do have any links on like a small shed type solar set up? Something you could fit in a small area without integrating power from the line. Like 1-2rig shack or something similar. If I could sell some PC parts and get a little solar set up I could mine on my own a little. Maybe my sp20 and a couple s3. Then I would have solar setup left for upgrade time. |
|
|
|
|
firetreeactual
Legendary
Offline
Activity: 952
Merit: 1003
|
|
March 15, 2016, 02:38:05 AM |
|
Well, that's a few pages of 'interesting' comments I was just gonna do a quick click though all these pages since 'last night' since I'm working on the next 4 payouts that are overdue, but then decided I better post some more details rather than wait until after I finish processing the payouts. Yes I've sent out (and all but one person) has received the payouts for blocks 402342 and 402347 We confirmed the 2 payouts Over the last 2 days I've been doing a lot of work on the share tracking to determine if miners are doing the wrong thing (intentionally or unintentionally) This is of course related to the stuff organofcorti mentioned and I posted about his comments here also. I've found a few miners, 2 are pretty much certain, and the rest very likely, using hardware that doesn't mine properly. They all started mining in January, their total payouts since then have been less than 1 block. These are miners that have the same problem as that 'other' pool. I wonder if they just moved their hardware here, from there? The pool logs ALL sorts of information that I will go through later to see if there is any correlation between them all (and any other miners) Then I'll contact them some time after that ... At this point I'm going to stop all their payouts, so they end up in their 'dust', until they find blocks. Also, the block finding luck will need to be better than 100%, since they need to cover the pool's loss of their payouts they've received. i.e. they have about a 2/3 chance of finding a block in time to cover their ... actions. See, I see it as: if I ask for the BTC back, that they've been paid, I doubt anyone would give it back and blame their choice of hardware on ... well no idea ... but blaming it on the pool is not gonna work for me. If they run away, then the dust building up in their accounts will eventually be redistributed based on the payout it should have been in, back to everyone else as 'adjustments' later once that is possible. It's not a lot of BTC, single digits on each account, and total is, as I said, less than a block. This is also now the next code change I've got to do, a way to simply flag an account to be in this state of no 'auto' payout so I don't have to manually intervene with these accounts during the payout process. I'll post more details at some later time, but yeah I better get back to these 4 payouts overdue since last night. Thanks, kid. Appreciated.  |
To infinity and beyond...on two 741s and one of only 3...nope, make that 4...full nodes in Hawaii...on <30A. (I have other gear on the Hoth ice planet)
|
|
|
mtmining2
Newbie
Offline
Activity: 35
Merit: 0
|
|
March 15, 2016, 02:38:24 AM |
|
So what block have been paid out thus far?
I only got up to
402347
Same here |
|
|
|
|
philipma1957
Legendary
Offline
Activity: 4116
Merit: 7849
'The right to privacy matters'
|
|
March 15, 2016, 02:38:37 AM |
|
So what block have been paid out thus far?
I only got up to
402347
me too and I think that is correct now I have two accounts one of which is 100 % avalon6 that was paid to block 402347 and the larger account which is s-7 avalon6 and many rentals is paid to 402347 |
|
|
|
|
nhando
|
|
March 15, 2016, 02:41:11 AM |
|
Ok, just want to be in sync.
|
Just "Mining" my own business.
|
|
|
kano (OP)
Legendary
Online
Activity: 4494
Merit: 1805
Linux since 1997 RedHat 4
|
|
March 15, 2016, 02:46:04 AM |
|
... and to avoid me having to manually adjust payout amounts and doing that multiple times, I'll be restarting CKDB in about 40 minutes.
This update is to allow me to simply flag an account related to this, and the rest of my payout processing will do what's needed.
As usual for a CKDB restart:
No miners will be affected ... at all.
...and ... I'll wait for the first shift summarisation after the hour to ensure the restart runs quickly.
A summarisation just completed, so the one after the hour will be ~40minutes from now.
So, the CKDB restart will be at roughly 03:25am UTC
The 4 overdue payouts will be sent out shortly after that with the correct adjustments.
402505 402556 402561 402567
|
|
|
|
|
