when the txhash_list is processed through the multithreading in concurrent futures the current order of transactions is staying in order as they were in the block. however the way the tx_index is being assigned can be somewhat random depending on thread execution. this makes tx_index unordered as per the block ordering and propogates into the ledger hash for txlist causing mismatches upon subsequent indexes because the tx_index may move around.
when the txhash_list is processed through the multithreading in concurrent futures the current order of transactions is staying in order as they were in the block. however the way the tx_index is being assigned can be somewhat random depending on thread execution. this makes tx_index unordered as per the block ordering and propogates into the ledger hash for txlist causing mismatches upon subsequent indexes because the tx_index may move around.
Fix pending final validation in feature branch