Hi everyone,
Like many of you, I have developed severe “data-slurp fatigue.” But beyond privacy concerns, I’ve come to realize it’s a massive architectural inefficiency: we are wasting storage and risking security through the aggressively growing duplication of our home addresses and emails across millions of servers just to complete basic digital actions.
As a counterweight to this, I formulated an architectural concept called UYC: Unknow Your Customer — the structural antithesis to ubiquitous KYC.
The core premise of UYC is that systems must be built so they physically cannot hold, see, or remember unnecessary personal data. Instead of hoarding information, architecture should naturally leverage cryptography and pseudonymization in scenarios where collecting, storing, or processing personal data is entirely unnecessary.
As a solo creator, I built Factflew (https://factflew.io/) specifically to test and prove that UYC is a viable foundation for a cleaner, independent web.
I’m bringing this to Lemmy to discuss the engineering reality of this approach:
- Is a UYC architecture viable at scale, or is the industry bound by too much engineering inertia when it comes to collecting data?
- How can we shift the developer mindset away from collecting everything “just in case”?
I am eager to hear your technical critique of the UYC principle and discuss whether we can build a leaner web. Cheers!
I was under the impression only Monero was anonymous, Bitcoin definitely keeps all traceability in the ledger. That along with kyc means your wallet is tied to you. Any transfer to cold wallets as well.
Unless you mine yourself. Then truly zero knowledge. But yes if you try to buy bitcoin via a bank thing then it will be an issue.
Even bitcoin that you mine in its entirety yourself is traced to the cold wallet you mined it into. You then need to maintain a disconnect between your identity and your cold wallet. All coin going from your cold to hot wallet is on the ledger.
The only way to keep the entire transaction cold is to just divide your coin yourself and give the hash on paper.
Then the recipient can cash the hash, so to speak. Idk if it has to be verified on the network though. If so, the trace is re-established.
Maybe someone else that knows how it works better will come in and call me ignorant and spit some facts.
Note: I’m not suggesting that these are good solutions to the problem, only that they were engineered to solve this type of problem.