Agreed - putting encrypted data onchain is not a good idea. But not putting data onchain sacrifices verifiability.
A better approach is to put commitments (i.e., hashes) to private data onchain and provide ZKPs attested to the correctness to these commitments. This way, there is nothing for anyone to "harvest now, decrypt later", and at the same time the entire network can verify correctness of the global state.
Is encrypted data just a locked vault waiting to be cracked?
Digital Asset CEO Yuval Rooz says encrypted data could eventually be cracked, so Canton shares transaction data only with the parties involved, not across the network
"We don't have a centralized privacy solution. The
Maybe a controversial opinion: "not your keys, not your coins" meme did vastly more harm than good for crypto.
This doesn't mean that the idea of self-custody is bad (it is one of the core benefits of crypto), but rather that we should have built systems that do not require
Over the past few weeks I've gone from thinking leanPCS is total bull to being a total bull. So let me explain some of these buzzwords in more detail.
At the core, 8288 is about hyper-scaling data and execution for any computation that needs to get performed on a piece of data
A token can have long-term value for one of two reasons:
- It is backed by a business with revenue.
- It becomes money.
In the second case, SoV is one approach, but it'd surely be more beneficial if the token also had practical utility (e.g., it would have been great if Bitcoin was both SoV and a functional payment network).