Sep 25, 2026

Of course we can! We can do it exceedingly well in fact. And we can do it in a way that sets us up for the tx graph. Aside from managing conflicting spends, there's really no need for an unconfirmed tx index unless you are mining. I've worked out a table mod to the validated_tx table as a SoA (multicolumn) that will allow us to scan for compact block identifiers using SIMD or GPU, though SIMD is plenty fast unless it's like a 100M txs in the pool. The genius of compact blocks is that you have to perform a linear scan over every single unconfirmed tx for every single compact_block.tx. It cannot be indexed, because the key changes with every new compact block. It's really the same model as silent payments (stealth) scanning. And in another stroke of batshit crazy, cb v2 operates over the wtxid, which wasn't necessary, isn't optimizing or DoS protecting, and there is no other compelling reason to store it. But it's 32 bytes per tx, which is huge. So finding a way to avoid this storage and the cost of sweeping it for every mined tx, and still validate the block in picoseconds is the challenge.