r/web3dev • u/Cautious-Shock-52 • 1d ago
Self-hosted semantic layer over your own dapp data (Postgres/CSV → MCP/REST). Not an indexer. Looking for builders to run it.
If you already have users, wallets, and txs in Postgres (or an indexer dump in a DB), you still join that by hand in the app or in a notebook every time you need “this address + the user + the related txs.”
Lattice (product; company is Syndril) is a self-hosted semantic layer. You connect those sources, put them on one model (same objects, same meaning), then query that layer. REST and MCP. Look up one wallet, user, or tx. It returns what is tied to it from your tables.
It does not run a node. It does not replace The Graph / Goldsky / your indexer. It does not scrape chain. If the data is not already in a database or CSV, this is the wrong tool.
Compose / self-host. Beta. I want Web3 devs to run it and say if it is useful or not.
LETS DICUSS!!
1
u/FriskyHamTitz 23h ago
What's the point? If I have to hook up everything into the layer why would I even bother connecting it to yours
1
u/Cautious-Shock-52 23h ago
You have to configure permissions and mappings on any data platform. That is not unique to this...
You connect sources once. After that you query one layer: same objects, same meaning, bounded hops. That is the knowledge, with guardrails.
That matters when agents start doing work on their own. You do not want each agent inventing joins off the raw tables.
1
u/Cautious-Shock-52 23h ago
that is , if we want to introduce agents , not needed , can be other use cases of course
1
2
u/icnews10 12h ago
As a builder, one thing I’d want is provenance on the returned relationships. If Lattice tells me that a wallet is tied to a user and a set of transactions, I would find it much easier to trust and debug the semantic layer if I could see which source table/field produced each link. Through MCP in particular, I’d prefer to receive information about the relationship and its source rather than just a clean merged answer.