zhk101

it has been reported as well in one of the closed issues of the bnb48 snapshot repo, here https://github.com/48Club/bsc-snapshots/issues/150#issue-2261308800 I do see the same value `txIndexRemainingBlocks: 33602365` in my node...

I did try yes but that `txIndexRemainingBlocks` doesn't budge. I switched to using the full node (the 800gb one) with pbss (instead of hash-based) and it works fine. Also changed...

Btw, I was using the BNB48 fast snapshot that was done with 1.4.5, on my 1.4.6 node. Yesterday saw this https://github.com/48Club/bsc-snapshots/issues/151#issuecomment-2102135151 And also, this might be related to https://github.com/bnb-chain/bsc/issues/2437

Just assuming here, pointing at a comment I saw from the BNB48 snapshot publisher explicitly saying the need to use 1.4.5 for the snapshot. I haven't tried that snapshot with...

Ok so tried again with the latest fast node snapshot @du5 just released yersterday, on the same configuration mentioned above and the node is still synching for-ever because of `txIndexRemainingBlocks:...

Ok so for the sake of it I tried again what @zzzckck mentioned about specifying `--history.transactions=90000`. I could swear I tried at the time without success. Anyway, restart the node...

> * **48Club FastNode(~200GB):** > `state`: Only recent 129 blocks. `block`: Only recent 90k blocks > `receipts`: Only recent 90k blocks > `header`: Only recent 90k blocks I assumes these...