LogoLogo
  • Welcome to Tythe
  • Terminology
  • Protocol Overview
  • Onboarding
    • For Individuals
      • For Users
      • For Builders
    • For Organizations
      • For On-Chain
      • For Off-Chain
  • DISC (For Individuals)
    • Engine
    • Inputs
      • TRIS
        • Wallet-Agnosticism
        • Chain-Agnosticism
      • Trovebook
      • TDT Framework
        • TCT (TruCred Token)
          • Dual Vaults
          • Credonate
        • TYT (Tythe Token)
    • Output
      • Score Metrics
        • Financial
        • Creative
        • Educational
        • Behavioral
        • Social
        • Security
        • Compliance
      • Score Logic
        • Pre-Protocol Logic
        • Post-Protocol Logic
      • Score Rating
      • Score Utility
  • DISC (For Organization)
    • Organization Vetting
    • DISC Ranks
  • Credibility Enforcement
    • BAD Status
    • Credonate Rules
    • Indexes
      • Cred List
      • Cred Watch
      • Cred Chain
    • TCT Staking
  • Governance
    • Voting Power Model
    • Proposal Lifecycle
    • Governance Scope
  • Integration Resources
    • Quickstart Guide
    • API References
    • Example Implementation Flows
    • SDK Library (Coming Soon)
    • Sandboxes (Coming Soon)
    • Use Cases
  • Why Polygon
    • ZK-Native Architecture
    • Uncompromising Scalability
    • Infrastructure Maturity
    • Shared Ethos
    • Ecosystem Synergy
  • Legal
    • Terms of Service
    • Privacy Policy
  • FAQs
Powered by GitBook
On this page
Export as PDF
  1. Credibility Enforcement

Credonate Rules

Tythe’s Credonation system enables users to validate the credibility of others by spending their own TCT. However, to prevent reputation inflation and gaming, Credonations are governed by strict rules — enforced at the protocol level.

This page defines what types of Credonations are allowed, what restrictions apply, and how proximity between identities shapes trust flow.

Credonation Matrix

Donor
Recipient
Allowed
Rule Type

Individual

Individual

✅

Proximity-Based

Individual

Organization

✅

No Restriction

Organization

Organization

✅

No Restriction

Organization

Individual

❌

Blocked (Not Permitted)

Individual → Individual

Credonations between individual TRIS identities are allowed, but subject to proximity rules based on DISC Score rating bands as follows:

Your Rating
You Can Credonate To
You Can Be Credonated By

Poor

Anyone

Poor, Fair

Fair

Anyone

Poor, Fair, Good

Good

Fair and above

Poor, Fair, Good, Very Good

Very Good

Good and above

Anyone

Excellent

Very Good and Excellent

Anyone

Users can always decline Credonations from others, and proximity rules are enforced automatically at the protocol level.

Individual → Organization

Credonations from individuals to verified organizations are allowed with no proximity restriction.

This enables community-driven reputation flows:

• DAO contributors validating platforms

• Users endorsing toolkits, L1s/L2s, or governance bodies

• Independent builders supporting credible initiatives

These Credonations strengthen an organization’s DISC Rank over time, increasing its reputation standing and public perception.

Organization → Organization

Organizations may freely Credonate to other organizations.

There are no restrictions on peer-org validation.

This enables:

• Trust signaling between DAOs

• Partnership validation

• Mutual support in public grant ecosystems

• Decentralized ecosystem mapping

Organizational Credonations affect DISC Rank only, and are stored as validation metadata on both TRIS profiles.

Organization → Individual

Credonations from organizations to individual TRIS IDs are not permitted.

This restriction exists to:

• Prevent reputation laundering from institutions to sockpuppet users

• Avoid inflation of DISC Scores through biased org-originated endorsements

• Maintain the peer-based trust layer of individual credibility

Attempted Org → Individual Credonations will be automatically rejected at the protocol level. No TCT will be transferred or deducted.

Declining a Credonation

All TRIS IDs — individual or organizational — retain the right to decline an incoming Credonation. All users can manually decline Credonations or configure inbound filters to automatically block unwanted validations.

• Declined Credonations are reversed

• No metadata is recorded

• The sender’s Validation Vault is fully refunded

This provides reputational control for both sides while keeping the trust signal opt-in and clean.


“Better is the poor who walks in integrity than one who is crooked in speech and is a fool.”

— Proverbs 19:1

PreviousBAD StatusNextIndexes

Last updated 5 days ago