Improve Kleros integration
We currently use a hardcoded list of tokens from Kleros TCR which is embedded with our distribution.
While it is a good solution to prevent tampering of data, that also means the list will get outdated if it is not actively updated.
Some ideas (and we can unfold it into more specific issues):
ref: https://docs.kleros.io/integrations/types-of-integrations/2.-curated-data-integration-plan
- Provide some option for the user to get fresh data directly from the kleros subgraph.
- Explore using their address tags registry (it needs our infra-structure for generic address tagging done first)
- Add other networks than mainnet (when I first added it I was only worried about mainnet, also it only had mainnet).
Hi @wmitsuda, this is Guangmian from Kleros and we are keen to revisit this integration! Our decentralized data product has since been rebranded as Kleros Scout and is used by Etherscan, Ledger and also Metamask through their Metamask Snaps framework. Keen to know what's the best way for us to contribute data, either through batch exports or through an integration with our subgraphs for real-time retrieval of metadata.
let's use this issue as a parent to track/link all Kleros Scout-related contributions.