Does this happened to everyone ? Stuck on block number 21962149

[billyadelphia]

Does this happened to everyone ? Stuck on block number 21962149

isSync false
localRpc 21962149
https://bscrpc.com 21962144
https://bsc-dataseed.binance.org/ 21962149
bscscan 21962147

[sangbeomji89]

I have same issue.. https://bscscan.com/ also stop block update

[randyortonx]

The whole network is down

[utkarsssh17]

Chain is halted due to exploit.

[billyadelphia]

Chain is halted due to exploit.

For how long ? and where can I see the news ?

[utkarsssh17]

https://twitter.com/BNBCHAIN/status/1578148078636650496

[arthurwolf]

Same here. So glad to hear it's not just me, I was pulling my hair...

[ko0f]

Updated to new version 1.15, now getting BAD BLOCK messages.

Should we rollback to a certain block?

########## BAD BLOCK #########
Chain config: {ChainID: 56 Homestead: 0 DAO: <nil> DAOSupport: false EIP150: 0 EIP155: 0 EIP158: 0 Byzantium: 0 Constantinople: 0 Petersburg: 0 Istanbul: 0, Muir Glacier: 0, Ramanujan: 0, Niels: 0, MirrorSync: 5184000, Bruno: 13082000, Berlin: <nil>, YOLO v3: <nil>, CatalystBlock: <nil>, London: <nil>, ArrowGlacier: <nil>, MergeFork:<nil>, Euler: 18907621, Gibbs: <nil>, Nano: 21962149, Engine: parlia}

Number: 21962158
Hash: 0xc0cabd12b4ff205b3d7e04450eb09e9cd79b09ba22f3808d26a6619e30e2a495


Error: could not apply tx 443 [0x798c6ddd6c727fb3da5e437577e09f51f16ee03c0e2758b0673ce2cb18952b42]: gas limit reached
##############################

[ofarukcaki]

I'm also getting lots of bad block messages and my node stuck at block 21962155

1161: cumulative: 85105775 gas: 23658 contract: 0x0000000000000000000000000000000000000000 status: 0 tx: 0xef1cf77e94d2d55186885742cc06fa69bdec22263082018ffd1de1d55ff6341e logs: [] bloom: 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 state:
         1162: cumulative: 85150262 gas: 44487 contract: 0x0000000000000000000000000000000000000000 status: 1 tx: 0x3692a5674c5213db6a6863e2ba5c03a7a87e13773ac06f1b05811168d2b43da2 logs: [0xc007e18420] bloom: 00000200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000200000000008000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002000000000000000000000200000000000000000000800000000020000000000000000000000021000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000010000000000000008000000000000000000001000000000000000000000000 state:
         1163: cumulative: 85172590 gas: 22328 contract: 0x0000000000000000000000000000000000000000 status: 1 tx: 0x54d10dff21367ecc1f36dfc3d3f14a0f78dc51686e828dad4cf2fb858e189371 logs: [0xc007e184d0] bloom: 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000400000000400000000000000000000000000000000000000000000000000000000040000000000000000000000100000000000000000010000000000040000000000000080000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002000080000000000000000000000000000000000000000000000000000000000000000000 state:
         1164: cumulative: 85225209 gas: 52619 contract: 0x0000000000000000000000000000000000000000 status: 1 tx: 0x03bf4ff6e3700fb517a70cd13a1ac07ad3b205d0a5c5b79988c83263cf14d6cd logs: [0xc007e18580] bloom: 00000000000000000000000000000000000000000000000000000000000000000000000008002000000000100000000000000000000000000000000000000000000000000001000000000008000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000010000040000000000000000000000000000000000000000000800000000000000000000000000000000000000000000000000000000000800000000000000000000000000000000002000000080000000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000 state:
         ```

[sangbeomji89]

I changed v1.1.15 and succeed block update. I just change v1.1.13 geth binary to v1.1.15 and then restarted.

BTW, why bscscan is not updated?..hmm.. https://bscscan.com/

[sangbeomji89]

https://bscscan.com/ just started to update!!

[arthurwolf]

Is there a guide somewhere with information about what I should do to get my node back up and running?

[huangyisan]

Is there a guide somewhere with information about what I should do to get my node back up and running?

update to v1.1.15

[b10c77]

Updated from 1.1.11 to 1.1.15 but seems it's still stuck at block 21962155

instance: Geth/v1.1.5-8ff7d531/linux-amd64/go1.16.10

{
  currentBlock: 21962155,
  highestBlock: 21966614,
  knownStates: 297473485,
  pulledStates: 297473485,
  startingBlock: 21962155
}

Can't get past block 21962155

[ofarukcaki]

After hours, I restarted my node several times but still stuck at 21962155

[jackbbhua]

same at 21962155

[DeepBorys]

I have updated to 1.15, rolled back the chain a bit with debug.setHead() and restarted the sync. Worked for me.

[b10c77]

I have updated to 1.15, rolled back the chain a bit with debug.setHead() and restarted the sync. Worked for me.

To what block have you rolled back to? Rolled back 21960000 using:

debug.setHead("0x14F1540")

But now it's stuck at block 21960399

[kaber2]

More fine work brought to you by the good people of Binance Shit Chain. Despite the obvious mess ups like silently halting the chain etc, why the hell the "fix" adds blacklisting in one of the hottest paths of the txpool remains a mystery, that's just transient data and this adds unnecessary overhead for no reason at all.

[arthurwolf]

@kaber2 how about you push your opinion piece somewhere people want it, like on Twitter or something, and leave this place for constructive technical conversations?