go-tableland
go-tableland copied to clipboard
tablelandnetwork
Go implementation of the Tableland database/validator - run your own node, handling on-chain events and serving read-queries
null [GOT-42](https://linear.app/tableland/issue/GOT-42/expose-api-endpoint-to-get-a-proof-that-a-row-is-in-a-table)
Validator can update the tree at some regular internal which matches the interval that the root is posted on chain. [GOT-41](https://linear.app/tableland/issue/GOT-41/maintain-at-some-interval-a-tree-of-all-tables-where-each-table-is)
We need to scope how backward-compatible protocol upgrades would work: - In the validator. - The spec should now start explaining which feature lives in which network version. - Include...
This is capturing an idea that I had a while ago. Currently, [we store all the read-query results in memory](https://github.com/tablelandnetwork/go-tableland/blob/dbac14cbd83655b3f2681083742d8933c09acb2c/pkg/sqlstore/store_user.go#L12) and do the right formating after. That might be comfortable...
The current `config.json` [validation configuration file](https://github.com/tablelandnetwork/go-tableland/blob/main/docker/deployed/testnet/api/config.json) looks reasonable, but I believe it has some problems. In the same configuration file, we have two big groups of configurations: - Protocol level...
Metadata
Owner
Metadata
Go implementation of the Tableland database/validator - run your own node, handling on-chain events and serving read-queries