SIGN’s wCBDC promises regulatory transparency — but the real question is: who else is watching?
Digging into the wholesale architecture reveals something subtle but important.
The whitepaper highlights “RTGS-level transparency,” meaning regulators get full visibility into interbank settlements on Fabric X. That part makes sense — central banks need complete oversight to monitor liquidity, risk, and systemic stability.
But in traditional RTGS systems, transparency is asymmetric by design:
The central bank sees everything
Each bank sees only its own transactions
Banks do not see each other’s settlement flows
That confidentiality isn’t just a feature — it’s critical. Settlement flows can expose competitive positioning, liquidity stress, and counterparty relationships.
Now here’s where it gets interesting.
Fabric X is built on Hyperledger Fabric, where banks operate peer nodes holding ledger data. By default, that raises a concern:
👉 Do banks gain visibility into each other’s flows?
Technically, Hyperledger Fabric already solves this:
Private data collections
Channel-based isolation
These allow fine-grained control over who sees what.
The twist?
SIGN’s whitepaper clearly explains ZKP privacy for retail (rCBDC)… but stays quiet on the exact privacy configuration for wholesale (wCBDC) settlements.
So this isn’t a limitation — it’s a deployment choice.
The capability exists.
The architecture supports confidentiality.
But the real signal to watch is this:
👉 Does SIGN explicitly enforce private data collections for interbank settlement data?
Because in wholesale finance,
transparency for regulators is essential — but visibility between competitors is a risk. 👀