In most governance mechanisms, KYC is not needed.

Since these applications are specialized (say smartpushti ) , the users who receive rewards have already demonstrated expertise.

Only users who receive rewards through conviction voting can issue beta reputation.

How do we validate a Nostr public key? Include the public key as evidence.

What is the purpose of beta reputation? What responsibilities do users with high beta reputation have?

For example, in SmartPushti there are buyers and sellers. Who decides which sellers are trustworthy?

The answer is the workers who have earned rewards through conviction voting.

If you use Bayesian beta reputation (where trust is continuously updated as more evidence arrives), then users with high beta reputation should have greater responsibility, not just greater influence. Their reputation should be earned through consistently accurate judgments.

A good principle is:

Beta reputation measures the reliability of a person's evaluations, not their popularity or authority.

Responsibilities of users with high beta reputation could include:

  1. 1.

    Evaluate new contributors

    • Review work submitted by newcomers.

    • Give endorsements only when the work meets community standards.

  2. 2.

    Certify quality

    • Verify that code, articles, recipes, designs, or research are genuine and useful.

    • Their endorsements become evidence for future governance decisions.

  3. 3.

    Detect fraud and spam

    • Flag plagiarism, fake accounts, low-quality submissions, or malicious behavior.

    • Incorrect or abusive judgments should reduce their own reputation.

  4. 4.

    Guide reward distribution

    • Their evaluations can provide input to conviction voting or funding decisions.

    • They do not decide alone; they contribute weighted evidence.

  5. 5.

    Mentor newcomers

    • Help new participants improve their work.

    • Endorsements become more meaningful when combined with mentorship.

  6. 6.

    Resolve disputes

    • Participate in reviewing appeals or conflicting evaluations.

    • Multiple high-reputation reviewers reduce the chance of bias.

  7. 7.

    Maintain category-specific expertise

    • Reputation should be domain-specific.

    • Someone trusted for software development should not automatically influence food quality or economics.

In SmartPushti

Workers who receive rewards through conviction voting become eligible to issue beta reputation.

Their responsibilities include:

  • Verifying sellers' reliability.

  • Reviewing recipe quality.

  • Detecting copied or AI-generated spam recipes.

  • Confirming that deliveries and transactions are legitimate.

  • Helping new sellers build trust.

  • Reporting malicious behavior.

A seller endorsed by many accurate evaluators gains trust much faster than one endorsed by random users.

https://iambrainstorming.github.io/chapters/computer/algorithm/bayes-reputation.html