KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 1137.

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: gt_addict on December 12, 2016, 01:38:34 AM

Quote from: kano on December 11, 2016, 06:16:34 PM

Quote from: gt_addict on December 11, 2016, 04:00:09 PM

...
Sorry didn't see your last post. Ok so I'm kind of confused. The txid's show the usual pool payouts including all address and shows in my wallet with no confirms but you guys aren't seeing anything? How is that possible?

I send out the payout transactions to the pool bitcoinds soon after they mature (usually less than 2 minutes)
Normally no one else on the planet is interested in them coz they are zero fee - so they are just in the pool's mempool.

Out next block (usually) confirms them.

In this case I suspect that many outside china saw the transactions since our block got out first.
Thus many had the payout transactions in their bitcoind to handle our block.
Of course, since the block was (later) orphaned, the payout transactions switched back to being unconfirmed.

Blockchain.info has difficulty dealing with orphans and also flags the pools that mine orphans as double spending (yeah blockchain.info is stupid)

Thanks for the explanation Kano. So will they actually confirm at all or be stuck in limbo?

When we find a block ... Tongue

gt_addict

hero member

Activity: 2534

Merit: 623

Quote from: kano on December 11, 2016, 06:16:34 PM

Quote from: gt_addict on December 11, 2016, 04:00:09 PM

...
Sorry didn't see your last post. Ok so I'm kind of confused. The txid's show the usual pool payouts including all address and shows in my wallet with no confirms but you guys aren't seeing anything? How is that possible?

I send out the payout transactions to the pool bitcoinds soon after they mature (usually less than 2 minutes)
Normally no one else on the planet is interested in them coz they are zero fee - so they are just in the pool's mempool.

Out next block (usually) confirms them.

In this case I suspect that many outside china saw the transactions since our block got out first.
Thus many had the payout transactions in their bitcoind to handle our block.
Of course, since the block was (later) orphaned, the payout transactions switched back to being unconfirmed.

Blockchain.info has difficulty dealing with orphans and also flags the pools that mine orphans as double spending (yeah blockchain.info is stupid)

Thanks for the explanation Kano. So will they actually confirm at all or be stuck in limbo?

firetreeactual

legendary

Activity: 952

Merit: 1003

Many mahalos (thanks) for the tweaks, Kano & CK. I am back to full node.

I do love it when a plan comes together. Kiss

EDIT: ...and when I learn something new...

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: gt_addict on December 11, 2016, 04:00:09 PM

...
Sorry didn't see your last post. Ok so I'm kind of confused. The txid's show the usual pool payouts including all address and shows in my wallet with no confirms but you guys aren't seeing anything? How is that possible?

I send out the payout transactions to the pool bitcoinds soon after they mature (usually less than 2 minutes)
Normally no one else on the planet is interested in them coz they are zero fee - so they are just in the pool's mempool.

Out next block (usually) confirms them.

In this case I suspect that many outside china saw the transactions since our block got out first.
Thus many had the payout transactions in their bitcoind to handle our block.
Of course, since the block was (later) orphaned, the payout transactions switched back to being unconfirmed.

Blockchain.info has difficulty dealing with orphans and also flags the pools that mine orphans as double spending (yeah blockchain.info is stupid)

beltsniffer

sr. member

Activity: 277

Merit: 250

Quote from: gt_addict on December 11, 2016, 04:00:09 PM

Quote from: wmabern on December 11, 2016, 02:54:06 PM

Quote from: gt_addict on December 11, 2016, 02:51:52 PM

Quote from: firetreeactual on December 11, 2016, 01:54:23 PM

Quote from: gt_addict on December 11, 2016, 12:05:36 PM

Well two payments have appeared in my wallet from the pool even though it's an orphan. Let's hope they confirm soon.

I suspect those were triggered by 442732.

Yea but unfortunately 3 hours later they haven't confirmed. Can someone with a wallet other than blockchain confirm if they have received them please?

As I said before I did not receive any payouts to my Core wallet. The last block paid was 442732.

Sorry didn't see your last post. Ok so I'm kind of confused. The txid's show the usual pool payouts including all address and shows in my wallet with no confirms but you guys aren't seeing anything? How is that possible?

