Bitcoin Forum
May 09, 2024, 04:45:56 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 [640] 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 ... 2248 »
  Print  
Author Topic: KanoPool since 2014 🐈 - PPLNS and Solo 0.5% fee - Worldwide - 2436 blocks  (Read 5350310 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic. (50 posts by 3+ users deleted.)
grifdogr
Newbie
*
Offline Offline

Activity: 9
Merit: 0


View Profile
March 15, 2016, 02:50:11 AM
 #12781

Hi all, I am new to server and fairly new to mining, I started at eligius after buying a machine 2 years ago, then bought s5's and relivested and was fearfully trying different servers and was on Bitminter and then they went bad and after asking a question after almost a week about payouts I got a smart.. remark and after another day I searched and found this place.
 I stopped mining after a day of dead and reran my electric so that as things get better I may buy some more, I only have 7 s7's as of now but hope to add more as I can from earnings.
After that long story I would like to say I have been reading the posts and see the responses and work going on behind the scenes and really appreciate the effort and hope everything works out for all of us.
I am pretty uninformed on a lot of this but am constantly reading and learning how things work but still like not knowing the whole gambit.
I would like to know under worker management if I should have a value in there or not and if it helps?
BitcoinCleanup.com: Learn why Bitcoin isn't bad for the environment
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715273156
Hero Member
*
Offline Offline

Posts: 1715273156

View Profile Personal Message (Offline)

Ignore
1715273156
Reply with quote  #2

1715273156
Report to moderator
1715273156
Hero Member
*
Offline Offline

Posts: 1715273156

View Profile Personal Message (Offline)

Ignore
1715273156
Reply with quote  #2

1715273156
Report to moderator
kano (OP)
Legendary
*
Offline Offline

Activity: 4494
Merit: 1808


Linux since 1997 RedHat 4


View Profile
March 15, 2016, 02:54:02 AM
 #12782

...
I would like to know under worker management if I should have a value in there or not and if it helps?
Unless there's a problem with your miner, you are best to leave the difficulty at the pool default.

However, you can't make it lower than the pool makes it, but you can put it up higher.

Pool: https://kano.is - low 0.5% fee PPLNS 3 Days - Most reliable Solo with ONLY 0.5% fee   Bitcointalk thread: Forum
Discord support invite at https://kano.is/ Majority developer of the ckpool code - k for kano
The ONLY active original developer of cgminer. Original master git: https://github.com/kanoi/cgminer
grifdogr
Newbie
*
Offline Offline

Activity: 9
Merit: 0


View Profile
March 15, 2016, 03:00:28 AM
 #12783

Thanks, I will leave it alone, My systems are great and I just saw that option and was curious.
Hoping to see my name as block finder one day soon... I know it probably makes no dif but will make me smile Grin
PeaMine
Hero Member
*****
Offline Offline

Activity: 979
Merit: 510



View Profile
March 15, 2016, 03:29:20 AM
 #12784

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

402347 is also the last block I got paid on.
On the 13th, I show only 1 payout pending from the Account Payouts, normally is 4-6, did we just have bad luck that day?
6 blocks show under Payments, but my wallet hasn't received them yet.

Datacenter Technician and Electrician.  If you have any questions feel free to ask me as I am generally bored looking at logs and happy to help during free time.
kano (OP)
Legendary
*
Offline Offline

Activity: 4494
Merit: 1808


Linux since 1997 RedHat 4


View Profile
March 15, 2016, 03:43:04 AM
 #12785

... 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
Restart completed.
Took 9 minutes.

Pool: https://kano.is - low 0.5% fee PPLNS 3 Days - Most reliable Solo with ONLY 0.5% fee   Bitcointalk thread: Forum
Discord support invite at https://kano.is/ Majority developer of the ckpool code - k for kano
The ONLY active original developer of cgminer. Original master git: https://github.com/kanoi/cgminer
clgrissom3
Legendary
*
Offline Offline

Activity: 1722
Merit: 1032


Carl, aka Sonny :)


View Profile
March 15, 2016, 04:22:19 AM
 #12786

Well, that's a few pages of 'interesting' comments Smiley

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 Smiley

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.

It seems like there are two things to be done to make it right...one is to pay back BTC that was gained improperly and the second is to take the offending hardware out of commission as soon as possible.  Getting the hardware that doesn't mine properly off the pool is critical to stopping the problem.  Are you able to identify which worker(s) need to be shut down?  Are you going to communicate this information directly to the owners?  I would want to shut down any problem machines right away if they were in my collection...
SergES
Member
**
Offline Offline

Activity: 81
Merit: 10


View Profile
March 15, 2016, 04:41:47 AM
 #12787

So what is the actual problem? Irregular payment of these miners? Explain what they did.
aarons6
Legendary
*
Offline Offline

Activity: 1736
Merit: 1006


View Profile
March 15, 2016, 04:45:57 AM
 #12788

So what is the actual problem? Irregular payment of these miners? Explain what they did.

