I was reading through SIGN’s CBDC design, and something clicked that I can’t really ignore now.
At first, it sounds clean. Compliance is built directly into the system AML checks, transfer limits, reporting all automated. No paperwork, no delays, everything just works in the background.
But then I started thinking about what that actually means in practice.
If every transaction runs through a compliance check, then every action you take creates a record. Not just the transaction, but the fact that it happened, when it happened, and that it passed (or failed) the check.
And those records are stored permanently.
So on one side, you have privacy. The actual details amount, sender, receiver are protected.
But on the other side, there’s still a trail being created every time you do something.
And even without the full details, that trail can say a lot. How often you transact, when you’re active, whether anything gets flagged. Over time, that builds a pattern.
Then there’s the limit part.
Every transaction is checked before it even goes through. If your limit is reduced even to zero you still see your balance, your wallet looks fine but nothing works. You can’t send anything. And you might not even know why.
From your side, it feels like the system is broken.
From the system’s side, it’s doing exactly what it’s supposed to.
And then there’s reporting.
It happens automatically, but it’s not really clear who gets that data, what exactly is included, or whether users even see it.
So now I’m just sitting with this question
Is this actually making compliance easier and smoother?
Or is it quietly turning every transaction into a permanent record where we don’t fully know what’s being tracked? Still trying to understand where the balance really is.