I do not see this as selfishness. I tend to disagree on this. Nope, see below. From anonymously provided Stratum work logs from Foundry (dig a bit at source) around blocks of reorg area, it's pretty much clear that Foundry was well aware of mined blocks by Antpool and ViaBTC. Foundry even mined for few seconds on top of each later staled Antpool and ViaBTC blocks, but quickly decided to persue on their own blocks. From carefully reading the discussion at above provided source, it's not water-tight selfish-mining, but it very much looks like a very intentional and deliberate choice. I mean, I don't blame them, they are the largest mining pool and certainly have no reason to be samatarians. But it shatters kind of my view of honest mining by established Kqbd24h mining game theory. Possible but don't forget about this: Foundry probably does not do any checking on their own blocks or anything internal to their network. When you are talking multiple seconds across firewalls and the internet they might not have fully validated the other block. For those of us running home firewalls and minimal filtering you never really see the slowdown. For a place like Foundry a real delay can exist. Even more so with multiple geographically dispersed nodes. Some of them may have actually been mining on the other blocks when they came back with their own and then started again. I can also see it happening because nobody on their end ever thought it could happen. And when it did, "well, that was odd, but it's never going to happen again" Not defending them, but I see sooooo much network slowdown due to tin foil hat paranoia settings on edge and internal security devices having something like this happen does not surprise me. -Dave
I do not see this as selfishness. I tend to disagree on this. Nope, see below. From anonymously provided Stratum work logs from Foundry (dig a bit at source) around blocks of reorg area, it's pretty much clear that Foundry was well aware of mined blocks by Antpool and ViaBTC. Foundry even mined for few seconds on top of each later staled Antpool and ViaBTC blocks, but quickly decided to persue on their own blocks. From carefully reading the discussion at above provided source, it's not water-tight selfish-mining, but it very much looks like a very intentional and deliberate choice. I mean, I don't blame them, they are the largest mining pool and certainly have no reason to be samatarians. But it shatters kind of my view of honest mining by established Kqbd24h mining game theory. Possible but don't forget about this: Foundry probably does not do any checking on their own blocks or anything internal to their network. When you are talking multiple seconds across firewalls and the internet they might not have fully validated the other block. For those of us running home firewalls and minimal filtering you never really see the slowdown. For a place like Foundry a real delay can exist. Even more so with multiple geographically dispersed nodes. Some of them may have actually been mining on the other blocks when they came back with their own and then started again. I can also see it happening because nobody on their end ever thought it could happen. And when it did, "well, that was odd, but it's never going to happen again" Not defending them, but I see sooooo much network slowdown due to tin foil hat paranoia settings on edge and internal security devices having something like this happen does not surprise me. -Dave

I do not see this as selfishness. I tend to disagree on this. Nope, see below. From anonymously provided Stratum work logs from Foundry (dig a bit at source) around blocks of reorg area, it's pretty much clear that Foundry was well aware of mined blocks by Antpool and ViaBTC. Foundry even mined for few seconds on top of each later staled Antpool and ViaBTC blocks, but quickly decided to persue on their own blocks. From carefully reading the discussion at above provided source, it's not water-tight selfish-mining, but it very much looks like a very intentional and deliberate choice. I mean, I don't blame them, they are the largest mining pool and certainly have no reason to be samatarians. But it shatters kind of my view of honest mining by established Kqbd24h mining game theory. Possible but don't forget about this: Foundry probably does not do any checking on their own blocks or anything internal to their network. When you are talking multiple seconds across firewalls and the internet they might not have fully validated the other block. For those of us running home firewalls and minimal filtering you never really see the slowdown. For a place like Foundry a real delay can exist. Even more so with multiple geographically dispersed nodes. Some of them may have actually been mining on the other blocks when they came back with their own and then started again. I can also see it happening because nobody on their end ever thought it could happen. And when it did, "well, that was odd, but it's never going to happen again" Not defending them, but I see sooooo much network slowdown due to tin foil hat paranoia settings on edge and internal security devices having something like this happen does not surprise me. -Dave

I do not see this as selfishness. I tend to disagree on this. Nope, see below. From anonymously provided Stratum work logs from Foundry (dig a bit at source) around blocks of reorg area, it's pretty much clear that Foundry was well aware of mined blocks by Antpool and ViaBTC. Foundry even mined for few seconds on top of each later staled Antpool and ViaBTC blocks, but quickly decided to persue on their own blocks. From carefully reading the discussion at above provided source, it's not water-tight selfish-mining, but it very much looks like a very intentional and deliberate choice. I mean, I don't blame them, they are the largest mining pool and certainly have no reason to be samatarians. But it shatters kind of my view of honest mining by established Kqbd24h mining game theory. Possible but don't forget about this: Foundry probably does not do any checking on their own blocks or anything internal to their network. When you are talking multiple seconds across firewalls and the internet they might not have fully validated the other block. For those of us running home firewalls and minimal filtering you never really see the slowdown. For a place like Foundry a real delay can exist. Even more so with multiple geographically dispersed nodes. Some of them may have actually been mining on the other blocks when they came back with their own and then started again. I can also see it happening because nobody on their end ever thought it could happen. And when it did, "well, that was odd, but it's never going to happen again" Not defending them, but I see sooooo much network slowdown due to tin foil hat paranoia settings on edge and internal security devices having something like this happen does not surprise me. -Dave