2 ms·
Some of these miss the mark, e.g. depending on what you're doing with PII storing hashes or symmetric encryptions would work fine. Similarly, updates can be acc
by CydeWeys 8y ago
Some of these miss the mark, e.g. depending on what you're doing with PII storing hashes or symmetric encryptions would work fine. Similarly, updates can be accomplished by writing new entries, which is how Bitcoin works; you read all blocks ever and steadily build up a (local) database of all the unspent transactions, and update those as new blocks come in. Namecoin works similarly but for DNS entries. It's no different than replaying a transaction log in a standard DB (once) to reconstruct the current state.
Where >99% of blockchain proposals fall down, though, is that they don't actually need the "anyone can commit" property. Businesses sure as hell wouldn't allow random strangers to commit to their internal blockchain, so they don't really need one at all. They would only allow some small number of vetted, authenticated external parties to do so, in which case normal account mechanisms work fine.
- sigstoat 8y ago> Some of these miss the mark, e.g. depending on what you're doing with PII storing hashes or symmetric encryptions would work fine. granted that "depending on what you're doing" is a big caveat, but: i feel like there's a difference between encrypting my PII with an ephemeral session key, then sending it in some packets across the internet that are unlikely to be captured, and encrypting my PII with some not-very ephemeral key, then writing it to the disks of thousands or millions of people with a big "this is PII" sign on top of it.
- CydeWeys 8y agoThere wouldn't be a "this is PII" sign on top of it. By its nature you don't know what encrypted data is unless you can decrypt it, and there's many other things that people would be encrypting and putting on the blockchain that aren't PII (probably the vast majority of them wouldn't be). And that's only for the symmetric case anyway; in the hash case it's non-reversible and the majority of the blockchain data is already hashes anyway. Also, your "ephemeral encrypted packets" are probably logged to disk in multiple three-letter agency databases.