I mean, technically SSA data might be a legitimate use of the blockchain. I am one of the biggest opponents of the whole mess, but there are use cases for a persistent immutable data record, and social security numbers would be one of them.

[–] Vanilla_PuddinFudge@infosec.pub 1 points 2 weeks ago (4 children)

The not-bullshit version of this already exists.

Many know it as MySQL, Postgres, etc.

Databases don't need Blockchains.

[–] dreadbeef@lemmy.dbzer0.com 0 points 2 weeks ago* (last edited 2 weeks ago) (3 children)

Damn why doesn't git just use sql instead of Merkle trees I guess that's just stupid tell Linus to get to using SQLite asap!!!

But no, you're wrong. Cryptographically verifiable merkle trees are a valuable way to store changing data. Unlike your recommendations, they don't satisfy the needs of verification, which is literally a great use-case for ssns. Now I'll admit that the SSN db doesn't need to be distributed, which is the only thing a blockchain adds to that equation. But you are just flat out wrong for suggesting a sql db 😂

[–] enumerator4829@sh.itjust.works 1 points 2 weeks ago

Or you know, trusted timestamps and cryptographic signatures via normal PKI. A Merkle tree isn’t worth shit legally if you can’t verify it against a trust outside of the tree.

All of the blockchain bullshit miss that part - you can create a cryptographic representation of money or contracts, but you can’t actually enforce, verify or trust anything in the real world without intermediaries. On the other hand, I can trust a certificate from a CA because there are verifiable actual real-world consequences for someone if that CA breaks legal agreements.

I’ll use a folder of actual papers, signed using a pen. Have some witnesses, make sure they have a legal stake and consequences, and you are golden.

load more comments (2 replies)

load more comments (9 replies)