Learn the basics of how to use the validator Gateway API or even run your own validator node.
A validator node is responsible for validating onchain transactions and materializing table state. The Tableland network exposes an HTTP API for interacting with validator nodes, called the Gateway API. Additionally, you can run your own validator node to participate in the network and manage the indexing on your own.
The Tableland Gateway API is organized around REST. You can leverage these APIs to read directly from tables, compose data across them, and make calls to learn information about the node itself.
Feel free to test out the Gateway API yourself in our interactive docs: here
In Tableland, Validators are the execution unit/actors of the protocol. They have the following responsibilities:
- Listen to onchain events to materialize Tableland-compliant SQL queries in a database engine (currently, SQLite by default).
- Serve read-queries (e.g:
SELECT * FROM foo_69_1) to the external world.
- Serve state queries (e.g. list tables, get receipts, etc) to the external world.
Keep in mind that a node listens to mainnet chains and testnet chains separately such that there are separate gateway URLs for each respective environment.