Yes. This is the first project where vibe coding has proven helpful to me: I used an LLM to implement my protocol for checking if a pruned utxo is unspent, and it seems to work. So now I'm thinking of making a node implementation that lets users prune the utxo set, and when that setting is used, I'm wondering what amount of memory I should allocate to store the most recently created utxos. The more you keep, the less network queries you have to make. Perhaps I should just do some tests with different memory allocations and make a chart to visualize the results. This protocol would massively slow down IBD if it prunes too aggressively, but I bet it would be a decent tradeoff if the numbers come out to something like, "you need 500 megabytes of memory to store 99% of the utxos that get created and consumed in a given day, and 1% of the time you'll have to do a network query because a pruned utxo got spent."