it is worth noting that this same "problem" would also occur if bitcoin had a large number of UTXOs for other reasons (like lots of users taking self-custody)

it's a problem that would need to be solved (and is being solved by solutions like zerosync and utreexo) regardless of the use-case that caused it.

I think it's easy to forget because it's not a big problem if you're already running a node that's been up for a long time, since you only need to validate once every 10 minutes or so.  I only realized it when I decided to rebuild my node from scratch.
