Mercle

Build portable Web3 reputation with verifiable claims for governance and rewards
Rating
Your vote:
Screenshots
1 / 2
Visit Website
mercle.xyz
Loading

Skip the theory and wire Mercle into your product in minutes. Start by turning user actions into portable signals you can trust. Install the SDK, define a claim schema (for example: made 3 swaps this week, merged a PR, verified Discord role), and map it to data sources across chains or external services. When an event matches your rules, Mercle issues a verifiable claim to the user’s wallet or DID, with optional expiry and revocation. You control whether proofs anchor on-chain or remain off-chain, and users get a single place to review, approve, and share their signals across apps.

For governance, replace guesswork with programmable participation. In your admin dashboard, compose rules like held-token-days × forum-posts × past-vote-turnout to compute weights. Gate proposal creation by minimum contributor score, give long-term participants more voting power, or enable allowlists for sensitive decisions. Tie everything to time windows (last 30 days) and decay older activity to keep influence current. Drop the policy into your voting front end, read real-time scores via the API, and let delegates showcase public claims so communities can assess credibility at a glance.

For growth and rewards, automate distribution without spreadsheets. Create a campaign, pick the claim types that qualify (completed quest, referred wallet, attended event), set budgets and per-user caps, and schedule drops. Mercle evaluates eligibility as claims arrive and triggers payouts or role assignments. Use composite rules for sybil resistance (age of wallet + on-chain volume + off-chain verification) and roll out targeted incentives by segment, like new builders with code contributions or NFT holders who completed tutorials. Export leaderboards, send webhooks to your bot or CRM, and pause or revoke rewards if inputs change.

For trust and portability, let users carry verified history between apps while keeping control. They choose which claims to disclose, hide sensitive ones, and revoke access later. You can require selective proofs for actions like borrowing, minting, or bidding—without collecting raw data. Analysts query the graph to spot top contributors, predict churn, or identify emerging leaders. Whether you’re shipping a DAO tool, marketplace, game, or lending protocol, Mercle gives you a consistent way to read reputation signals, automate decisions, and align incentives—so you spend less time on manual reviews and more time shipping.

Review summary

Features

  • Schema designer and registry for custom claim types
  • Connectors for blockchain events and external APIs
  • Verifiable claims issued to wallets or DIDs
  • Cross-app, cross-chain reputation aggregation
  • User consent, visibility controls, and revocation
  • Expiration, time decay, and versioned policies
  • Reputation scoring and rule-based automation
  • Query API, webhooks, and exportable leaderboards
  • SDKs and dashboard for no-code configuration
  • Selective disclosure and privacy-preserving checks

How It’s Used

  • DAO voting weight from sustained participation
  • Delegate discovery and contributor vetting
  • Automated airdrops, quests, and campaign rewards
  • Sybil-resistant allowlists for mints or sales
  • Risk tiers for lending or rental access
  • Referral tracking and partner program payouts
  • Game achievements and anti-bot progression gates
  • Bounty and hackathon credentialing
  • Community role assignment in chat and tooling
  • Marketplace trust badges and dispute history

Comments

User

Your vote: