I find it also funny they don't address the chicken-and-egg problem I am seeing of having to verify a new withdrawal address, which, of course, doesn't have any balance to do the test with in the first place. I'm assuming 'sometimes' (because they say 'might be') the satoshi test won't be needed? Just describe that situation and don't let us assume anything, but that's probably too logical...
Is anyone keeping track, using on-chain analytics, of how many people are doing this idiotic EU "satoshi test"? E.g, Kraken describes the procedure here, presumably other exchanges use variants, which makes for great fingerprinting.
https://support.kraken.com/hc/nl/articles/what-is-a-satoshi-test
Discussion
From what I've seen on Reddit, they solve the chicken-egg problem by having you buy some crypto (with fiat, below the threshhold amount), withdrawing it and then sending it back.
I can imagine that if you contact support they'll eventually offer another solution, but they could make you wait for weeks while your funds are stuck.
By solve I mean "solve",
Which means you've now gone from one deposit that doesn't stand out much on chain, to a very obvious pattern of receiving sats from the exchange and sending them back, all using the same address. Plus your bank sees a small transaction going to an exchange and a large one coming back, which might trigger their alarm and they hold you fiat ransom too.
And of course this fiat transaction pattern tells your bank that you're a self-custodial person.
For entirely new customers this is of course, are they assumed to get some balance from somewhere else, for the test?
