There are numerous occasions where record contents need to be verified. At least outside the personal/hobbyist realm. Some popular hash function (preferably SHA3 but any other would be OK also, if there are code size considerations) seems very appropriate to be part of the built-in set of available SQLite3 functions in the amalgamation, even if only enabled under some conditional directive. Ideally, the result should be a hex string, but there is already a hex function, so either way would be fine. One could sometimes include such hash function at the application layer but that would not allow internal SQLite3 processing from using it (e.g., triggers). Thank you.