Reth rejects block 635 — nodes stuck with "invalid ancestor"

[Lukplop]

Describe the bug

Testnet: Reth rejects block 635 — nodes stuck with "invalid ancestor"

Summary

We run 2 full nodes on Alpen testnet. Both fail to sync past block 635: Reth marks that block as invalid, so every subsequent block is rejected with Bad block with existing invalid ancestor. The public explorer shows block 635 as valid. A fresh sync (new node, empty storage) hits the same failure at block 635.

Environment

• Network: Alpen testnet (explorer.testnet.alpenlabs.io)
• Image: v0.2.0-rc8 (alpen-node)

Affected block

• Number: 635
• Hash: 0x47a664f49e889ed3d25f783e2d236ee1bf409cf9b00f1c6396c14e2dc5040149
• Parent: 0x6ba9b4d7f65e0150b172d9663ec5e161a4f047edf8721311d5229c0bf2d8d20a

Explorer: https://explorer.testnet.alpenlabs.io/block/0x47a664f49e889ed3d25f783e2d236ee1bf409cf9b00f1c6396c14e2dc5040149

Logs (execution container)

WARN Bad block with existing invalid ancestor ... invalid_ancestor=BlockWithParent { parent: 0x6ba9b4d7..., block: NumHash { number: 635, hash: 0x47a664f49e889ed3d25f783e2d236ee1bf409cf9b00f1c6396c14e2dc5040149 } }
INFO Received block from consensus engine number=10750 hash=0x...
WARN Encountered invalid block number=10750 hash=0x...

Same pattern for all blocks after 635.

Questions

1. Is block 635 a known bad block on testnet?
2. Is there a fixed node version or recommended sync source?
3. Is a testnet reset or other recovery step expected?

Steps to reproduce

Nodes setup from scrash

Platform(s)

No response

What is the sha256 checksum of the full node you are running?

No response

If you've built the full node from source, provide the full command you used

git clone --depth 1 https://github.com/alpenlabs/alpen.git && git fetch --depth 1 origin tag ${ALPEN_VERSION} && git checkout ${ALPEN_VERSION} RUSTFLAGS="-C link-arg=-Wl,-rpath-link=/usr/lib/x86_64-linux-gnu" cargo build --locked --release --bin alpen-reth --bin strata-client Rust version: 1.92 ALPEN_VERSION: corresponds to tag used in image v0.2.0-rc8

Code of Conduct

• I agree to follow the Code of Conduct

[barakshani]

Thanks for the report. This release should be stable.
Can you please check if you see the following error receipt root mismatch? [EDIT: after review we actually less suspect this is the case]
According to your report, some error is actually in block 364, so you may want to check an error with its processing. If you find it, please provide the entire error message.
In general, it is worth checking where is the first occurrence of an error in your reth log file.

[barakshani]

@Lukplop checking if you still need help with this issue.

[barakshani]

Closing due to lack of activity.