Skip to main content

Incentives to Use

🔹 Why incentivize “use” (not just holding or spending)?​

Embedding UTIL into day‑to‑day workflows turns the token into real product utility. Incentives should amplify actions that strengthen Matou’s knowledge, culture, governance, and services — not speculation.


🔹 What “use” means on Matou​

These are priority behaviours we want to reward and make easier:

  • Cultural archiving
    • Submit, digitize, tag, and maintain cultural materials with provenance and metadata
    • Verify sources, steward licenses/permissions, and keep entries up to date
  • Governance participation
    • Propose, deliberate, review, and vote (with emphasis on quality participation)
    • Maintain participation streaks and quorum reliability; contribute decision summaries
  • Contribution recording
    • Log work using Matou schemas; link proofs and outcomes
    • Merge PRs, publish modules, ship integrations, and attach attestations
  • Knowledge curation
    • Classify content, add citations, improve taxonomies, and fix broken links
  • Moderation and quality assurance
    • Triage issues, validate submissions, and resolve reports within SLAs
  • Onboarding and mentorship
    • Welcome new contributors, complete guided pathways, and mentor peers
  • Localization and accessibility
    • Translate docs, improve UX copy, and add accessibility metadata
  • Testing and reliability
    • Run test plans, report reproducible bugs, and verify fixes
  • Events and facilitation
    • Host workshops, record minutes, and publish outcomes back to the commons
  • Integrations and automations
    • Use platform APIs, set up automations, and share reusable templates

🔹 Example program designs​

  • Cultural Archive Missions
    • Earn 5 UTIL credits for verified cultrual entries with complete metadata
  • Governance Participation Program
    • Earn 50 credits for facilitating governance discussions
  • Contributor Onboarding Pathway
    • Earn 50 credits for facilitating a group onboarding session
  • Knowledge contribution
    • Earn 100 credits for submitted PR updating technical documentation

🔹 Controls and safeguards​

  • Anti‑sybil and verification
    • Identity checks, uniqueness scoring, and cross‑signal validation
  • Caps, cooldowns, and expirations
    • Per‑account caps; non‑transferable points; credits expire to prevent hoarding
  • Fairness and integrity
    • No pay‑to‑vote; boosts are small, capped, and tied to active roles
  • Privacy and consent
    • Clear data minimization; users opt‑in to public attestations
  • Abuse detection
    • Rate limits, anomaly detection, and audit trails; revoke fraudulent rewards

🔹 Integration notes​

  • On‑chain
    • Attestation registry for roles, streaks, and mission completions
    • Optional mission contracts with budget caps and per‑account limits
  • Off‑chain
    • Task queues, review workflows, and SLA timers
    • Rate limiter and feature gates read attestations to grant benefits
    • Billing applies credits/rebates at invoice or payment time

See tokenomics/util-overview, util-incentises-to-spend, util-incentives-to-hold, and util-pricing-model for related policies.


🔹 Measurement and review​

  • Active weekly users performing incentivized actions
  • Governance participation rate and quorum reliability
  • Cultural archive growth and metadata completeness
  • Conversion: use → spend; use → hold
  • Budget utilization vs. impact (credits per outcome)

Treasury sets yearly caps and reviews quarterly with public reporting.


🔹 Glossary​

  • Attestation: A verifiable, non‑transferable proof (e.g., role, streak, mission)
  • Non‑transferable points: Reward points that cannot be traded or sold
  • Mission: A time‑bound, scoped set of tasks with caps and review rules
  • Streak: A series of consecutive participation windows met (e.g., monthly votes)
  • SLA: Service‑level agreement for response or resolution time
  • Utility rewards: Credits, access, and rebates usable on Matou services