That's blockchain for ya. They are unconfirmed in my blockchain wallet too. I'm sure they will drop from there eventually, since they were part of an orphaned block. Blockchain shows it as orphaned on their orphan page, with the block reward going to BW (Thanks a lot Antpoo for building on the wrong one).

wmabern

hero member

Activity: 658

Merit: 500

Visualize whirledps

I don't have an answer for you. I have never used the Blockchain wallet.

gt_addict

hero member

Activity: 2534

Merit: 623

Quote from: wmabern on December 11, 2016, 02:54:06 PM

Quote from: gt_addict on December 11, 2016, 02:51:52 PM

Quote from: firetreeactual on December 11, 2016, 01:54:23 PM

Quote from: gt_addict on December 11, 2016, 12:05:36 PM

Well two payments have appeared in my wallet from the pool even though it's an orphan. Let's hope they confirm soon.

I suspect those were triggered by 442732.

Yea but unfortunately 3 hours later they haven't confirmed. Can someone with a wallet other than blockchain confirm if they have received them please?

As I said before I did not receive any payouts to my Core wallet. The last block paid was 442732.

Sorry didn't see your last post. Ok so I'm kind of confused. The txid's show the usual pool payouts including all address and shows in my wallet with no confirms but you guys aren't seeing anything? How is that possible?

Biodom

legendary

Activity: 4004

Merit: 4656

with current low luck getting an orphan due to tech problems is unfavorable, but i have confidence that it is one and done situation.
All i care about is looong term and so far I got 8-10% better here over about 1 year period than on a competing pool.
The only thing that i worry a bit is that as "hot-shot" miners leave, our share of the network decreases and this would result in even more "lumpiness".
That said, i am looking forward to kano having back-to back two months of 100+%.
We haven't had this since June/July.

firetreeactual

legendary

Activity: 952

Merit: 1003

I fat-fingered it...s/b 442364 that triggered 696 & 732...and Who's on first...

wmabern

hero member

Activity: 658

Merit: 500

Visualize whirledps

Quote from: gt_addict on December 11, 2016, 02:51:52 PM

Quote from: firetreeactual on December 11, 2016, 01:54:23 PM

Quote from: gt_addict on December 11, 2016, 12:05:36 PM

Well two payments have appeared in my wallet from the pool even though it's an orphan. Let's hope they confirm soon.

I suspect those were triggered by 442732.

Yea but unfortunately 3 hours later they haven't confirmed. Can someone with a wallet other than blockchain confirm if they have received them please?

As I said before I did not receive any payouts to my Core wallet. The last block paid was 442732.

gt_addict

hero member

Activity: 2534

Merit: 623

Quote from: firetreeactual on December 11, 2016, 01:54:23 PM

Quote from: gt_addict on December 11, 2016, 12:05:36 PM

Well two payments have appeared in my wallet from the pool even though it's an orphan. Let's hope they confirm soon.

I suspect those were triggered by 442732.

Yea but unfortunately 3 hours later they haven't confirmed. Can someone with a wallet other than blockchain confirm if they have received them please?

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

OK, so it seems the answer to why the orphan happened is as follows:

1) 15 minutes before the orphan, the old relay stopped working in china

2) the new fibre relay isn't working

3) there was a 99 second GFW delay sending our block (share) to our china node

Result ... orphan ... even though we found it 1.8 seconds before them.

firetreeactual

legendary

Activity: 952

Merit: 1003

Quote from: gt_addict on December 11, 2016, 12:05:36 PM

Well two payments have appeared in my wallet from the pool even though it's an orphan. Let's hope they confirm soon.

I suspect those were triggered by 442732.

firetreeactual

legendary

Activity: 952

Merit: 1003

Quote from: ZedZedNova on December 11, 2016, 11:58:43 AM

