The mainnet has same transaction hash bug also, such as both of blocks 39185599 and 39185611 has transaction hash 0x000f94c5677e68504bc8daabdb051d3f1e51fd626b59d9533f5fc55f656f6fd1. There is a fix already: github.com/XinFinOrg/XDPoSChain/pu.... Please wait for some time.
For further actions, you may consider blocking this person and/or reporting abuse
Please set
ETHEREUM_REORG_THRESHOLD
to 1. You can refer to github.com/XinFinOrg/XDC-Graph-Nod....That seems like a bandaid solution that will end up with incorrect data long term. From the graph node docs
Note that we're not seeing this against the XDC mainnet, only the testnet. Are the RPC calls I provided above expected and correct behavior?
I'm not sure whether the mainnet has this issue. This issue will affect some software. But It's a very big project to solve it.
I'll write a script to check the duplicate transaction hashes on mainnet when I'm free.
The mainnet has same transaction hash bug also, such as both of blocks 39185599 and 39185611 has transaction hash 0x000f94c5677e68504bc8daabdb051d3f1e51fd626b59d9533f5fc55f656f6fd1. There is a fix already: github.com/XinFinOrg/XDPoSChain/pu.... Please wait for some time.