As an update for this thread there have been two more stale blocks today at blocks 789135 and 789147: https://forkmonitor.info/nodes/btc
The first involved an unknown pool some 7 minutes behind viaBTC, the second yet again involved Foundary USA with a 2 minute delay behind F2Pool. Maybe someone can elaborate on the unknown here.
mempool.space is orgerwise redirecting stale block hash links to the verified blocks, so not sure what other blockchain explorers have more info.
Why so many stale blocks right now? Still only 2 deep, but has made me curious if this isn't just Foundary USA anymore.
Topic: foundry is playing a power game screwing with bitcoin (Read 218 times)
as there isn't any financial benefit for a mining pool to do this right?
That said, he also mentioned that if it happened again they are evil (which has since happened as you pointed out). So now I don't know what to think
That said, he also mentioned that if it happened again they are evil (which has since happened as you pointed out). So now I don't know what to think
There is tremendous financial benefit, it's called front-running and then trading BRC20's
I'm curious to hear what OP @kano makes of all this, and the recent BRC20 shenanigans, on the one hand it's an undeniable way to spread awareness and usage of Bitcoin, on the other hand it's concerning that the chain gets incredibly congested whenever there is even moderate hype...
A Layer2 for Bitcoin (similar to ZK rollups of Ethereum) can be the next natural step forward...
...
Isn't this when the block was confirmed, as the longest chain? Hence the 28 minute delay for subsequent blocks to be added.
From fork monitor it seems the two conflicting blocks were created a few seconds apart: https://forkmonitor.info/stale/788837
No.They submitted their 788837 block to the world wide bitcoin network 28 minutes after fupoo did.
Isn't this when the block was confirmed, as the longest chain? Hence the 28 minute delay for subsequent blocks to be added.
From fork monitor it seems the two conflicting blocks were created a few seconds apart: https://forkmonitor.info/stale/788837
It is as I said.
You see, an interesting thing about my pool that's rather good
I have 10 nodes in various places over the planet and I see when blocks are distributed to the network
(and I distribute blocks faster than the other pools this way also due to other reasons)
Every single node shows this abomination caused by foundry.
Aside: the timestamp in the block header is NOT when it was sent to the network, and not even when it was found.
Well fair enough, if you have 10 nodes I'll take your word for it, as I'm only following 3rd party data here. Is it not possible that Foundry's nodes aren't updating quick enough, so they are simply just trying to mine blocks that have already been mined without realising it? I'd like to believe DaveF's theory that this is likely out of incompetence, as there isn't any financial benefit for a mining pool to do this right?
That said, he also mentioned that if it happened again they are evil (which has since happened as you pointed out). So now I don't know what to think
...
Isn't this when the block was confirmed, as the longest chain? Hence the 28 minute delay for subsequent blocks to be added.
From fork monitor it seems the two conflicting blocks were created a few seconds apart: https://forkmonitor.info/stale/788837
No.They submitted their 788837 block to the world wide bitcoin network 28 minutes after fupoo did.
Isn't this when the block was confirmed, as the longest chain? Hence the 28 minute delay for subsequent blocks to be added.
From fork monitor it seems the two conflicting blocks were created a few seconds apart: https://forkmonitor.info/stale/788837
It is as I said.
You see, an interesting thing about my pool that's rather good
I have 10 nodes in various places over the planet and I see when blocks are distributed to the network
(and I distribute blocks faster than the other pools this way also due to other reasons)
Every single node shows this abomination caused by foundry.
Aside: the timestamp in the block header is NOT when it was sent to the network, and not even when it was found.
Edit: you'll see in my first post, the failed blocks never even made it onto the main chain.
High network usage of what?
Many transaction in the mempool maybe? I'm sure a miner can explain the reasoning better, but last time there were these types of splits was in Nov 2020 when the mempool was quite full as well.
They submitted their 788837 block to the world wide bitcoin network 28 minutes after fupoo did.
Isn't this when the block was confirmed, as the longest chain? Hence the 28 minute delay for subsequent blocks to be added and the block to be confirmed as longest chain.
From fork monitor it seems the two conflicting blocks were created (or recognised at least) only a few seconds apart: https://forkmonitor.info/stale/788837
Very interesting, just to be completely clear as I think you have great experience on this subject, what determines the chances / reasons of a pool confirming the block that has a later timestamp than the orphaned one, especially in this case when the later block even has acquired less fees ?..
Lol, no I'm really not that experienced, but I know how to do my own research and which websites to look at
Think I already answered this question, but if the time difference is 3 seconds, then probably dumb luck comes into play...
Nice theory, but the F2Pool block had a fees reward of 5.683, whereas the Foundry block was less than that at 5.267. If I had to guess, the temporary chain-splits are due to high network usage rather than much else.
Very interesting, just to be completely clear as I think you have great experience on this subject, what determines the chances / reasons of a pool confirming the block that has a later timestamp than the orphaned one, especially in this case when the later block even has acquired less fees ?..
what are (or can be) legitimate reasons for a pool to confirm a late stale block, and orphaning the higher fee block which actually was solved earlier ?
...
Nice theory, but the F2Pool block had a fees reward of 5.683, whereas the Foundry block was less than that at 5.267. If I had to guess, the temporary chain-splits are due to high network usage rather than much else.
High network usage of what?Nice theory, but the F2Pool block had a fees reward of 5.683, whereas the Foundry block was less than that at 5.267. If I had to guess, the temporary chain-splits are due to high network usage rather than much else.
They submitted their 788837 block to the world wide bitcoin network 28 minutes after fupoo did.
... and they've done it again too ... but this time they forced a win 
2023-05-08T21:05:08.481915Z 788834 slush
2023-05-08T21:16:38.668872Z 788835 fupoo
2023-05-08T21:34:32.481238Z 788836 foundry
2023-05-08T21:41:54.191191Z 788837 fupoo
BUT then
2023-05-08T22:09:12.830416Z 788837 foundry 28 minutes late
2023-05-08T22:09:17.733790Z 788838 foundry confirming their 28 minutes late stale block and orphaning the fupoo block
So clearly foundry is screwing around with bitcoin
Code:
2023-05-08T21:05:08.481915Z PNB cb bn=788834 hash=00000000000000000002ce9a66b3b635737634ea3ed4b7b366f6bd9a3b6303d7 sig='0x03b0x090x0c0xfa0xbemm0x170xbdU70xa1!0xb9lQ0xcc0x87,0xf00xf0zg0x950xb40xcb0x1f0xfb0xe00xd50x8dR0x930x9e0x8e0xed0x860xfdP0x010x000x000x000x000x000x000x000x03e0x070x030x020x1a0x99K0x130x000x000x000x000x000x00I70x800xbf0x1d/slush/' (75)
2023-05-08T21:16:38.668872Z PNB cb bn=788835 hash=0000000000000000000343770ef3abc9b03a01a1c4466cfe64479f180ccbb971 sig='0x03c0x090x0c,0xfa0xbemm0x9c0xe80xe9ZK0xb00xb1G0x970x0f0xf20x07$J0x02q0x8d0xb8q0xe2h0x930xea0x9a0xfap0x82'm0x96PF0x100x000x000x000xf00x9f0x900x9f0x09/F2Pool/s0x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x050x00g0xe60x19c' (100)
2023-05-08T21:34:32.481238Z PNB cb bn=788836 hash=0000000000000000000018e509a36935f22951d9da5ca7b2623ca817b971a09a sig='0x03d0x090x0c0x040xbbjYd/Foundry USA Pool #dropgold/0x0d0xb4PJ0x820x0bf0x000x000x000x000x00' (49)
2023-05-08T21:41:54.191191Z PNB cb bn=788837 hash=00000000000000000002f51100fafb5c60b2dc9623554c219afef3cf398cecbe sig='0x03e0x090x0c,0xfa0xbemm0xf9!0xbew0xee[0xc00xc7"AX0x9f0xca0x0cW0xb60xbd0x1d0x1bn2(0x8e0xf40xc50x1c_-0x100xd60xfaC0x100x000x000x000xf00x9f0x900x9f0x09/F2Pool/s0x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x050x000x150x010x000x00' (100)
2023-05-08T22:09:12.830416Z PNB cb bn=788837 hash=00000000000000000000fde2b5105e8d43fc1d48e5da6478c6776a4a33408a82 sig='0x03e0x090x0c0x04}lYd/Foundry USA Pool #dropgold/0x10k0x8d0xd80xf60x1c0x010x000x000x000x000x00' (49)
2023-05-08T22:09:17.733790Z PNB cb bn=788838 hash=000000000000000000034b33d680c897cbc3dd70ee54e74727f5711f17a06463 sig='0x03f0x090x0c0x040xcbrYd/Foundry USA Pool #dropgold/0x0en^0x020x000x000x9c0x1e0xce0xad0x020x00' (49)
2023-05-08T21:16:38.668872Z 788835 fupoo
2023-05-08T21:34:32.481238Z 788836 foundry
2023-05-08T21:41:54.191191Z 788837 fupoo
BUT then
2023-05-08T22:09:12.830416Z 788837 foundry 28 minutes late
2023-05-08T22:09:17.733790Z 788838 foundry confirming their 28 minutes late stale block and orphaning the fupoo block
So clearly foundry is screwing around with bitcoin
https://mempool.space/mining shows block 788837 is F2Pool, not Foundry as your post suggests. Am I missing something?
Yes, although the hash for that block "00000000000000000002f51100fafb5c60b2dc9623554c219afef3cf398cecbe" shows up on mempool space, the transactions within are unconfirmed as they were replaced with hash "00000000000000000000fde2b5105e8d43fc1d48e5da6478c6776a4a33408a82" by Foundry for block 788837. See more here: https://forkmonitor.info/stale/788837.
It seems mempool.space still shows the invalid blocks based on their hashes, and doesn't seem to reference the fact that they are orphaned blocks.
I would estimate there is a 90%++ chance that the reason for this interference is frontrunning BRC20 mints after seeing huge price appreciation in the market,
Nice theory, but the F2Pool block had a fees reward of 5.683, whereas the Foundry block was less than that at 5.267. If I had to guess, the temporary chain-splits are due to high network usage rather than much else.
...
https://mempool.space/mining shows block 788837 is F2Pool, not Foundry as your post suggests. Am I missing something?
Coz mempool is wrong https://mempool.space/mining shows block 788837 is F2Pool, not Foundry as your post suggests. Am I missing something?
788837
fupoo is 00000000000000000002f51100fafb5c60b2dc9623554c219afef3cf398cecbe
foundry is 00000000000000000000fde2b5105e8d43fc1d48e5da6478c6776a4a33408a82
Code:
788840 00000000000000000000ae234c2137d8df6671e355012da2a7951f51513429fc = Luxor
prev = 0000000000000000000540543428d041299d6e2e35024c0bab0341bd153ab5e4 (788839 viabtc)
788839 0000000000000000000540543428d041299d6e2e35024c0bab0341bd153ab5e4 = viabtc
prev = 000000000000000000034b33d680c897cbc3dd70ee54e74727f5711f17a06463 (788838 foundry)
788838 000000000000000000034b33d680c897cbc3dd70ee54e74727f5711f17a06463 = foundry
prev = 00000000000000000000fde2b5105e8d43fc1d48e5da6478c6776a4a33408a82 (788837 foundry)
Clearly mempool at least has trouble handling re-orgs.
https://mempool.space/mining shows block 788837 is F2Pool, not Foundry as your post suggests. Am I missing something?
1. BTC.com says Foundry USA - https://explorer.btc.com/btc/block/7888372. Blockchain.com says Foundry USA - https://www.blockchain.com/explorer/blocks/btc/788837
3. Blockchair.com say Foundry USA - https://blockchair.com/bitcoin/block/788837
Not sure what's going on with mempool.space
... and they've done it again too ... but this time they forced a win
2023-05-08T21:05:08.481915Z 788834 slush
2023-05-08T21:16:38.668872Z 788835 fupoo
2023-05-08T21:34:32.481238Z 788836 foundry
2023-05-08T21:41:54.191191Z 788837 fupoo
BUT then
2023-05-08T22:09:12.830416Z 788837 foundry 28 minutes late
2023-05-08T22:09:17.733790Z 788838 foundry confirming their 28 minutes late stale block and orphaning the fupoo block
So clearly foundry is screwing around with bitcoin
Code:
2023-05-08T21:05:08.481915Z PNB cb bn=788834 hash=00000000000000000002ce9a66b3b635737634ea3ed4b7b366f6bd9a3b6303d7 sig='0x03b0x090x0c0xfa0xbemm0x170xbdU70xa1!0xb9lQ0xcc0x87,0xf00xf0zg0x950xb40xcb0x1f0xfb0xe00xd50x8dR0x930x9e0x8e0xed0x860xfdP0x010x000x000x000x000x000x000x000x03e0x070x030x020x1a0x99K0x130x000x000x000x000x000x00I70x800xbf0x1d/slush/' (75)
2023-05-08T21:16:38.668872Z PNB cb bn=788835 hash=0000000000000000000343770ef3abc9b03a01a1c4466cfe64479f180ccbb971 sig='0x03c0x090x0c,0xfa0xbemm0x9c0xe80xe9ZK0xb00xb1G0x970x0f0xf20x07$J0x02q0x8d0xb8q0xe2h0x930xea0x9a0xfap0x82'm0x96PF0x100x000x000x000xf00x9f0x900x9f0x09/F2Pool/s0x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x050x00g0xe60x19c' (100)
2023-05-08T21:34:32.481238Z PNB cb bn=788836 hash=0000000000000000000018e509a36935f22951d9da5ca7b2623ca817b971a09a sig='0x03d0x090x0c0x040xbbjYd/Foundry USA Pool #dropgold/0x0d0xb4PJ0x820x0bf0x000x000x000x000x00' (49)
2023-05-08T21:41:54.191191Z PNB cb bn=788837 hash=00000000000000000002f51100fafb5c60b2dc9623554c219afef3cf398cecbe sig='0x03e0x090x0c,0xfa0xbemm0xf9!0xbew0xee[0xc00xc7"AX0x9f0xca0x0cW0xb60xbd0x1d0x1bn2(0x8e0xf40xc50x1c_-0x100xd60xfaC0x100x000x000x000xf00x9f0x900x9f0x09/F2Pool/s0x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x050x000x150x010x000x00' (100)
2023-05-08T22:09:12.830416Z PNB cb bn=788837 hash=00000000000000000000fde2b5105e8d43fc1d48e5da6478c6776a4a33408a82 sig='0x03e0x090x0c0x04}lYd/Foundry USA Pool #dropgold/0x10k0x8d0xd80xf60x1c0x010x000x000x000x000x00' (49)
2023-05-08T22:09:17.733790Z PNB cb bn=788838 hash=000000000000000000034b33d680c897cbc3dd70ee54e74727f5711f17a06463 sig='0x03f0x090x0c0x040xcbrYd/Foundry USA Pool #dropgold/0x0en^0x020x000x000x9c0x1e0xce0xad0x020x00' (49)
2023-05-08T21:16:38.668872Z 788835 fupoo
2023-05-08T21:34:32.481238Z 788836 foundry
2023-05-08T21:41:54.191191Z 788837 fupoo
BUT then
2023-05-08T22:09:12.830416Z 788837 foundry 28 minutes late
2023-05-08T22:09:17.733790Z 788838 foundry confirming their 28 minutes late stale block and orphaning the fupoo block
So clearly foundry is screwing around with bitcoin
https://mempool.space/mining shows block 788837 is F2Pool, not Foundry as your post suggests. Am I missing something?
... and they've done it again too ... but this time they forced a win
2023-05-08T21:05:08.481915Z 788834 slush
2023-05-08T21:16:38.668872Z 788835 fupoo
2023-05-08T21:34:32.481238Z 788836 foundry
2023-05-08T21:41:54.191191Z 788837 fupoo
BUT then
2023-05-08T22:09:12.830416Z 788837 foundry 28 minutes late
2023-05-08T22:09:17.733790Z 788838 foundry confirming their 28 minutes late stale block and orphaning the fupoo block
So clearly foundry is screwing around with bitcoin
Code:
2023-05-08T21:05:08.481915Z PNB cb bn=788834 hash=00000000000000000002ce9a66b3b635737634ea3ed4b7b366f6bd9a3b6303d7 sig='0x03b0x090x0c0xfa0xbemm0x170xbdU70xa1!0xb9lQ0xcc0x87,0xf00xf0zg0x950xb40xcb0x1f0xfb0xe00xd50x8dR0x930x9e0x8e0xed0x860xfdP0x010x000x000x000x000x000x000x000x03e0x070x030x020x1a0x99K0x130x000x000x000x000x000x00I70x800xbf0x1d/slush/' (75)
2023-05-08T21:16:38.668872Z PNB cb bn=788835 hash=0000000000000000000343770ef3abc9b03a01a1c4466cfe64479f180ccbb971 sig='0x03c0x090x0c,0xfa0xbemm0x9c0xe80xe9ZK0xb00xb1G0x970x0f0xf20x07$J0x02q0x8d0xb8q0xe2h0x930xea0x9a0xfap0x82'm0x96PF0x100x000x000x000xf00x9f0x900x9f0x09/F2Pool/s0x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x050x00g0xe60x19c' (100)
2023-05-08T21:34:32.481238Z PNB cb bn=788836 hash=0000000000000000000018e509a36935f22951d9da5ca7b2623ca817b971a09a sig='0x03d0x090x0c0x040xbbjYd/Foundry USA Pool #dropgold/0x0d0xb4PJ0x820x0bf0x000x000x000x000x00' (49)
2023-05-08T21:41:54.191191Z PNB cb bn=788837 hash=00000000000000000002f51100fafb5c60b2dc9623554c219afef3cf398cecbe sig='0x03e0x090x0c,0xfa0xbemm0xf9!0xbew0xee[0xc00xc7"AX0x9f0xca0x0cW0xb60xbd0x1d0x1bn2(0x8e0xf40xc50x1c_-0x100xd60xfaC0x100x000x000x000xf00x9f0x900x9f0x09/F2Pool/s0x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x050x000x150x010x000x00' (100)
2023-05-08T22:09:12.830416Z PNB cb bn=788837 hash=00000000000000000000fde2b5105e8d43fc1d48e5da6478c6776a4a33408a82 sig='0x03e0x090x0c0x04}lYd/Foundry USA Pool #dropgold/0x10k0x8d0xd80xf60x1c0x010x000x000x000x000x00' (49)
2023-05-08T22:09:17.733790Z PNB cb bn=788838 hash=000000000000000000034b33d680c897cbc3dd70ee54e74727f5711f17a06463 sig='0x03f0x090x0c0x040xcbrYd/Foundry USA Pool #dropgold/0x0en^0x020x000x000x9c0x1e0xce0xad0x020x00' (49)
2023-05-08T21:16:38.668872Z 788835 fupoo
2023-05-08T21:34:32.481238Z 788836 foundry
2023-05-08T21:41:54.191191Z 788837 fupoo
BUT then
2023-05-08T22:09:12.830416Z 788837 foundry 28 minutes late
2023-05-08T22:09:17.733790Z 788838 foundry confirming their 28 minutes late stale block and orphaning the fupoo block
So clearly foundry is screwing around with bitcoin
I would estimate there is a 90%++ chance that the reason for this interference is frontrunning BRC20 mints after seeing huge price appreciation in the market,
just for my education what happens when it's discovered that a mining pool is trying to manipulate the blockchain for monetary gain, and as a result many legitimate transactions are rejected and front run ?..
... and they've done it again too ... but this time they forced a win
2023-05-08T21:05:08.481915Z 788834 slush
2023-05-08T21:16:38.668872Z 788835 fupoo
2023-05-08T21:34:32.481238Z 788836 foundry
2023-05-08T21:41:54.191191Z 788837 fupoo
BUT then
2023-05-08T22:09:12.830416Z 788837 foundry 28 minutes late
2023-05-08T22:09:17.733790Z 788838 foundry confirming their 28 minutes late stale block and orphaning the fupoo block
So clearly foundry is screwing around with bitcoin
Code:
2023-05-08T21:05:08.481915Z PNB cb bn=788834 hash=00000000000000000002ce9a66b3b635737634ea3ed4b7b366f6bd9a3b6303d7 sig='0x03b0x090x0c0xfa0xbemm0x170xbdU70xa1!0xb9lQ0xcc0x87,0xf00xf0zg0x950xb40xcb0x1f0xfb0xe00xd50x8dR0x930x9e0x8e0xed0x860xfdP0x010x000x000x000x000x000x000x000x03e0x070x030x020x1a0x99K0x130x000x000x000x000x000x00I70x800xbf0x1d/slush/' (75)
2023-05-08T21:16:38.668872Z PNB cb bn=788835 hash=0000000000000000000343770ef3abc9b03a01a1c4466cfe64479f180ccbb971 sig='0x03c0x090x0c,0xfa0xbemm0x9c0xe80xe9ZK0xb00xb1G0x970x0f0xf20x07$J0x02q0x8d0xb8q0xe2h0x930xea0x9a0xfap0x82'm0x96PF0x100x000x000x000xf00x9f0x900x9f0x09/F2Pool/s0x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x050x00g0xe60x19c' (100)
2023-05-08T21:34:32.481238Z PNB cb bn=788836 hash=0000000000000000000018e509a36935f22951d9da5ca7b2623ca817b971a09a sig='0x03d0x090x0c0x040xbbjYd/Foundry USA Pool #dropgold/0x0d0xb4PJ0x820x0bf0x000x000x000x000x00' (49)
2023-05-08T21:41:54.191191Z PNB cb bn=788837 hash=00000000000000000002f51100fafb5c60b2dc9623554c219afef3cf398cecbe sig='0x03e0x090x0c,0xfa0xbemm0xf9!0xbew0xee[0xc00xc7"AX0x9f0xca0x0cW0xb60xbd0x1d0x1bn2(0x8e0xf40xc50x1c_-0x100xd60xfaC0x100x000x000x000xf00x9f0x900x9f0x09/F2Pool/s0x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x000x050x000x150x010x000x00' (100)
2023-05-08T22:09:12.830416Z PNB cb bn=788837 hash=00000000000000000000fde2b5105e8d43fc1d48e5da6478c6776a4a33408a82 sig='0x03e0x090x0c0x04}lYd/Foundry USA Pool #dropgold/0x10k0x8d0xd80xf60x1c0x010x000x000x000x000x00' (49)
2023-05-08T22:09:17.733790Z PNB cb bn=788838 hash=000000000000000000034b33d680c897cbc3dd70ee54e74727f5711f17a06463 sig='0x03f0x090x0c0x040xcbrYd/Foundry USA Pool #dropgold/0x0en^0x020x000x000x9c0x1e0xce0xad0x020x00' (49)
2023-05-08T21:16:38.668872Z 788835 fupoo
2023-05-08T21:34:32.481238Z 788836 foundry
2023-05-08T21:41:54.191191Z 788837 fupoo
BUT then
2023-05-08T22:09:12.830416Z 788837 foundry 28 minutes late
2023-05-08T22:09:17.733790Z 788838 foundry confirming their 28 minutes late stale block and orphaning the fupoo block
So clearly foundry is screwing around with bitcoin
And this is why you shouldn't be putting all your eggs in the same basket (mining to the biggest pool)...
Well since they have a pool, I guess miners should stop using them until they start behaving again... don't you think?
I think foundry attempted to modify the blockchain by adding their own blocks, which caused a conflict with the existing chain.It seems that foundry attempted to perform a rollback of two blocks to modify the blockchain to their liking, but they were unsuccessful. This is a concerning situation, as it suggests that foundry may be attempting to manipulate the blockchain for their own benefit. Without more information, it is impossible to determine the exact motivations behind foundry's actions. However, any attempt to temper with the blockchain is highly problematic, as the blockchain's security relies on the assumption that all nodes are working together honestly.
Or, they have a configuration issue and had a problem with something and just messed up.
It's the don't try to find malevolence when something can be explained by incompetence.
Could even not be pure incompetence, did they have their mempool setting at 1GB and decided to increase it and something else broke along the way.
Did they update one their BGP routers for the new vulnerability and it took a bit longer to get back online and one of their nodes did not see the antpool block.
And so on...
If it happens again, THEN you start thinking about them going evil.
-Dave
It's the don't try to find malevolence when something can be explained by incompetence.
Could even not be pure incompetence, did they have their mempool setting at 1GB and decided to increase it and something else broke along the way.
Did they update one their BGP routers for the new vulnerability and it took a bit longer to get back online and one of their nodes did not see the antpool block.
And so on...
If it happens again, THEN you start thinking about them going evil.
-Dave
Well since they have a pool, I guess miners should stop using them until they start behaving again... don't you think?
Interesting set of blocks about a day ago:
As can be seen, but summarised:
2023-05-07T20:43:13.656356Z 788685 AntPool
2023-05-07T20:45:22.024705Z 788686 AntPool
2023-05-07T20:47:23.851828Z 788687 AntPool
Then foundry starts fucking with the blockchain
2023-05-07T20:47:32.038157Z 788686 foundry
2023-05-07T20:47:32.959478Z 788687 foundry
2023-05-07T20:57:29.084999Z 788688 emcd
They tried to roll back two blocks, but failed.
(emcd confirmed 788687 AntPool)
Clearly foundry is doing something VERY stupid.
Code:
2023-05-07T20:43:13.656356Z PNB cb bn=788685 hash=000000000000000000015221d97f2a108ae4bfea27639592f6cf17a2effc5fa6 sig='0x030xcd0x080x0c0x1bMined by AntPool970`0x000x110x030xdb`m80xfa0xbemm0xad0xa30x0c0x04K0xfb0xc0G&Z0x990x000x00o0x0e0xfe0xc20xee0xb10xf70x850xbf]0xb0A0x86J0xb6R0xd10xa40x870x020x000x000x000x000x000x000x000x000x000xffL0x900x030x000x000x000x000x000x00' (88)
2023-05-07T20:45:22.024705Z PNB cb bn=788686 hash=000000000000000000044be25d4e7407622329317a46c3949aebd3cc5f925d7f sig='0x030xce0x080x0c0x1bMined by AntPool971`0x00K0x030xdc"s0x930xfa0xbemm0xbc0xa70xe02023-05-07T20:47:23.851828Z PNB cb bn=788687 hash=0000000000000000000012e1d19037d2dabc3a89beac2169bb1e7d2913211cdb sig='0x030xcf0x080x0c0x1bMined by AntPool959`0x00S0x000xdc0xbb0x0b0x0c0xfa0xbemma-0x96T0xe90xd90x8e0xaeP0xf60xb10xd80xe380xd4Cas0x9d0xbb0x010x9f0xd70x960x070xa60x9cH0xca0xf8_[0x020x000x000x000x000x000x000x000x000x00Clb0x000x000x000x000x000x000x00' (88)
2023-05-07T20:47:32.038157Z PNB cb bn=788686 hash=000000000000000000032e2236a4c96c9dfc0f9f7993be6675fefb8fb6200b4b sig='0x030xce0x080x0c0x040xd70x0dXd/Foundry USA Pool #dropgold/0x1c0xe1|uP0x000x000x000x000x000x000x00' (49)
2023-05-07T20:47:32.959478Z PNB cb bn=788687 hash=0000000000000000000070ec61b72a3cab40a0f5cea33e4266a08044fd48ee27 sig='0x030xcf0x080x0c0x04G0x0eXd/Foundry USA Pool #dropgold/0x0a0x9f>0x00v0x910x010x000x000x000x000x00' (49)
2023-05-07T20:57:29.084999Z PNB cb bn=788688 hash=00000000000000000003e69e381c0dd941e4ae5e759f355e279d319157c084a9 sig='0x030xd00x080x0c0x13emcd.io10070xa80x000xdd0x020xe0X0xd40xa50xfa0xbemm'0xb90x96t0xf70xd60xf80x83UY0xfe0x0eT=j0xf3L0xdf0xfe0x16 G0x8d0x144a0x164!0x9fQ0x0a0x040x000x000x000x000x000x000x000x000x000x1eGKc0x000x000x000x000x000x00' (80)
As can be seen, but summarised:
2023-05-07T20:43:13.656356Z 788685 AntPool
2023-05-07T20:45:22.024705Z 788686 AntPool
2023-05-07T20:47:23.851828Z 788687 AntPool
Then foundry starts fucking with the blockchain
2023-05-07T20:47:32.038157Z 788686 foundry
2023-05-07T20:47:32.959478Z 788687 foundry
2023-05-07T20:57:29.084999Z 788688 emcd
They tried to roll back two blocks, but failed.
(emcd confirmed 788687 AntPool)
Clearly foundry is doing something VERY stupid.
Jump to: