A Go language implementation of the Tableland validator, enabling developers and service providers to run nodes on the Tableland network and host databases for web3 users and applications.
Validators are the execution unit/actors of the protocol.
They have the following responsibilities:
- Listen to on-chain 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.
💡 The responsibilities of the validator will continue to change as the Tableland protocol evolves. In the future, validators will have more responsibilities in the network.
The following is a diagram that describes at a high level the interaction between the validator, EVM-chains, and the external world:
To understand better the usual work mechanics of the validator, let’s go through a typical use-case where a user mints a table, adds data to the table, and reads it:
1- The user will mint a table in the Registry smart contract.
2- The Registry contract will emit a CreateTable event containing the CREATE TABLE statement as extra data.
3- Validators will detect the new event and execute the CREATE TABLE statement.
4- The user will call the runSQL method in the Registry smart contract, with mutating statements such as INSERT INTO ....
5- The Registry contract, as a result of that call, will emit a RunSQL event that contains the INSERT TABLE statement as extra data.
6- The validators will detect the new event and execute the mutating query in the corresponding table.
7- The user can query the /query?statement=... REST endpoint of the validator to execute read-queries (e.g: SELECT * FROM ...), to see the materialized result of its interaction with the SC.
💡 The description above is optimized to understand the general mechanics of the validator. Minting tables, and executing mutating statements also imply more work both at the SC and validator levels (e.g: ACL enforcing); we’re skipping them here.
The validator detects the smart contract events using an EVM node API (e.g: geth node), which can be self-hosted or served by providers (e.g: Alchemy, Infura, etc).
While network growth is not our immediate focus, we're excited about its potential in the future. If you're curious about the process, eager to contribute, or interested in experimenting, we encourage you to try running a validator. To get started, follow the step-by-step instructions provided in our validator documentation.
We appreciate your interest and welcome any questions or feedback you may have during the process. As our project evolves, we'll be shifting our focus and priorities, including network expansion in the future. Stay tuned for updates and developments.
For projects that want to use the validator API, Tableland maintains a public gateway.
You can build the validator binary from source by running: make build-api.
The repository contains in the docker folder a complete docker-compose setup to run a validator.
Soon we'll publish dedicated documentation with instructions on how to run it.
The cmd/toolkit is a CLI which contain useful commands:
gaspricebump: Bumps gas price for a stuck transactionsc: Offers smart sontract callswallet: Offers wallet utilites
Pull requests and bug reports are very welcome.
Feel free to get in touch by:
- Opening an issue.
- Joining our Discord server.
MIT AND Apache-2.0, © 2021-2022 Tableland Network Contributors