- Thank you for offering to help out with this Kleros initiative!
- The Ledger registry is meant to create a crowd-sourced registry of contract-to-domain mappings that allow wallets like Ledger to verify that frontends/DNSes have not yet been compromised.
- We are bootstrapping this process with the Kleros team and community contributors in the beginning to achieve a high number of entries in the shortest amount of time.
- The contributors will work closely with the Kleros Cooperative members to populate the registries in question, communicating through Slack, Telegram, Discord or calls when necessary.
Recommended steps for creating an entry:
- Kleros Cooperative set out the list of projects to focus on (i.e. high impact projects), and these projects can be found here. The ones that are meant for contributors like yourselves have assignee = ‘For Contributors’.
- For each project:
- Check which contracts are being interacted with through their primary (sub)domain, and look for primary sources of information documenting them.
- Once the addresses are found, gather and verify the data needed and ensure the submissions (both individual fields and JSON fields) are compliant with the guidelines in the registries here.
- Additionally you will also need to:
- Check that addresses for Ethereum are formatted in lower case for consistency.
- Cover all the addresses that can be interacted through the most used (sub)domain of the dApp in question. This ensures that the entry is actually useful for users/wallet providers.
- Double-check for duplicates in the file (some projects list the same address twice for different purposes and directly copying it could lead to duplicates).
- Some projects can have many different spellings for their name, and we need the exact official capitalisation and spelling (e.g. ‘LooksRare’ vs ‘Looks Rare’ vs ‘LOOKSRARE’?). If in doubt, Coinmarketcap is a good point of reference.
- Cite the Github commit hash (if not, the date of access) of the file/page you are referencing in the ‘Additional Information field’.
- These categories of addresses can be omitted for now (just note down their existence in the sheet):
- Token contracts of tokens that are not from the project itself (e.g. USDC contract on app.uniswap.org). Do mention which ones these are so I can push them to tokens.kleros.io
- Factory-created contracts (e.g. LP contracts) which are accessed through a router on the frontend. Do make a note so that we can come back to them when we set up a registry for subgraph queries+endpoints.
- Once you have verified all the information, upload the JSON file to here (feel free to make your own folder), and fill in the fields in the spreadsheet above.
- A video of how I deal with one batch of addresses can be found here (using free and easy tools):
- To thank you for the work, we will be putting out a reward/bounty of $300 for 20 submissions, and a retainer of $250 for completing minimum 2 batches of 20 submissions (i.e. 40 per retainer).
- To qualify for the retainer, no more than two submissions per month should contain data that would qualify the entry for rejection (i.e. loss of deposit for Kleros) - this penalty will be waived for the first month.