Every time I hear we'll add privacy later
I picture a compliance officer holding a spreadsheet of exceptions.
That's the friction. A bank wants shared infrastructure but can not expose client data. So privacy gets bolted on through permissioned chains, off chain databases and special carve outs. Each exception is one more thing an auditor has to understand, and one more place data can leak.
So I keep asking whether the data needs to be visible at all. That's roughly where @Nillion sits for me.
I see it as plumbing rather than a story: computation on data that stays split and encrypted so privacy is the default condition instead of a waiver.
The part I find more interesting is the boring one. Blacklight node operations are moving from Nillion's L2 to Ethereum L1. Regulated players care about where settlement and accountability live and an L2 is another trust assumption to explain. L1 is easier to point at. Costs and complexity probably go up, though, and I'm not sure institutions will care as much as I'd like.
Who would use it?
Likely teams where legal risk already outweighs engineering cost like healthcare identity and financial data sharing.
What breaks it: performance overhead, unclear regulator acceptance, and nobody wanting to go first. Privacy by design only works if someone is willing to sign off on it.
#nil
$NIL
I picture a compliance officer holding a spreadsheet of exceptions.
That's the friction. A bank wants shared infrastructure but can not expose client data. So privacy gets bolted on through permissioned chains, off chain databases and special carve outs. Each exception is one more thing an auditor has to understand, and one more place data can leak.
So I keep asking whether the data needs to be visible at all. That's roughly where @Nillion sits for me.
I see it as plumbing rather than a story: computation on data that stays split and encrypted so privacy is the default condition instead of a waiver.
The part I find more interesting is the boring one. Blacklight node operations are moving from Nillion's L2 to Ethereum L1. Regulated players care about where settlement and accountability live and an L2 is another trust assumption to explain. L1 is easier to point at. Costs and complexity probably go up, though, and I'm not sure institutions will care as much as I'd like.
Who would use it?
Likely teams where legal risk already outweighs engineering cost like healthcare identity and financial data sharing.
What breaks it: performance overhead, unclear regulator acceptance, and nobody wanting to go first. Privacy by design only works if someone is willing to sign off on it.
#nil
$NIL