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. DISC (For Individuals)
  2. Output
  3. Score Logic

Pre-Protocol Logic

PreviousScore LogicNextPost-Protocol Logic

Last updated 19 hours ago

Before Tythe launched, the DISC Engine did not exist — meaning no platforms could submit live decision relays, and no on-chain scoring logic could be enforced in real time.

To ensure early adopters, contributors, and builders are recognized fairly, Tythe uses a separate trust path known as Pre-Protocol Logic.

What It Covers

Pre-Protocol Logic applies only to Contributions (Impact Weighted) — not Actions. To understand the distinction, refer to the [ → Contributions vs. Actions].

No behaviors or transient platform activity are counted retroactively. Instead, Tythe recognizes verifiable contributions made before protocol launch. These are categorized into two types:

1. On-Chain Contributions

These are inherently verifiable through public blockchain data, smart contract interaction, or cryptographic proofs.

Examples:

• Open-source code commits linked to verified repos

• DAO governance activity (e.g., votes, proposals)

• On-chain protocol contributions (e.g., liquidity provision, validator activity)

• NFT, token, or smart contract deployment tied to a known wallet

Verification Path:

• Auto-validated via wallet-linked on-chain activity

• Proofs submitted through Trovebook (ZK-hashed with wallet binding)

• Cross-validated against public ledger data

On-chain contributions are automatically scoped to the correct wallet and can only be claimed by a TRIS with ownership over that wallet address.

2. Off-Chain Contributions

These require supplemental verification to prove origin and authenticity. They may include public or third-party contributions made outside the chain.

Examples:

• Technical documentation or research

• Community leadership and ecosystem education

• Grant participation or public dev bounties

• Pre-launch advocacy or social influence

Verification Path:

To prevent fraud or duplication, Tythe enforces strict validation layers for off-chain submissions:

1. Reclaim Protocol Verification (X + GitHub)

→ Users can prove they own their off-chain identities using zkTLS via Reclaim

→ Allows validation of content ownership and contribution origin

→ TRIS metadata will display linked social accounts when verified

2. Trovebook ZK Proofs

→ Users submit hashed claims of off-chain work (e.g., .pdf, blog, contribution logs)

→ Hashes are detached from wallet/username at generation, and linked only after

3. Third-Party Attestations

→ DAOs, protocols, or partners may sign attestations confirming a user’s contribution

→ Only one TRIS may be rewarded per verified instance

4. Manual Review (For Edge Cases)

→ When automated proof is not possible, users may submit off-chain claims for review

→ Tythe reviewers evaluate for impact, proof quality, and originality

→ Only high-effort, meaningful submissions are approved

Contribution Reuse Prevention

• Every off-chain contribution hash is indexed and deduplicated via nullifier logic

• Once a hash is linked to a TRIS, it cannot be resubmitted or claimed by another

• Wallet overlap detection prevents multi-TRIS reuse by the same person

• Group contributions are accepted only when multiple independently verified TRIS IDs qualify for shared credit

Impact on DISC Score

• Validated Pre-Protocol contributions grant a one-time DISC Score boost during onboarding

• This boost applies only to the Credibility Vault (never the Validation Vault)

• Boosts are non-recurring, capped, and permanently tied to the claiming TRIS

• Tythe scores the impact — not the volume — of each submission

Key Principles

• Proof over claims — Verifiability is required

• Contributions, not actions — No retroactive platform behavior

• No inflation — All scoring is capped and audited

• Tamper-resistance — One contribution, one TRIS, once

Who It Benefits

Pre-Protocol Logic rewards early contributors who created real value before Tythe’s launch:

• Builders, engineers, and designers

• DAO governors and researchers

• Content educators and public evangelists

• Legitimate ecosystem pioneers

Tythe doesn’t reset the clock at launch. It captures the weight of what’s been built — and proves it before rewarding it.


“God is not unjust; he will not forget your work and the love you have shown him as you have helped his people and continue to help them.”

— Hebrews 6:10

Logic page