Antoni Spaanderman

just to add, i run Core v25.0.0

i now regularly get these warnings about twice a day (max 10 on 6th of january), but before i would get them spammed in the log every 2 or so...

got master + #997 running on my node right now, will report later on the results as these messages did not show very often, also, no new `mempool sync failed`...

That works! thanks, i get the right txid, but could there be an easier way to just get the data, instead of having to subscribe, check if spending data is...

> `"No such mempool transaction. Use -txindex or provide a block hash to enable blockchain transaction queries. Use gettransaction for wallet transactions."` didn't bitcoind just only search the mempool because...

> IIUC, this optimization is used for optimizing txid index scan (by early-exiting the iteration) yes, exiting early means that after the right one if found no more block parsing...

reversing `blockhashes` is somewhat harder that sticking a `.rev()` adapter in between, but with `rocksdb::IteratorMode` a backwards iterator can be made, out of scope for this pr, but surely an...

> > the may be collisions in txids as long as no utxos from the utxo set would be overwritten by it. > > Not sure - do you mean...

> I think that #933 should resolve the ordering (returning the first matching tx), as well as not parsing the next blocks. i think as well (it reuses the old...

when running this pr on my node i got the following two messages (alongside the usual indexing 1 blocks, chain updated): `missing mempool entry: 9c75d38a3eeca395a2c6bb6bb4b14bf8126334f16c2da57b7a1753b930890748` and `missing mempool tx: f10483eaf7defa69ea77932b0839379466bfa5bec9a8fa9255e7aa0b1dd7ef45`...