Tableland is most usefully treated as smart-contract-controlled relational data infrastructure, not as a general blockchain or generic database startup.
The important analytical surface is the split between onchain mutation authority and offchain validator/gateway query serving.
No standalone whitepaper was located during this pass.
First-party docs repository README explaining that the protocol includes SQL and Gateway API specifications and framing Tableland as a web3-native relational database.
Official organization surface confirming the maintained validator and docs repositories.
Key takeaways captured for corpus
Tableland’s core mechanism is to mint tables and authorize mutations through EVM smart contracts while materializing the resulting SQL state in validator-run SQLite databases.
Validators are the execution unit of the system: they follow onchain events, enforce access assumptions, and expose readable state to applications.
The protocol meaningfully standardizes both a constrained SQL dialect and a gateway/query API, which makes the data-access layer part of the protocol surface rather than just an implementation detail.
Practical trust sits partly in validator availability and upstream RPC dependencies, because validators must reliably observe chain events before serving useful reads.
Tableland is a strong comparison class for Ceramic-style decentralized data systems because it chooses relational state materialization and contract-owned tables instead of stream-oriented authenticated event history.