> since an enterprise blockchain is append-only, immutable, time-stamped, and each new entry has a hash of the previous view, it overcomes a lot of data integri

> since an enterprise blockchain is append-only, immutable, time-stamped, and each new entry has a hash of the previous view, it overcomes a lot of data integrity issues inherent to a distributed SQL database. And why couldn't a distributed SQL database be append-only, immutable, time-stamped, and implemented so each new entry has a hash of the previous state? (If you own it, just set it up to disallow updates or deletes, and allow inserts only through a trigger / stored procedure that adds the timestamp and hash.)