by my understanding is they have very fast equipment.. ones that surely should have found a block in the time they have been mining here.. but they have produced zero blocks.

but im not very knowledgeable on how it works.. i do know my s5s have never found a bitcoin block in the year ive owned them.. :/

now i have a s7 pointed here, hopefully it finds a block for the pool someday.
fvineyard
Member
**
Offline Offline

Activity: 135
Merit: 11


View Profile
March 15, 2016, 04:54:03 AM
 #12789

I agree. If I have any misbehaving or defective hardware I would hope it could be identified so I can shut it down. I would also be open to repayment to the pool as appropriate as long as supporting facts to back up the calculation of the BTC owed.

A PM would be an appropriate means of contact to prevent any hurt feelings in the case of a poor choice of hardware.

I speak for myself only, and my words are not meant to represent any other individual. I like this pool and want to do right by it.

fvineyard
clgrissom3
Legendary
*
Offline Offline

Activity: 1722
Merit: 1032


Carl, aka Sonny :)


View Profile
March 15, 2016, 05:00:42 AM
 #12790

I agree. If I have any misbehaving or defective hardware I would hope it could be identified so I can shut it down. I would also be open to repayment to the pool as appropriate as long as supporting facts to back up the calculation of the BTC owed.

A PM would be an appropriate means of contact to prevent any hurt feelings in the case of a poor choice of hardware.

I speak for myself only, and my words are not meant to represent any other individual. I like this pool and want to do right by it.

fvineyard

That's kind of where I was going with my questions...I would want to do the right thing including shutting down any funky equipment I may have pointing here and repaying what I should if I caused any issues.
SergES
Member
**
Offline Offline

Activity: 81
Merit: 10


View Profile
March 15, 2016, 05:03:13 AM
 #12791

Rest payment accept.
kano (OP)
Legendary
*
Offline Offline

Activity: 4494
Merit: 1808


Linux since 1997 RedHat 4


View Profile
March 15, 2016, 05:03:59 AM
 #12792

...
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 ...
...

It seems like there are two things to be done to make it right...one is to pay back BTC that was gained improperly and the second is to take the offending hardware out of commission as soon as possible.  Getting the hardware that doesn't mine properly off the pool is critical to stopping the problem.  Are you able to identify which worker(s) need to be shut down?  Are you going to communicate this information directly to the owners?  I would want to shut down any problem machines right away if they were in my collection...
... removed all the rest from my post Smiley

Pool: https://kano.is - low 0.5% fee PPLNS 3 Days - Most reliable Solo with ONLY 0.5% fee   Bitcointalk thread: Forum
Discord support invite at https://kano.is/ Majority developer of the ckpool code - k for kano
The ONLY active original developer of cgminer. Original master git: https://github.com/kanoi/cgminer
kano (OP)
Legendary
*
Offline Offline

Activity: 4494
Merit: 1808


Linux since 1997 RedHat 4


View Profile
March 15, 2016, 05:05:16 AM
 #12793

The 4 outstanding payouts have been sent.
Not confirmed yet:
402505 920f9ab293bd2013bf6183bfd5b6f64a5cd5be1f45a8fafd8d7bd7190631b6fb
402556 8a247e082506a107c261c7d54f7b0f32e8f12b27361054ce011e201121a95010
402561 48d96e74e46fadfb796da5295a145fe9b0485893dd4863250d4eb24ff2312281
402567 c09b5c003e67cf72c56685e22edb4df7e8330057fbb5f340f492f92c5310a0f6

Pool: https://kano.is - low 0.5% fee PPLNS 3 Days - Most reliable Solo with ONLY 0.5% fee   Bitcointalk thread: Forum
Discord support invite at https://kano.is/ Majority developer of the ckpool code - k for kano
The ONLY active original developer of cgminer. Original master git: https://github.com/kanoi/cgminer
SergES
Member
**
Offline Offline

Activity: 81
Merit: 10


View Profile
March 15, 2016, 05:06:41 AM
 #12794

Bad miners have done it on real hardware (ASIC), or through contracts (nicehash)?...
clgrissom3
Legendary
*
Offline Offline

Activity: 1722
Merit: 1032


Carl, aka Sonny :)


View Profile
March 15, 2016, 05:07:23 AM
 #12795

...
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 ...
...

It seems like there are two things to be done to make it right...one is to pay back BTC that was gained improperly and the second is to take the offending hardware out of commission as soon as possible.  Getting the hardware that doesn't mine properly off the pool is critical to stopping the problem.  Are you able to identify which worker(s) need to be shut down?  Are you going to communicate this information directly to the owners?  I would want to shut down any problem machines right away if they were in my collection...
... removed all the rest from my post Smiley

 Grin Dang it!  I read your post frontwards and backwards also!
hawkfish007
Hero Member
*****
Offline Offline

Activity: 895
Merit: 504


View Profile
March 15, 2016, 05:08:36 AM
 #12796

