4 ms·
You can have an immutable centralized/federated system without using "crypto" though "proof-of-work", there are databases out there that provide immutable stor
by cphoover 5y ago
You can have an immutable centralized/federated system without using "crypto" though "proof-of-work", there are databases out there that provide immutable storage that don't require this overhead.
Providing api access to a signed immutable database makes sense... but I'm not sure how much sense utilizing existing popular cryptocurrencies would make (e.g. bitcoin, etherium)
- smt88 5y agoYou need cryptography for hashing and verifying the integrity of any copy of the database. You probably don't need proof of work, you're right.
- miunau 5y agoProof of work is not needed, just a pool of time servers that you can make a quorum out of. We're working on exactly this on top of roughtime (https://roughtime.googlesource.com/roughtime https://roughtime.googlesource.com/roughtime) for a future version of QR Date (https://qrdate.org/ https://qrdate.org/)
- asail77 5y agoGreat discussions! Some thoughts: First, there are multiple solutions to this problem, all need to be explored and many will have a part in the future. Bad actors will do everything they can to find a way around every solution. Second, for the hashing approach, have a look at "Perceptual Hashing", it's a way to hash content like a an image, even if the resolution changes. Where to store the hashes? A centralized server is probably fine, but there is always a risk of a bad actor exposing it somehow. A secure blockchain can work better. But if you go that route, might as well go with the most secure blockchain. POW is generally more secure than POS. And currently the most secure blockchain is Bitcoin. So one solution is to batch hashes together and write them with a Bitcoin transaction in some cadence. -Ali