Do the sqlite replication systems depend upon WAL checksums?

Merkle hashes would probably be better.

google/trillian adds Merkle hashes to table rows.

sqlite-parquet-vtable would workaround broken WAL checksums.

sqlite-wasm-http is almost a replication system

Re: "Migration of the [sqlite] build system to autosetup" https://news.ycombinator.com/item?id=41921992 :

> There are many extensions of SQLite; rqlite (Raft in Go,), cr-sqlite (CRDT in C), postlite (Postgres wire protocol for SQLite), electricsql (Postgres), sqledge (Postgres), and also WASM: sqlite-wasm, sqlite-wasm-http, dqlite (Raft in Rust),

> awesome-sqlite

From "Adding concurrent read/write to DuckDB with Arrow Flight" https://news.ycombinator.com/item?id=42871219 :

> cosmos/iavl is a Merkleized AVL tree. https://github.com/cosmos/iavl

/? Merkle hashes for sqlite: https://www.google.com/search?q=Merkle+hashes+for+SQlite

A git commit hash is basically a Merkle tree root, as it depends upon the previous hashes before it.

Merkle tree: https://en.wikipedia.org/wiki/Merkle_tree

(How) Should merkle hashes be added to sqlite for consistency? How would merkle hashes in sqlite differ from WAL checksums?