That’s kind of weird, that each block payload is an entire SQLite database file. It means that the time to query the blockchain will grow linearly with the number of blocks (because you have to query every block), and you can’t run a query that might rely on data in two different blocks.
To me, the obvious way to do this would be to make each block payload a changeset, using the SQLite session extension. Then the database is the amalgamation of all the changesets. The overall goal of this project seems similar to Dat <https://datproject.org>, which is much more mature (but doesn’t use SQLite.) —Jens _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
