Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> the company can retroactively create a conflicting chain of backdated signatures and purport it to be the canonical one


Again, that can be incredibly easily solved with signatures stored in a separate system of record - Effectively, publishing a git sha somewhere else on a regular basis. This is not a blockchain, this is a merkle tree, which is a good idea and is currently unimplemented.

The immense fraud and criminal behavior associated with the "Blockchain" ecosystem is the biggest inhibitor to actually good crypto being used for system-of-record. It sucks all the air out of the room and that's a bad thing.


Git does not guarantee the validity of timestamps stored within it, nor does it explicitly provide a single canonical tip. Those two guarantees are what prevent history from being forged.

> The immense fraud and criminal behavior associated with the "Blockchain" ecosystem is the biggest inhibitor to actually good crypto being used for system-of-record.

You could say the same thing about internet scams in the 90s. Eventually, everyone got over themselves and picked out the good parts.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: