Kleros
Kleros.ioGithub
  • Introduction to Kleros
  • Kleros FAQ
  • Governance
  • PNK Token
  • They talk about Kleros
  • Products
    • Court
      • Kleros Juror Tutorial
      • Famous Kleros Cases
      • What happens during a dispute?
      • Kleros & Credible Neutrality
    • Court V2
    • Proof of Humanity
      • Proof of Humanity 2.0 Tutorial: (Register & Vouch)
      • Proof of Humanity 2.0 Tutorial (Remove & Challenge)
      • Proof of Humanity 2.0 Tutorial (Transferring a Profile)
      • Proof of Humanity 2.0 Integration Guide
      • Proof of Humanity FAQ
        • Proof of Humanity 2.0 launch FAQ
    • Curate
      • Kleros Curate Tutorial
      • Kleros Scout
        • Tutorial
        • Earn With Kleros Scout
        • Partnerships
        • Kleros Scout - Metamask Snaps
          • Knowledge Base
        • FAQs
    • Oracle
    • Governor
    • Escrow
      • Kleros Escrow Tutorial
      • Kleros Escrow Specifications
    • Linguo
      • Kleros Linguo Tutorial
      • Step-by-step Tutorial
        • Requesting translations
        • Working as a translator
        • Reviewing translations
      • F.A.Q
      • High-level Overview
    • Moderate
      • Susie
        • Getting Started
          • Add Susie
          • Start Susie
        • Basics
          • Welcome
          • Language
          • Notifications
        • Rules
        • Reports
        • Evidence
        • Federations
  • INTEGRATIONS
    • Overview
    • Industry use cases
    • Types of Integrations
      • 1. Dispute resolution integration plan
        • Smart contract integration with Kleros Court (Arbitrator)
        • Use Cases
          • DeFi Insurance
          • Gaming
          • Recognition of Jurisdiction Integration
            • Integración por Reconocimiento de Jurisdicción
        • Channel partners
          • How to use Reality.eth + Kleros as an oracle
          • Safe Zodiac integration
          • Kleros Reality Module
        • Integration Tools
          • Centralized Arbitrator
          • Dispute Resolver
      • 2. Curated-data integration plan
        • Retrieving information from Kleros Dapps
    • Policy writing guide
    • Live & Upcoming Integrations
    • Kleros Analytics
    • Scalability & Cross-chain
      • Using Kleros arbitration for Dapps on xDai/Gnosis
    • Integrations FAQ
  • Developers
    • Arbitration Development
      • ERC-792: Arbitration Standard
      • ERC 1497: Evidence Standard
      • Arbitrable Proxy
    • Arbitration by Example
      • ArbitrableDeposit.sol
      • TwoPartyArbitrable.sol
      • Rental.sol
      • ArbitrableTransaction.sol
      • MultipleArbitrableTransaction.sol
      • MultipleArbitrableTokenTransaction.sol
    • Deployment Addresses
    • Curate Classic: Integration for Devs
    • Light Curate: Integration for Devs
    • Guide for Preparing Transactions
  • Contribution Guidelines
    • Overview
    • General Dev. Workflow
      • Task Tracking & Lifecycle
      • Releases
    • Smart Contract Workflow
      • Task Tracking & Lifecycle
      • RAB - Review, Audit, Bounty
      • RABd (+ Deploy)
      • Reporting Vulnerabilities
    • Code Style and Guidelines
      • Git
      • Solidity
      • Web Languages
    • License & Code of Conduct
      • License
      • Code of Conduct
  • Additional Resources
    • Discord
    • Telegram
    • Governance Forum
    • Twitter
    • Blog
    • Reddit
    • Github
    • Slack
Powered by GitBook
On this page
  • How is the data for providing contract information via the Kleros Scout Snap curated?
  • Who submits and decides if an entry stays on the list?
  • What is the need for a credibly neutral, community sourced contract information data source?
  • I’m seeing that some of my contract interactions don’t have any insights. Can I make submissions to the Kleros security metadata registries?
  • Why will I take on the risk of interacting with an unknown contract and submit an entry to the Kleros registries?

Was this helpful?

Edit on GitHub
  1. Products
  2. Curate
  3. Kleros Scout
  4. Kleros Scout - Metamask Snaps

Knowledge Base

Guide for addressing common questions from users during the course of using the Kleros Scout Snap.

PreviousKleros Scout - Metamask SnapsNextFAQs

Last updated 3 months ago

Was this helpful?

How is the data for providing contract information via the Kleros Scout Snap curated?

Kleros Curate is a decentralized dApp that can be used to create open curated registries of just about anything using financial incentives and Kleros dispute resolution technology to ensure a list stays on topic and that each entry is compliant to the predefined acceptance criteria.

For the Kleros Scout Snap, we are focused on contract insights data (security data) to secure dApp interactions.

Who submits and decides if an entry stays on the list?

When a user (anybody can make a submission as long as they can put up a deposit along with it) submits an item to Curate, it is first vetted by a challenge period which allows anyone else to challenge that submission (anybody from the community who can put up a competing deposit is a challenger). If the submission isn’t challenged within this period of time, it’s deemed legitimate and on topic, if it is, the challenged submission is sent to Kleros jurors to decide whether it is, or isn’t valid for the list in question.

What is the need for a credibly neutral, community sourced contract information data source?

There is an inherent vested interest for centralised parties to whitelist new tokens for example, in order to make a profit through the volume/liquidity increase in the market for that token due to the listing. This has happened in the past with several CEXs. Similar issues plague centralised address tagging and contract to domain mappings (phishing attacks, front-end DNS attacks, etc.)

The need for decentralised, community sourced and secured security metadata can’t be overstated.

I’m seeing that some of my contract interactions don’t have any insights. Can I make submissions to the Kleros security metadata registries?

Absolutely! We encourage the community to submit and police submissions to move towards a scaled, highly secure, community driven data source which can empower safe dApp interactions.

Why will I take on the risk of interacting with an unknown contract and submit an entry to the Kleros registries?

There are two important reasons for this:

  • 👫 Altruism: There is little to no risk involved with making a submission to the registries of a contract you have previously interacted with, which you know is safe. You are enabling thousands, if not more people to have peaceful, anxiety free contract interactions.

💰 Kleros’ Incentives Programs: To encourage community submissions to scale and cover the long-tail of security data on the registries, Kleros regularly runs incentives programs. We have seen regular submitters win hundreds of $$ by simply helping secure the community’s dApp interactions.

Here are step-by-step guides to make submissions to the 3 security metadata registries.
You can see information about the latest incentives program here.