The 4 outstanding payouts have been sent.
Not confirmed yet:
402505 920f9ab293bd2013bf6183bfd5b6f64a5cd5be1f45a8fafd8d7bd7190631b6fb
402556 8a247e082506a107c261c7d54f7b0f32e8f12b27361054ce011e201121a95010
402561 48d96e74e46fadfb796da5295a145fe9b0485893dd4863250d4eb24ff2312281
402567 c09b5c003e67cf72c56685e22edb4df7e8330057fbb5f340f492f92c5310a0f6


I see 4 incoming payments on Circle Smiley I run only S7s, guess I am out of the woods  Wink

For quality risers, splitters or 133 CFM fans, please visit my eBay listings,
http://www.ebay.com/sch/hawkfish007/m.html?_ipg=50&_sop=12&_rdc=1
Epoch
Legendary
*
Offline Offline

Activity: 922
Merit: 1003



View Profile
March 15, 2016, 05:11:25 AM
 #12797

I do know my s5's have never found a bitcoin block in the year I've owned them.
Now i have a s7 pointed here, hopefully it finds a block for the pool someday.
The reality is that an S7 is expected to find a block every 4.7 years under the current difficulty. Think about that for a second. 4.7 years.

So sadly, no, your S7 is unlikely to hit a block here (or anywhere). And this is a good illustration of why most miners, especially the smaller ones, prefer pools to solo; a small solo miner can hash for months or years without getting any payout at all.
vh
Hero Member
*****
Offline Offline

Activity: 699
Merit: 666


View Profile
March 15, 2016, 05:25:13 AM
 #12798

I do know my s5's have never found a bitcoin block in the year I've owned them.
Now i have a s7 pointed here, hopefully it finds a block for the pool someday.
The reality is that an S7 is expected to find a block every 4.7 years under the current difficulty. Think about that for a second. 4.7 years.

So sadly, no, your S7 is unlikely to hit a block here (or anywhere). And this is a good illustration of why most miners, especially the smaller ones, prefer pools to solo; a small solo miner can hash for months or years without getting any payout at all.

don't be such a bummer.   the same s7 would have a 1 in 2 chance in 2.3 years, 1 in 4 in 1.15 year, 1 in 16 every 3.4 months, a 1 in 54 every month, a 1:233 every week.

kano (OP)
Legendary
*
Offline Offline

Activity: 4494
Merit: 1808


Linux since 1997 RedHat 4


View Profile
March 15, 2016, 05:30:24 AM
 #12799

The 4 outstanding payouts have been sent.
Not confirmed yet:
402505 920f9ab293bd2013bf6183bfd5b6f64a5cd5be1f45a8fafd8d7bd7190631b6fb
402556 8a247e082506a107c261c7d54f7b0f32e8f12b27361054ce011e201121a95010
402561 48d96e74e46fadfb796da5295a145fe9b0485893dd4863250d4eb24ff2312281
402567 c09b5c003e67cf72c56685e22edb4df7e8330057fbb5f340f492f92c5310a0f6


I see 4 incoming payments on Circle Smiley I run only S7s, guess I am out of the woods  Wink
All 4 confirmed.

Pool: https://kano.is - low 0.5% fee PPLNS 3 Days - Most reliable Solo with ONLY 0.5% fee   Bitcointalk thread: Forum
Discord support invite at https://kano.is/ Majority developer of the ckpool code - k for kano
The ONLY active original developer of cgminer. Original master git: https://github.com/kanoi/cgminer
kano (OP)
Legendary
*
Offline Offline

Activity: 4494
Merit: 1808


Linux since 1997 RedHat 4


View Profile
March 15, 2016, 05:33:38 AM
 #12800

I do know my s5's have never found a bitcoin block in the year I've owned them.
Now i have a s7 pointed here, hopefully it finds a block for the pool someday.
The reality is that an S7 is expected to find a block every 4.7 years under the current difficulty. Think about that for a second. 4.7 years.

So sadly, no, your S7 is unlikely to hit a block here (or anywhere). And this is a good illustration of why most miners, especially the smaller ones, prefer pools to solo; a small solo miner can hash for months or years without getting any payout at all.

don't be such a bummer.   the same s7 would have a 1 in 2 chance in 2.3 years, 1 in 4 in 1.15 year, 1 in 16 every 3.4 months, a 1 in 54 every month, a 1:233 every week.

Or if you use my pool calc page ... Smiley

http://tradebtc.net/bitcalc.php

5.5THs (whatever an S7 is? Tongue)
Chance of you finding a block in one day: 1 in 1,431.9

Pool: https://kano.is - low 0.5% fee PPLNS 3 Days - Most reliable Solo with ONLY 0.5% fee   Bitcointalk thread: Forum
Discord support invite at https://kano.is/ Majority developer of the ckpool code - k for kano
The ONLY active original developer of cgminer. Original master git: https://github.com/kanoi/cgminer
Pages: « 1 ... 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 [640] 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 ... 2248 »
  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!