clgrissom3
Legendary
Offline
Activity: 1722
Merit: 1032
Carl, aka Sonny :)
|
|
July 31, 2017, 02:30:26 PM |
|
My core wallet has a incoming transaction from Kano.is at 7/31/17 @ 04:04 and it shows a light grey and says:
Status: 0/unconfirmed, not in memory pool Date: 7/31/2017 04:04 From: unknown To: 1Q14j1KRDRcpUUb2rQYUh5WMLaynPfyP7S (own address, label: KANO.IS) Credit: 0.00599468 BTC Net amount: +0.00599468 BTC Transaction ID: 5f6688c178cd5cba2c98056f9091da43e0b6b7ac3ecda023ab7f21b4b0773d4f Transaction total size: 28234 bytes Output index: 496
Never seen that, new normal?
I've seen that happen with a few zero fee transactions in the past. It just sits at 0 until we hit our next block or until someone else confirms it which did happen from time to time. This one has fees so it has a better chance of getting confirmed Of course, our BLOCK MONDAY party will take care of it if no one else does...let's get it started!
|
|
|
|
bronder
Newbie
Offline
Activity: 48
Merit: 0
|
|
July 31, 2017, 04:12:08 PM |
|
Kano,
I appreciate you keeping us informed as to the plan for B-Day, hopefully it's a non-event and it should be at least for us.
|
|
|
|
firetreeactual
Legendary
Offline
Activity: 952
Merit: 1003
|
|
July 31, 2017, 04:56:19 PM |
|
I'm all clear on payments as well. Reminds me of the brouhaha around the last two halvings...
|
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
Offline
Activity: 4242
Merit: 8506
'The right to privacy matters'
|
|
July 31, 2017, 06:36:11 PM |
|
I'm all clear on payments as well. Reminds me of the brouhaha around the last two halvings... hope so. Oh my avalon 741 comes on tues just in time for the new era.
|
|
|
|
OneInchWonder
|
|
July 31, 2017, 07:55:49 PM |
|
With the fork going happen and if a good size of the speed drops off the network to mine BCC with about 8 days till difficulty adjustment.
How do you see it playing out? Longer wait times and tell blocks are found and slow down transactions and confirmations.
|
get.uber.com/drive/?invite_code=brianp6308ue
|
|
|
kano (OP)
Legendary
Offline
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
|
|
July 31, 2017, 09:40:28 PM |
|
With the fork going happen and if a good size of the speed drops off the network to mine BCC with about 8 days till difficulty adjustment.
How do you see it playing out? Longer wait times and tell blocks are found and slow down transactions and confirmations.
Well that all simply depends on how much hash rate goes to the fork, and that's anyone's guess. It will of course mean average slower blocks until the next diff change, but once the next diff change gets here, that will mean a diff drop also. I doubt we'll see 20% of the network switch to the fork, but doing the calculations with 20%: e.g. if it was 20% then that would mean 1/0.8 or 25% longer blocks i.e. expected avg 12.5 mins per block. we are at the moment 666 blocks in this diff change i.e. 1350 to go so ~1/3 done, ~2/3 to go 2/3 would expect to be 9.375 days, but with the extra 25% that would be 11.7 days so about 2.3 extra days - so even 20% is not that big a change. The diff drop for 20% would be about 13.3% - i.e. about 2/3 of the 20% The next diff change, after this up coming one, will also be a little slower, since the first 1/3 of this diff change was at the higher hash rate, so that should be the other 1/3 of the 20% for the whole next diff change, but since it would already have dropped 13.3% ... that 1/3 would mean roughly about another 6.2% diff drop next diff change. ... all that also presuming no hash rate rise
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
|
|
July 31, 2017, 09:48:30 PM Last edit: July 31, 2017, 10:12:26 PM by kano |
|
Last payout (478295) confirmed - in time The power of 42,000 satoshis Edit: also there were a few failovers from 16:18 to 16:28 UTC from one of the US stratum nodes. You'll see a drop on the shift graph for that shift. I'm guessing there was network trouble but got no notifications (to wake me up) since in each case they were immediate failovers and failbacks. My monitoring needs to lose the connection (which it didn't, so it wasn't a full failover of everyone) or it needs to fail another network test, which didn't happen either. So must have been very short each time.
|
|
|
|
philipma1957
Legendary
Offline
Activity: 4242
Merit: 8506
'The right to privacy matters'
|
|
August 01, 2017, 12:20:29 AM |
|
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
|
|
August 01, 2017, 12:27:57 AM Last edit: August 01, 2017, 01:19:20 AM by kano |
|
Well you'd have to look for rejected blocks in your bitcoin debug.log Give it a while Also the network hash rate will probably drop a bit - but that won't be obvious for a while either. The pools list at btc.com may or may not show the split correctly ... who knows how they come up with the numbers there I sent them the details for KanoPool a while ago and they've still done nothing to fix that ... Edit: blockchair.com was supposed to have a browser at fork time ... but that clearly didn't happen
|
|
|
|
Tamerz
|
|
August 01, 2017, 06:03:19 AM |
|
Well you'd have to look for rejected blocks in your bitcoin debug.log
Would that be these? warning='20 of last 100 blocks have unexpected version'
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
|
|
August 01, 2017, 06:39:14 AM |
|
Well you'd have to look for rejected blocks in your bitcoin debug.log
Would that be these? warning='20 of last 100 blocks have unexpected version' No, they're just the different block version numbers - for segwit2x 0x20000012 or other guff with other numbers The expected block version at the moment is 0x20000002 I've seen messages saying "invalid block=" and "is marked invalid" a bit over a week ago for a block with the hash "0000000000000000013ee4a86822d37a061732e04ee5f41fb77168f193363d1b" at 477115 So I'm guessing the message might be similar - but I'm not sure and have never checked the code to see what other such messages there are. One simple way on linux to see all block messages other than the standard expected ones is: grep 000000000 debug.log | grep -v "new best="
|
|
|
|
huynhdat1989
Member
Offline
Activity: 101
Merit: 10
|
|
August 01, 2017, 07:14:31 AM |
|
Dear kano, Do you support mining Bitcoin Cash? We use the same asic miner to mine?
Regards,
|
|
|
|
mousehouse
|
|
August 01, 2017, 08:06:54 AM |
|
Wow, nearly 40 hours without finding any blocks Question, can't seem to find a list of pool servers to connect to. Help shows "stratum.kano.is" but that seems to be in the US. Is it recommended to use only that one or is a closer one a smarter move?
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
|
|
August 01, 2017, 08:09:01 AM |
|
Dear kano, Do you support mining Bitcoin Cash? We use the same asic miner to mine?
Regards,
It's an alt-coin - which I tend to completely stay clear of. Unless it becomes what I consider 'valid', I'd not setup a pool, in my usual disinterest in being involved in scams, which it clearly currently is Setting up a pool is simple enough, but it also depends on how reliable the bitcoind is, since if it's crashing or causing problems, that's a royal PITA coz it can mean wasted mining for everyone pointed at the pool when such things happen. That's not something new, it happens all over the place, but you find that others pools don't tell you about it, or tell you what's going on ... ... ... ... ... However, Core bitcoind is currently pretty reliable as a fast work generator, with minor changes and since I run a few on the main node, it's been a long time since there's been anything that could matter.
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
|
|
August 01, 2017, 08:11:02 AM |
|
Wow, nearly 40 hours without finding any blocks Question, can't seem to find a list of pool servers to connect to. Help shows "stratum.kano.is" but that seems to be in the US. Is it recommended to use only that one or is a closer one a smarter move? Try pinging any in the thread title to find the closest one to you. i.e. de, sg, jp, nl, and nya.kano.is
|
|
|
|
mousehouse
|
|
August 01, 2017, 08:14:35 AM |
|
Wow, nearly 40 hours without finding any blocks Question, can't seem to find a list of pool servers to connect to. Help shows "stratum.kano.is" but that seems to be in the US. Is it recommended to use only that one or is a closer one a smarter move? Try pinging any in the thread title to find the closest one to you. i.e. de, sg, jp, nl, and nya.kano.is Thx, works great! Two new miners on your pool
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
|
|
August 01, 2017, 08:17:35 AM |
|
Wow, nearly 40 hours without finding any blocks Question, can't seem to find a list of pool servers to connect to. Help shows "stratum.kano.is" but that seems to be in the US. Is it recommended to use only that one or is a closer one a smarter move? Try pinging any in the thread title to find the closest one to you. i.e. de, sg, jp, nl, and nya.kano.is Thx, works great! Two new miners on your pool Your welcome and cool, more miners
|
|
|
|
Biffa
Legendary
Offline
Activity: 3220
Merit: 1220
|
|
August 01, 2017, 10:52:59 AM |
|
The BIP148 split was a no-sho it seems, everyone had already moved to BIP91 The Bitcash hard fork happens around 12:20 UTC today. Thats when there should be some ripples.
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
|
|
August 01, 2017, 12:15:06 PM |
|
For those interested This might actually be working - it now shows no BCH blocks ... correctly ... 5 mins before the 'fork' https://blockchair.com/bitcoin-cash/blocksThat might well show reasonably quickly (hours) how much hash rate has gone from Bitcoin. or https://www.btcforkmonitor.info/
|
|
|
|
Apprentice
|
|
August 01, 2017, 12:28:13 PM |
|
I'm all clear on payments as well. Reminds me of the brouhaha around the last two halvings... hope so. Oh my avalon 741 comes on tues just in time for the new era. Waiting too for 2 S9s to ship in August!
|
|
|
|
|