Not sure if you have the option on your cable modem (it's been ~16 years since I worked with them directly), but on my DSL modem I have the option to have it run in bridged mode. So instead of the cable/DSL modem having the "public" IP address, your router does, and the modem just passes the traffic through. You could then set up your router to port forward as usual, and the cable modem treats it as normal traffic.

Yup...it's one of their new Technicolor all-in-ones. Not a bad device, really...just don't want/need it...but yeah, I basically can turn it off to anything but through traffic, and handle the rest on my R6700, which is what I had been doing. That hasn't helped. I'll try the .conf tweaks a bit later. Thanks for the input...made sense.

wmabern

hero member

Activity: 658

Merit: 500

Visualize whirledps

Quote from: kano on December 11, 2016, 01:08:48 PM

Who is this "Matt" and why would he shut it down?
Is it back up now?
Thanks.

He's the bitcoin dev who runs the relay networks.

[/quote]

Thank you.

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: wmabern on December 11, 2016, 01:03:00 PM

Quote from: kano on December 11, 2016, 01:00:43 PM

Yeah the only thing I can find to say why it was an orphan is that it would appear that data going in and out of the GFW was really slowed down.

The CN node for sending out blocks didn't get it until 99 seconds after we found the block.

So basically it would seem that the network was broken for a short while there and no one inside china saw blocks quickly from outside china (and visa versa)

All our other nodes got the share less than 100ms after it arrived at the pool and submitted it to their bitcoinds

The old relays show everything OK, but it looks like Matt turned off the bejing relay about 15 minutes before our block.
The new fibre relay uses bitcoind (no special relay program) so the logs are basically useless to work out for sure what happened.

Who is this "Matt" and why would he shut it down?
Is it back up now?
Thanks.

He's the bitcoin dev who runs the relay networks.

Anyway ...
our block was about 1.8 seconds before the other block - 16:43:57.141 UTC after processing and being accepted at the pool bitcoind
The CN node saw the other block at 16:43:58.910 - so reasonably long after we got ours.
Seems the fibre relay didn't help at all, but as I said above, I can't tell what the new fibre relay network did Sad

wmabern

hero member

Activity: 658

Merit: 500

Visualize whirledps

Quote from: kano on December 11, 2016, 01:00:43 PM

Yeah the only thing I can find to say why it was an orphan is that it would appear that data going in and out of the GFW was really slowed down.

The CN node for sending out blocks didn't get it until 99 seconds after we found the block.

So basically it would seem that the network was broken for a short while there and no one inside china saw blocks quickly from outside china (and visa versa)

All our other nodes got the share less than 100ms after it arrived at the pool and submitted it to their bitcoinds

The old relays show everything OK, but it looks like Matt turned off the bejing relay about 15 minutes before our block.
The new fibre relay uses bitcoind (no special relay program) so the logs are basically useless to work out for sure what happened.

Who is this "Matt" and why would he shut it down?
Is it back up now?
Thanks.

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Yeah the only thing I can find to say why it was an orphan is that it would appear that data going in and out of the GFW was really slowed down.

The CN node for sending out blocks didn't get it until 99 seconds after we found the block.

So basically it would seem that the network was broken for a short while there and no one inside china saw blocks quickly from outside china (and visa versa)

All our other nodes got the share less than 100ms after it arrived at the pool and submitted it to their bitcoinds

The old relays show everything OK, but it looks like Matt turned off the bejing relay about 15 minutes before our block.
The new fibre relay uses bitcoind (no special relay program) so the logs are basically useless to work out for sure what happened.

clgrissom3

legendary

Activity: 1736

Merit: 1032

Carl, aka Sonny :)

Quote from: wmabern on December 11, 2016, 11:51:06 AM

Quote from: gt_addict on December 11, 2016, 11:49:15 AM

Quote from: wmabern on December 11, 2016, 11:46:55 AM

Block trail has that block going to BW Pool. Is that an error or have we missed again?

Just got a notification from ckpool app "Block 442979 solved by wetsuit.594-1".

Could well be an error I suppose Huh

Yes, I saw that. But if you click on the block link, it takes you to Blocktrail. There they are showing BW Pool solved it. I guess we will find out shortly. Huh

Damn!! Fing orphan! Angry

Chin up people! We usually get on a block roll after an orphan like this hits us! Cheesy

wmabern

hero member

Activity: 658

Merit: 500

Visualize whirledps

Quote from: gt_addict on December 11, 2016, 12:05:36 PM

Well two payments have appeared in my wallet from the pool even though it's an orphan. Let's hope they confirm soon.

Nothing in my Core wallet.

Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 1137. (Read 5352479 times)