Bitcoin Forum
June 25, 2024, 01:54:37 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 [558] 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 ... 2248 »
  Print  
Author Topic: KanoPool since 2014 🐈 - PPLNS and Solo 0.5% fee - Worldwide - 2437 blocks  (Read 5350869 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.)
VirosaGITS
Legendary
*
Offline Offline

Activity: 1302
Merit: 1068



View Profile
February 23, 2016, 09:32:10 AM
 #11141

Meanwhile Smiley Regarding the pool wallet.

I've had a good think about how I do it and what changes I could make.

It's actually not all that difficult to do as I do already with one change, combine them once a day rather than send each one when it's due.
I like the process I have at the moment of checks and balances - that are beyond what many may expect Smiley - but I could simply continue that to get to the point where I'm happy with each individual result, but not send the result, then later run another process that picks a set of payouts from earlier in the process and combines them all, once a day.

That way I already know they've passed all inspections, and it's just dependent on me creating a new step that can add the earlier data correctly - so dust payouts are combined, and dust only not sent if the combination is below 10k satoshi.

Yeah I really don't want a pool bank for everyone, and I think this change would fit in well, and reduce the number of transactions and the payout division caused by our average expected more than one block a day.

Any comments?

(Edit: if anyone didn't notice, the last address in each payout is the total dust in each, which has always been more than zero except once)

Daily or bi-daily sound good. Daily works. Sometimes getting paid more often can be nice, but 5 payout is a bit much and if the pool continue to grow in % of total hashrate, it will just get ridiculous.

Then again, if you internally do all the work and only release bundled payments, you'll still get more and more work to do.


                      ▄▄█████▄▄
                    ▐████████████▄
                   ▄█▀▀▀▀▀▀▀██████▌
             █▄  ▄█▀           ▀▀█
              ▀▀▀███▄▄▄▄▄▄▄▄▄▄   █▄   ▄

               ▄▀▀         ▀▀▀▀▀▀▀██▀▀▀
         ▄▄▄▄▄█▄▄ ▄▀▀▄ ▄▄▄▄▄▄▄▄▄▄▄▄▄█▄▄▄▄
         ████▒▒███    ████▒▒████▌
    ▀█▄ ▀
███████▄ ███▒▒███      ██▒▒█████       ▀█▄
 ███████ ▀█▒▒████     ▄█▒▒█████▀         ▀█ ▄  ▄▄
  ██████  ▌▀▀█████▄▄▄███████▀▀            ███▄███▌
 █████████  █████▀▀█▀▀██████▌             ██████▀
 ▀█████████ ███▄  ███   ▐███▌ ▄██       ▄█████▀
     ▀▀    ▀▀███████████████▄▄████▄▄▄▄█▀▀▀▀▀
               ▀▀▀███▀▀▀      ██████▄
                               ▀▀▀▀▀

▄█████████████████████████████▄
███████████████████████████████
███████████████████████████████
███████████████████████████████
█████████▀▀█████████▀▀█████████
███████ ▄▀▀         ▀▀▄ ███████
██████                   ██████
█████▌     ▄▄     ▄▄     ▐█████
█████     ████   ████     █████
█████      ▀▀     ▀▀      █████
█████▄   ▀▄▄▄     ▄▄▄▀   ▄█████
████████▄▄▄█████████▄▄▄████████
███████████████████████████████
███████████████████████████████
███████████████████████████████
 ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
█ █
█ █
█ █
█ █
█ █
omega015
Full Member
***
Offline Offline

Activity: 182
Merit: 100


View Profile
February 23, 2016, 10:42:54 AM
Last edit: February 23, 2016, 11:44:57 AM by omega015
 #11142

Well done Rdawg with your second block   Smiley

EDIT: and a nice sweet one from manel with his first block
sorry2xs
Legendary
*
Offline Offline

Activity: 924
Merit: 1000


Dark Passenger Bitcoin miner 2013,Bitcoin node


View Profile
February 23, 2016, 11:56:12 AM
 #11143

Well Ain't that special

Please tip the Node 1MPWKB23NsZsXHANnFwVAWT86mL24fqAjF; KO4UX
THAT NO GOOD DO GOODER BAT!!!
citronick
Legendary
*
Offline Offline

Activity: 1834
Merit: 1080


---- winter*juvia -----


View Profile
February 23, 2016, 12:36:13 PM
 #11144

Well done Rdawg with your second block   Smiley

EDIT: and a nice sweet one from manel with his first block

When the small guys find blocks, it's a prelude to a party....

If I provided you good and useful info or just a smile to your day, consider sending me merit points to further validate this Bitcointalk account ~ useful for future account recovery...
masterwolf
Newbie
*
Offline Offline

Activity: 25
Merit: 0


View Profile
February 23, 2016, 01:04:07 PM
 #11145

Meanwhile Smiley Regarding the pool wallet.

I've had a good think about how I do it and what changes I could make.

It's actually not all that difficult to do as I do already with one change, combine them once a day rather than send each one when it's due.
I like the process I have at the moment of checks and balances - that are beyond what many may expect Smiley - but I could simply continue that to get to the point where I'm happy with each individual result, but not send the result, then later run another process that picks a set of payouts from earlier in the process and combines them all, once a day.

That way I already know they've passed all inspections, and it's just dependent on me creating a new step that can add the earlier data correctly - so dust payouts are combined, and dust only not sent if the combination is below 10k satoshi.

Yeah I really don't want a pool bank for everyone, and I think this change would fit in well, and reduce the number of transactions and the payout division caused by our average expected more than one block a day.

Any comments?

(Edit: if anyone didn't notice, the last address in each payout is the total dust in each, which has always been more than zero except once)

Seems perfectly fine Smiley
vh
Hero Member
*****
Offline Offline

Activity: 699
Merit: 666


View Profile
February 23, 2016, 02:32:34 PM
Last edit: February 23, 2016, 02:45:23 PM by vh
 #11146

Meanwhile Smiley Regarding the pool wallet.

I've had a good think about how I do it and what changes I could make.

It's actually not all that difficult to do as I do already with one change, combine them once a day rather than send each one when it's due.
I like the process I have at the moment of checks and balances - that are beyond what many may expect Smiley - but I could simply continue that to get to the point where I'm happy with each individual result, but not send the result, then later run another process that picks a set of payouts from earlier in the process and combines them all, once a day.

That way I already know they've passed all inspections, and it's just dependent on me creating a new step that can add the earlier data correctly - so dust payouts are combined, and dust only not sent if the combination is below 10k satoshi.

Yeah I really don't want a pool bank for everyone, and I think this change would fit in well, and reduce the number of transactions and the payout division caused by our average expected more than one block a day.

Any comments?

(Edit: if anyone didn't notice, the last address in each payout is the total dust in each, which has always been more than zero except once)

misc comments:

1 - if (big if) anyone has been doing independent auditing, then that will be a bit harder to pair in/out via blocktrail BTC(n).   i like the way it is now, but okay with either since more daily blocks (eventually) mean more payout to manage and more dust (many of us don't want to accept we're insignificant yet although we see it coming with diff changes).  
2 - maybe a good time to also add confirmed payouts to user payment page if this happens?
3 - side note: iphone app's payout notifications will move to optional config soon but could temporarily glitch until i see the new transaction and make a slight adjust for value verification.

edit - random idea: if you do keep 1-to-1 as due, maybe you can consider using that last dust address as a get out of jail free card to payout a dust user if > some value.

Legacy2005
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250


View Profile
February 23, 2016, 03:21:25 PM
 #11147

im fine with however you end up doing the payouts. You know whats best for you and the pool and trust your judgement/decision. You will never make 100% of the people happy with how its done so do what you feel is best.
philipma1957
Legendary
*
Online Online

Activity: 4158
Merit: 8057


'The right to privacy matters'


View Profile WWW
February 23, 2016, 03:39:16 PM
 #11148

No issues if things are send with some extra $$ behind it. I always use 8 confirmations at the slowest 10 and haven't had a 'lost' transaction yet.

For testing I sent one with 20 confirmations and it took about 14 hours to finally confirm.

yeah but even extra cash  for the fees still does not help all of the time.

look at this

this is a hefty fee,  and I now need to wait to finish business as those coins are not clearing.

This is not just a kano.is issue.



▄▄███████▄▄
▄██████████████▄
▄██████████████████▄
▄████▀▀▀▀███▀▀▀▀█████▄
▄█████████████▄█▀████▄
███████████▄███████████
██████████▄█▀███████████
██████████▀████████████
▀█████▄█▀█████████████▀
▀████▄▄▄▄███▄▄▄▄████▀
▀██████████████████▀
▀███████████████▀
▀▀███████▀▀
.
 MΞTAWIN  THE FIRST WEB3 CASINO   
.
.. PLAY NOW ..
tlhIlwI
Sr. Member
****
Offline Offline

Activity: 305
Merit: 250



View Profile
February 23, 2016, 04:04:16 PM
 #11149

Regarding payouts, here's my quick thoughts on it:

Pros of daily payouts:
1 - Less time spent entering payouts into my mining spreadsheet
2 - Smaller transactions out of my wallet when I spend the coins (since my mining is rapidly becoming a smaller and smaller % of the pool I'm looking at hundreds of smaller inputs versus a few dozen larger ones)
3 - Less transaction fee overhead for the pool

Pros of the current per block payout:
1 - Pool holds coins longer and thus more risk
2 - Easy to match blocks to payments in my records (though that really isn't entirely necessary-- I just like knowing I have that data)

Overall, I lean toward the daily payout preference.

Subscribe to my Bitcoin Mining YouTube channel: https://www.youtube.com/channel/UC7eam9msr3I2qxzsCzRTuVQ
bctmke
Sr. Member
****
Offline Offline

Activity: 294
Merit: 250


View Profile
February 23, 2016, 04:24:34 PM
 #11150

I don't mind either way from a payout perspective.

I'm good with daily or every block like you currently are.

I think doing what is right for yourself is the way to go.  This way it'll allow you to focus on other areas of the pool that might need more work or enhancement.

If that means a single payment daily - go for it.  If that means keeping the status quo - then thats great too.

NXS is on the move!   Come subscribe to our subreddit  https://www.reddit.com/r/nexusearth/
Come mine NXS at http://nxsminingpool.com
ATCkit
Hero Member
*****
Offline Offline

Activity: 786
Merit: 1000


View Profile
February 23, 2016, 04:26:29 PM
 #11151

im fine with however you end up doing the payouts. You know whats best for you and the pool and trust your judgement/decision. You will never make 100% of the people happy with how its done so do what you feel is best.

Ditto
firetreeactual
Legendary
*
Offline Offline

Activity: 952
Merit: 1003



View Profile
February 23, 2016, 05:09:06 PM
 #11152

I don't mind either way from a payout perspective.

I'm good with daily or every block like you currently are.

I think doing what is right for yourself is the way to go.  This way it'll allow you to focus on other areas of the pool that might need more work or enhancement.

If that means a single payment daily - go for it.  If that means keeping the status quo - then thats great too.

I feel pretty much the same. This is my "job." It could be 20 blocks to record a day and I would not mind. It's money in my retirement fund.

Do what makes sense for you on payouts, Kano. We'll manage.

What is relied upon more is your vision, experience, expertise, and coding, which few of us could likely approach in level. That is much 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)
philipma1957
Legendary
*
Online Online

Activity: 4158
Merit: 8057


'The right to privacy matters'


View Profile WWW
February 23, 2016, 05:30:24 PM
Last edit: February 23, 2016, 05:41:06 PM by philipma1957
 #11153

nice to get a block

https://blockchain.info/block-height/399738


not nice to have my transaction miss this block


https://blockchain.info/tx/df60741e004f63c13d07eb422f89b3fbc1a2b270cccd35c05d0daeb35af5f20f

now 10 blocks have skipped the .0013 fee transaction due to it having 52 small parts of coin and 3 big parts.
thus 55 parts of coin which takes up space so it gets skipped.


even though the fee is .0013 I got skipped here  for this block.

These funds were sent to me and there are 3 big parts in the send  about  7.5  and 52 small parts around 0.05

This is tough as small payments take up space and the large fee of .0013 is not big enough.


This is fund sent to me so I can not control the fee. and the sender did a large fee .0013

This post rambles but there is a point.  If kano pool send out 2 to 4 payments a day to my address  in 20 days it is 40 to 80 payments   vs 20 payments.

When I go to pay from that wallet  all 80 payments will need a big fee to clear.

 So I rather 1 daily payment.

▄▄███████▄▄
▄██████████████▄
▄██████████████████▄
▄████▀▀▀▀███▀▀▀▀█████▄
▄█████████████▄█▀████▄
███████████▄███████████
██████████▄█▀███████████
██████████▀████████████
▀█████▄█▀█████████████▀
▀████▄▄▄▄███▄▄▄▄████▀
▀██████████████████▀
▀███████████████▀
▀▀███████▀▀
.
 MΞTAWIN  THE FIRST WEB3 CASINO   
.
.. PLAY NOW ..
clgrissom3
Legendary
*
Offline Offline

Activity: 1722
Merit: 1032


Carl, aka Sonny :)


View Profile
February 23, 2016, 05:36:16 PM
 #11154

Nice job bitcoinsvoorniks with 7THs hitting your 2nd kano.is block!  We've had quite a few normal sized miners to hit blocks lately!
mtmining2
Newbie
*
Offline Offline

Activity: 35
Merit: 0


View Profile
February 23, 2016, 05:44:13 PM
 #11155

I too believe that once a day would be better, not much point in saturating an already saturated network with additional transactions... unless it causes some undue security risk with the wallets of course
PPOC
Hero Member
*****
Offline Offline

Activity: 575
Merit: 500



View Profile
February 23, 2016, 05:50:31 PM
 #11156

nice to get a block

https://blockchain.info/block-height/399738


not nice to have my transaction miss this block


https://blockchain.info/tx/df60741e004f63c13d07eb422f89b3fbc1a2b270cccd35c05d0daeb35af5f20f

now 10 blocks have skipped the .0013 fee transaction due to it having 52 small parts of coin and 3 big parts.
thus 55 parts of coin which takes up space so it gets skipped.


even though the fee is .0013 I got skipped here  for this block.

These funds were sent to me and there are 3 big parts in the send  about  7.5  and 52 small parts around 0.05

This is tough as small payments take up space and the large fee of .0013 is not big enough.


This is fund sent to me so I can not control the fee. and the sender did a large fee .0013

This post rambles but there is a point.  If kano pool send out 2 to 4 payments a day to my address  in 20 days it is 40 to 80 payments   vs 20 payments.

When I go to pay from that wallet  all 80 payments will need a big fee to clear.

 So I rather 1 daily payment.


I agree with Philip, I am voting for a once per day payment.

BTC: 1Bo6YsPeHCrVRygHLJg9BwHeaLSQpppcJi
"Lost coins only make everyone else’s coins worth slightly more. Think of it as a donation to everyone."
Herv12
Full Member
***
Offline Offline

Activity: 226
Merit: 103


View Profile
February 23, 2016, 05:56:17 PM
 #11157

Regarding payouts, here's my quick thoughts on it:

Pros of daily payouts:
1 - Less time spent entering payouts into my mining spreadsheet
2 - Smaller transactions out of my wallet when I spend the coins (since my mining is rapidly becoming a smaller and smaller % of the pool I'm looking at hundreds of smaller inputs versus a few dozen larger ones)
3 - Less transaction fee overhead for the pool

Pros of the current per block payout:
1 - Pool holds coins longer and thus more risk
2 - Easy to match blocks to payments in my records (though that really isn't entirely necessary-- I just like knowing I have that data)

Overall, I lean toward the daily payout preference.

Heck, I am for the weekly payment, I feel very lonely! Grin

You have also the person who does not receive payment of the night as the smartphone app of its ledger rings at each BTC entrance and it wakes .... Grin  Grin  Grin
And of course take into account time zones!

To make everyone happy, kano will have at least a month of work to write the soft!

I do not know if you like to receive whose amount Payment small but me it pollutes my ledger, and it makes them impossible audits.
The proposal made kano is good, but if it is possible to adjust the automatic payment threshold and have a manual trigger, that would be great

However, I understand that kano does not want to keep too much BTC on its pool, it attracts hackers.
cryptichermit
Member
**
Offline Offline

Activity: 106
Merit: 10


View Profile
February 23, 2016, 06:08:48 PM
 #11158


https://blockchain.info/tx/df60741e004f63c13d07eb422f89b3fbc1a2b270cccd35c05d0daeb35af5f20f

now 10 blocks have skipped the .0013 fee transaction due to it having 52 small parts of coin and 3 big parts.
thus 55 parts of coin which takes up space so it gets skipped.


even though the fee is .0013 I got skipped here  for this block.

These funds were sent to me and there are 3 big parts in the send  about  7.5  and 52 small parts around 0.05

This is tough as small payments take up space and the large fee of .0013 is not big enough.


55 pennies is large fee to send $4,400 ?
Last week I spent $46.00 to wire $1,700 at the bank.
Sticking to .0001 per kb should still assure relatively fast acceptance.

VRobb
Hero Member
*****
Offline Offline

Activity: 1610
Merit: 538

I'm in BTC XTC


View Profile
February 23, 2016, 06:46:36 PM
 #11159

Cheers to bitcoinsvoorniks for cracking a block @ 7THs, makes me think my S7 might punch one out for the team someday!

Second, as a loyal member-fanatic of the best pool out there, whatever kano-san decides to do regarding payments is 100% fine by me.  I'm so ahead here it's not even funny!  Actually it is, HA!  Cheesy

Keep calm and mine on!

I don't believe in superstition because it's bad luck: 13thF1oor6CAwyzyxXPNnRvu3nhhYeqZdc
These aren't the Droids you're looking for: S5 & S7 (Sold), R4B2, R4B4 (RIP), 2x S9 obsolete, 2xS15-28, S17-56, S17-70
Pushing a whopping 1/5 PH!  Oh The SPEED!!!
tlhIlwI
Sr. Member
****
Offline Offline

Activity: 305
Merit: 250



View Profile
February 23, 2016, 06:58:54 PM
 #11160


This post rambles but there is a point.  If kano pool send out 2 to 4 payments a day to my address  in 20 days it is 40 to 80 payments   vs 20 payments.

When I go to pay from that wallet  all 80 payments will need a big fee to clear.

 So I rather 1 daily payment.

This is an example of what I was talking about with pro #2 for daily in my post above.  When I was mining 0.1 BTC or more per block this wasn't a big issue, but now that I'm down to 0.01 and sometimes less per block it does add up.

Subscribe to my Bitcoin Mining YouTube channel: https://www.youtube.com/channel/UC7eam9msr3I2qxzsCzRTuVQ
Pages: « 1 ... 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 [558] 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 ... 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!