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. Why Polygon

ZK-Native Architecture

Tythe is built on privacy, proof, and permanence. At its core are mechanisms like:

• ZK-KYH (Know Your Human)

• ZK-KYB (Know Your Business)

• Trovebook (ZK-proof storage)

• DISC Scoring without identity exposure

All of these require a network that can process, verify, and anchor zero-knowledge proofs efficiently and reliably.

Polygon’s zkEVM isn’t just compatible with this architecture — it’s essential to it.

Why zkEVM Matters for Tythe

• ZK-native compatibility

 → Scoring logic enforcement, KYH/KYB, and validation flows are all built on ZK-based structures.

• Ethereum-equivalence

 → Developers can use existing smart contract libraries to verify proofs with no compromises.

• On-chain proof anchoring

 → Trovebook, decision relays, and TRIS metadata need permanent, verifiable hash commitments.

• Future composability

 → Tythe’s components will integrate with other ZK systems — requiring native ZK infrastructure at the base layer.

Without zkEVM support, Tythe’s architecture becomes theoretical.

With Polygon, it becomes inevitable.


“It is the glory of God to conceal a matter; to search out a matter is the glory of kings.”

— Proverbs 25:2

PreviousWhy PolygonNextUncompromising Scalability

Last updated 6 days ago