hurricandave
Legendary
Offline
Activity: 966
Merit: 1003
|
|
October 15, 2015, 08:56:01 PM |
|
Everybody Hold On to Your Panties!!!!!
|
|
|
|
xZork
|
|
October 15, 2015, 09:04:42 PM |
|
Just need a confirmation... decent transaction fees too.
|
|
|
|
hurricandave
Legendary
Offline
Activity: 966
Merit: 1003
|
|
October 15, 2015, 09:20:30 PM |
|
Soo... I've been thinkin 'bout "useless" spreadsheet stuff! Who has confirmed our block solves first and how many times. How many of our block solves saw the first confirmation solve turn into an orphan race. Who / how many times, were first to include our pool payouts in a block solve. Yes, I know! "USELESS INFO" Damn you coffee!!!!
|
|
|
|
Jethroz
Newbie
Offline
Activity: 16
Merit: 0
|
|
October 15, 2015, 09:37:37 PM |
|
Nice! A block frenzy would have been a nice sight though.
|
|
|
|
gecox22
|
|
October 15, 2015, 09:46:28 PM |
|
51.90% Luck for the last 5 UGH!!!! Lets hope some green start coming our way. Glad that block is over though.
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4522
Merit: 1844
Linux since 1997 RedHat 4
|
|
October 15, 2015, 09:47:49 PM |
|
Soo... I've been thinkin 'bout "useless" spreadsheet stuff! Who has confirmed our block solves first and how many times.
That one will be purely random (based on network %) How many of our block solves saw the first confirmation solve turn into an orphan race.
We've orphaned at least a couple of others Bitfury comes to mind Who / how many times, were first to include our pool payouts in a block solve. Yes, I know! "USELESS INFO" Damn you coffee!!!!
Payout transactions ... never really noticed who confirms ours. I think we've only confirmed our own payout txn once or twice since it's usually quick to be confirmed (I'm surprised at how regularly it seems it's confirmed in less than 10 minutes) Edit: I always prioritise it so it is (first) in the block we are building so we will confirm it if our next block arrives after the payout before it was confirmed
|
|
|
|
gecox22
|
|
October 15, 2015, 10:18:45 PM |
|
Soo... I've been thinkin 'bout "useless" spreadsheet stuff! Who has confirmed our block solves first and how many times.
That one will be purely random (based on network %) How many of our block solves saw the first confirmation solve turn into an orphan race.
We've orphaned at least a couple of others Bitfury comes to mind Who / how many times, were first to include our pool payouts in a block solve. Yes, I know! "USELESS INFO" Damn you coffee!!!!
Payout transactions ... never really noticed who confirms ours. I think we've only confirmed our own payout txn once or twice since it's usually quick to be confirmed (I'm surprised at how regularly it seems it's confirmed in less than 10 minutes) Edit: I always prioritise it so it is (first) in the block we are building so we will confirm it if our next block arrives after the payout before it was confirmed I am sure this has been answered before so if it has I am sorry for asking it again but how does the percentage work? In my workers tab it shows I have a block percentage of 0.296% currently and the block we just mined was just over 0.35. Is this the percentage used in payout? Because the last block shows a reward of 0.18%. Not saying anything is wrong just trying to learn how the percentages are made.
|
|
|
|
notlist3d
Legendary
Offline
Activity: 1456
Merit: 1000
|
|
October 15, 2015, 11:04:14 PM |
|
51.90% Luck for the last 5 UGH!!!! Lets hope some green start coming our way. Glad that block is over though.
I was playing with this pool thought it would be intersting. And yea ouch it's starting to hurt on luck. I'm hoping we see some change I can understand why it varies. But we can all agree almost 50 percent is not a fun to sit at.
|
|
|
|
RealMalatesta
Legendary
Offline
Activity: 2338
Merit: 1124
|
|
October 16, 2015, 12:15:10 AM |
|
Seems luck offers a bit of compensation...
|
|
|
|
sloopy
|
|
October 16, 2015, 12:16:07 AM |
|
Yes she does, that dirty girl.
What is the tilde ` for on the blocks page?
|
Transaction fees go to the pools and the pools decide to pay them to the miners. Anything else, including off-chain solutions are stealing and not the way Bitcoin was intended to function. Make the block size set by the pool. Pool = miners and they get the choice.
|
|
|
PPOC
|
|
October 16, 2015, 12:17:54 AM |
|
Thats what i am talking about!
379092 (Main Chain) 2015-10-16 00:12:37 Kano CKPool 000000000000000006808ff46b763394d024d2930179513f57e9035dcb3fb6d3
FIRST BLOCK OF DAY!
Now just 2 more that are on the light green side and back to 100%
|
BTC: 1Bo6YsPeHCrVRygHLJg9BwHeaLSQpppcJi "Lost coins only make everyone else’s coins worth slightly more. Think of it as a donation to everyone."
|
|
|
kano (OP)
Legendary
Offline
Activity: 4522
Merit: 1844
Linux since 1997 RedHat 4
|
|
October 16, 2015, 12:32:09 AM Last edit: October 16, 2015, 12:43:10 AM by kano |
|
The '~' means that ckdb hasn't recalculated the stats for the block. It does it after the next confirm or after about 13minutes (whichever is later) Basically the reason is that when a block is found, ckdb stores all the current 'running' counters and resets them back to zero. However, there's a number of reasons why that number may be off by a small amount. The simplest one is that shares can still be accepted for the current work, after the block is found until I get the confirm from ckpool - since ckpool decides if a share is accepted, not ckdb - and this also could have affected the counters back at the start of the block. Once the 'aging' function of the workinfo containing the block has occurred, ckpool certainly wont send any more valid shares for the workinfo, so at that point, ckdb recalculates the correct stats for the block and updates it. e.g. for the last block [2015-10-16 11:27:18.027+11] summarise_blocks() block 379092, stats confirmed 5488381639/10979862/4739416/9795/12275
|
|
|
|
gecox22
|
|
October 16, 2015, 01:06:30 AM |
|
Thats what i am talking about!
379092 (Main Chain) 2015-10-16 00:12:37 Kano CKPool 000000000000000006808ff46b763394d024d2930179513f57e9035dcb3fb6d3
FIRST BLOCK OF DAY!
Now just 2 more that are on the light green side and back to 100%
What a nice block at 9% gotta love those..!!!!!! Now lets hope it doesn't follow like the last go around.
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4522
Merit: 1844
Linux since 1997 RedHat 4
|
|
October 16, 2015, 09:35:17 PM |
|
I'll be doing a ckpool restart in a few minutes (before the payout comes due) I'm switching the main bitcoind up to 0.11.1 and that switch will mean I'll have to restart ckpool (after bitcoind has finished restarting) It will only be a reconnect in cgminer for most (though as always some few will failover) Edit: done Edit2: oh I also increased the block size from 850,000 to 888,888 - for luck Payout 379070 sent dd9cd25449d620777bafbfd9681ebf8eafe45e21e93bfd6ef71852e951851917 and confirmed Payout 379092 sent 2535fe0d542191cec42b70399b1e8e9e553f6a76c9c5f1856c9e59d53c5f7bf4 and confirmed
|
|
|
|
gecox22
|
|
October 17, 2015, 10:52:07 PM |
|
BLOCK!!!! YAY! at least it wasn't red!!!!. Come one Green show us some LOVE! Luck is creeping slowly back up!
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4522
Merit: 1844
Linux since 1997 RedHat 4
|
|
October 18, 2015, 06:57:50 AM |
|
Heh Eligius are liars and thieves No idea why anyone would mine there. 2 posts deleted from their thread: What is this?
#15 (Unknown users) 183.02 Th/s 460225024 1.257%
LOL, that's people mining with an invalid address I think. = donations. scam If you have a way to track these users down, you're welcome to share it. On my pool we don't keep users connected with invalid connection details so we can steal their mining power = BTC. Invalid address miners are not allowed to mine. ... And as others have mentioned, it's not like rejecting the connections is going to benefit anybody. ...
Although you may think it wise to mine with a single account and no backup, most miners have realised for MANY years that is a foolish thing to do. If one pool/account is rejected or fails when mining, cgminer (used by the vast majority of BTC miners on the planet) switches over to the secondary or later accounts it has been provided with. If someone is dropping money on the street, it isn't the job of whoever finds it to hunt them down even if it is possible. ...
Well ... a few years ago a guy walking through a centre about 30m ahead of me dropped a small amount of paper. When I got to it I noticed it contained cash. I picked it up and it included over $100 ... Though you may consider that a bad thing to do, I chased after him and gave it to him. He hadn't even realised he'd dropped it. And wizpants final comment ... The accusations of stealing based on a well established policy are a bit absurd, and honestly I don't want to hear it. ... I'm not going to implement valid address/worker name checking in the pool software. It's not worth the time and effort when there are plenty of other things I can dedicate my time to.
Well established policy of stealing Well ... it is a fee free pool ... where no one makes the expected payout ... for years ... they gotta get paid somehow for all their costs running the pool right?
|
|
|
|
markBG
Newbie
Offline
Activity: 29
Merit: 0
|
|
October 18, 2015, 12:31:21 PM |
|
many pools accept P2SH addresses as users , but don't give shares for work, because can verify and recognize only P2PKH and give shares . Kano isn't such pool. CKpool code accept P2SH. Am I right?
|
|
|
|
gecox22
|
|
October 18, 2015, 12:33:21 PM |
|
Soo... I've been thinkin 'bout "useless" spreadsheet stuff! Who has confirmed our block solves first and how many times.
That one will be purely random (based on network %) How many of our block solves saw the first confirmation solve turn into an orphan race.
We've orphaned at least a couple of others Bitfury comes to mind Who / how many times, were first to include our pool payouts in a block solve. Yes, I know! "USELESS INFO" Damn you coffee!!!!
Payout transactions ... never really noticed who confirms ours. I think we've only confirmed our own payout txn once or twice since it's usually quick to be confirmed (I'm surprised at how regularly it seems it's confirmed in less than 10 minutes) Edit: I always prioritise it so it is (first) in the block we are building so we will confirm it if our next block arrives after the payout before it was confirmed I am sure this has been answered before so if it has I am sorry for asking it again but how does the percentage work? In my workers tab it shows I have a block percentage of 0.296% currently and the block we just mined was just over 0.35. Is this the percentage used in payout? Because the last block shows a reward of 0.18%.
Not saying anything is wrong just trying to learn how the percentages are made.Kano, I think my question was over looked, would you mind shedding some light on it for me. Thanks
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4522
Merit: 1844
Linux since 1997 RedHat 4
|
|
October 18, 2015, 12:42:09 PM |
|
... I am sure this has been answered before so if it has I am sorry for asking it again but how does the percentage work?
In my workers tab it shows I have a block percentage of 0.296% currently and the block we just mined was just over 0.35. Is this the percentage used in payout? Because the last block shows a reward of 0.18%.
Not saying anything is wrong just trying to learn how the percentages are made.
Kano, I think my question was over looked, would you mind shedding some light on it for me. Thanks It has nothing to do with the payout.
|
|
|
|
markBG
Newbie
Offline
Activity: 29
Merit: 0
|
|
October 18, 2015, 12:45:55 PM |
|
I think Block % is just a % from all shares since last found block. This is not conected with reward which is calculated by mined shares for last 5Nd where N is current mining difficulty for bitcoin
|
|
|
|
|