mdude77
Legendary
Offline
Activity: 1540
Merit: 1001
|
|
December 27, 2017, 07:34:46 PM |
|
Thanks a bunch wavelengthsf. I'll give it a try for about a week or two and see how it goes. Hopefully great!! Sure - my advice is to give it 2 months. You need some time for the ramp up and the longer you mine, the less variance. I agree. I think the ramp up period is close to 2 weeks right now. M
|
I mine at Kano's Pool because it pays the best and is completely transparent! Come join me!
|
|
|
dzimmerm56
Member
Offline
Activity: 118
Merit: 14
|
|
December 27, 2017, 07:53:18 PM |
|
Interesting. I am seeing the reward from the 24th in my wallet but it is still in the memory pool. I usually do not see the reward until the next block hits or Kano submits a small transaction fee to get payments out. My understanding was as long as we were running fee free till 2018 no paid transaction fees would be forthcoming. Is this just a fluke in that the reward is showing but not confirmed? I know that running a full node usually gets my payments transmitted right away, even if no confirmations. I was not sure if running a full node effects receiving in a similar way. Any bitcoin core wallet gurus out there that have some insight?
|
1 S9, 2 A741s, 1 A821, 3 A841s, and full bitcoin node About 80THash/sec
|
|
|
wavelengthsf
|
|
December 27, 2017, 08:02:37 PM |
|
Interesting. I am seeing the reward from the 24th in my wallet but it is still in the memory pool. I usually do not see the reward until the next block hits or Kano submits a small transaction fee to get payments out. My understanding was as long as we were running fee free till 2018 no paid transaction fees would be forthcoming. Is this just a fluke in that the reward is showing but not confirmed? I know that running a full node usually gets my payments transmitted right away, even if no confirmations. I was not sure if running a full node effects receiving in a similar way. Any bitcoin core wallet gurus out there that have some insight?
A node relayed the transaction, and it got to your wallet, so it'll show there, even if its not confirmed. You wont be able to spend it until it is confirmed, of course.
|
|
|
|
Waztim
Member
Offline
Activity: 210
Merit: 15
|
|
December 27, 2017, 08:26:17 PM |
|
In your experience, does the reward make up for the long wait before a block is found? I currently average 0.002918071 per day with Slushpool with only one S9.
Yes, absolutely. I switched from Slush to Kano and I definitely see the difference. Slush is a fine pool, nothing wrong with it, but the fee is higher than Kano (2% vs .9% when he has it). The pool is much smaller, so the variance is higher, but the payouts are great when they come. Thanks a bunch wavelengthsf. I'll give it a try for about a week or two and see how it goes. Hopefully great!! A week or two is not a long enough time period to do a proper assessment of the Pool. Give it 6 months, then look at the data. You have to have a bigger sample size to do a proper analysis. Mine On with Kano-San, it is worth it!! Come On Block!!
|
|
|
|
diasmd
Newbie
Offline
Activity: 2
Merit: 0
|
|
December 27, 2017, 11:04:01 PM |
|
So, after the ramp up, how often are the payouts? Tks
|
|
|
|
wavelengthsf
|
|
December 27, 2017, 11:12:09 PM |
|
So, after the ramp up, how often are the payouts? Tks
You get payouts when: 1) We find a block 2) 101 confirmations pass (the block matures) 3) The payout block is mined (usually when we find the next one.) Even during the ramp up, you get a payout, it just won't be for your full hash rate until you're fully ramped.
|
|
|
|
Waztim
Member
Offline
Activity: 210
Merit: 15
|
|
December 27, 2017, 11:28:17 PM |
|
Kano-San - How does an Orphaned Block occur? Thanks in advance.
|
|
|
|
rifleman74
Member
Offline
Activity: 658
Merit: 21
4 s9's 2 821's
|
|
December 27, 2017, 11:45:47 PM |
|
Kano-San - How does an Orphaned Block occur? Thanks in advance.
Very very very very very very very very rare.
|
|
|
|
rifleman74
Member
Offline
Activity: 658
Merit: 21
4 s9's 2 821's
|
|
December 27, 2017, 11:59:06 PM |
|
Now's the time on Sprockets where we dance!
BLOCK DANCE COMMENCES!
|
|
|
|
AerialGopher
Jr. Member
Offline
Activity: 196
Merit: 4
|
|
December 28, 2017, 12:12:13 AM |
|
OFFICIAL ANNOUNCEMENT:
Gopher is up to 70 TH/s 4x 13.5TH and 1 x 14 TH And they do just a wee bit more, making it 70 TH ish :-) Jan 21-30 Delivery came EARLY!!! YEAH!
|
|
|
|
mdude77
Legendary
Offline
Activity: 1540
Merit: 1001
|
|
December 28, 2017, 12:29:04 AM |
|
OFFICIAL ANNOUNCEMENT:
Gopher is up to 70 TH/s 4x 13.5TH and 1 x 14 TH And they do just a wee bit more, making it 70 TH ish :-) Jan 21-30 Delivery came EARLY!!! YEAH!
Grats! We could use it. M
|
I mine at Kano's Pool because it pays the best and is completely transparent! Come join me!
|
|
|
MattMell
Newbie
Offline
Activity: 42
Merit: 0
|
|
December 28, 2017, 12:40:02 AM |
|
Congrats Gopher! Lets see the blocks roll in OFFICIAL ANNOUNCEMENT:
Gopher is up to 70 TH/s 4x 13.5TH and 1 x 14 TH And they do just a wee bit more, making it 70 TH ish :-) Jan 21-30 Delivery came EARLY!!! YEAH!
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4620
Merit: 1851
Linux since 1997 RedHat 4
|
|
December 28, 2017, 12:40:13 AM |
|
Kano-San - How does an Orphaned Block occur? Thanks in advance.
An orphan occurs when the pool is slow to send out the blocks it finds or another pool found a block at the same time. The Fibre Relay is the biggest help in reducing orphans. Though for some unknown reason, no pools pay for it except me, according to the person who runs it (and I pay about half what he expects since we are clearly a lot smaller than the large pools that use it) However, there's 2 classifications for 'orphans' due to the 2 reasons why they can occur: 1) Normal Orphan - when 2 pools find a block at the same time and neither pool sees the other pool's block before their own. The internet isn't perfect so data can take time to get around it. 2) Stale - when we get a block late, 'after' another pool gets a block. This is due to a miner sending a block late to the pool, after the pool has switched to new work on a new block height. When this happens, most pools don't tell you about them, or to be correct, you will probably find that no pool tells you about them other than pools using my database code. They represent a block that should not exist - but since the pool code will (now) switch to it, we try to confirm it ourselves, so if we get lucky and get a double block, then we will keep the stale and switch the network over to it instead. Stales don't count as orphans since they shouldn't exist - but there's still the (small) chance we might confirm it anyway
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4620
Merit: 1851
Linux since 1997 RedHat 4
|
|
December 28, 2017, 12:44:14 AM |
|
OFFICIAL ANNOUNCEMENT:
Gopher is up to 70 TH/s 4x 13.5TH and 1 x 14 TH And they do just a wee bit more, making it 70 TH ish :-) Jan 21-30 Delivery came EARLY!!! YEAH!
Heh, sounds like Bitmain is worried about Canaan and sending out the hardware they have rather than keeping it Glad to see you got some early!
|
|
|
|
Waztim
Member
Offline
Activity: 210
Merit: 15
|
|
December 28, 2017, 12:57:22 AM |
|
Kano-San - How does an Orphaned Block occur? Thanks in advance.
An orphan occurs when the pool is slow to send out the blocks it finds or another pool found a block at the same time. The Fibre Relay is the biggest help in reducing orphans. Though for some unknown reason, no pools pay for it except me, according to the person who runs it (and I pay about half what he expects since we are clearly a lot smaller than the large pools that use it) However, there's 2 classifications for 'orphans' due to the 2 reasons why they can occur: 1) Normal Orphan - when 2 pools find a block at the same time and neither pool sees the other pool's block before their own. The internet isn't perfect so data can take time to get around it. 2) Stale - when we get a block late, 'after' another pool gets a block. This is due to a miner sending a block late to the pool, after the pool has switched to new work on a new block height. When this happens, most pools don't tell you about them, or to be correct, you will probably find that no pool tells you about them other than pools using my database code. They represent a block that should not exist - but since the pool code will (now) switch to it, we try to confirm it ourselves, so if we get lucky and get a double block, then we will keep the stale and switch the network over to it instead. Stales don't count as orphans since they shouldn't exist - but there's still the (small) chance we might confirm it anyway Once again, KANO-SAN The Subject Matter Expert Speaks and this Grasshopper listens with both ears. Thanks.
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4620
Merit: 1851
Linux since 1997 RedHat 4
|
|
December 28, 2017, 01:16:33 AM |
|
So, after the ramp up, how often are the payouts? Tks
You get payouts when: 1) We find a block 2) 101 confirmations pass (the block matures) 3) The payout block is mined (usually when we find the next one.) Even during the ramp up, you get a payout, it just won't be for your full hash rate until you're fully ramped. ... and just to clarify a few things about the 'ramp' It isn't expected to reduce your rewards if you do hop. The 'ramp' is simply a side effect of spreading out your rewards over a longer period of time - in our case 5Nd - to reduce your reward variance - and of course stop pool hopping from taking expected rewards from long term miners - that's what the PPLNS payout does (that many pools use) You can hop in and get lucky and you can hop in and get unlucky - it's random and COMPLETELY outside anyone's control. The length of the 5Nd however makes the variance of the 'hop luck' expected to be much lower. A pool with a smaller N will have much higher variance in the 'hop luck'. Lastly, I can't just go and reduce the 5Nd with no effect. The effect of changing it a lot would be to the advantage of all miners who haven't 'ramped up' and thus to the detriment of all miners who have 'ramped up'.
|
|
|
|
mdude77
Legendary
Offline
Activity: 1540
Merit: 1001
|
|
December 28, 2017, 01:26:23 AM |
|
The effect of changing it a lot would be to the advantage of all miners who haven't 'ramped up' and thus to the detriment of all miners who have 'ramped up'.
It's actually an extremely fair process. There's no reason why someone should be able to join at the tail end of a 3 day block and get paid the same amount as all the miners that were mining that entire 3 days. M
|
I mine at Kano's Pool because it pays the best and is completely transparent! Come join me!
|
|
|
kano (OP)
Legendary
Offline
Activity: 4620
Merit: 1851
Linux since 1997 RedHat 4
|
|
December 28, 2017, 02:17:12 AM |
|
The NL node just had a short complete network outage. All connections to NL will have failed over to your 2nd pool listed in your miner. The network is back up again (less than a minute later) so all is OK again there. Mine on! -- ... and a little aside about mining fees. They're around 6-7BTC per 10 minute block at the moment - so have stayed down below that 10BTC mark for a while now.
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4620
Merit: 1851
Linux since 1997 RedHat 4
|
|
December 28, 2017, 02:57:58 AM |
|
Not sure how many people ever use BitPay to pay for anything, but they're landed themselves on my ban list ... well I guess you could say that they put themselves there, I can't use BitPay at the moment and probably wont want to ever again It seems they no longer allow Bitcoin payments to an address, they require you to use a "Bitcoin Payment Protocol" (that's supposedly in core 0.15 but not in 0.14) that also decides your transaction fees for you ... hmm. Every time I make payments I choose my fees, and every time I've used BitPay, it has said my fees were too low, even when my payments were picked up in the very next block on the network ...
|
|
|
|
rifleman74
Member
Offline
Activity: 658
Merit: 21
4 s9's 2 821's
|
|
December 28, 2017, 03:19:36 AM |
|
Not sure how many people ever use BitPay to pay for anything, but they're landed themselves on my ban list ... well I guess you could say that they put themselves there, I can't use BitPay at the moment and probably wont want to ever again It seems they no longer allow Bitcoin payments to an address, they require you to use a "Bitcoin Payment Protocol" (that's supposedly in core 0.15 but not in 0.14) that also decides your transaction fees for you ... hmm. Every time I make payments I choose my fees, and every time I've used BitPay, it has said my fees were too low, even when my payments were picked up in the very next block on the network ... Don't cross Kano-san!
|
|
|
|
|