Pre-Protocol Logic

Before Tythe launched, the DISC Engine did not exist, and therefore, no real-time relays, platform integrations, or metric-based scoring could be enforced.

To ensure early contributors are recognized without compromising score integrity, Tythe applies a separate logic track for pre-launch credibility: one that scores verifiable contributions.

What Counts in Pre-Protocol?

Pre-Protocol inputs are impact-weighted contributions (not actions).

These are one-time score-seeding events, and must be provably real.

Contribution Type
Examples

Onchain Contributions

DAO proposals, validator history, NFT mints, governance votes, LP staking

Offchain Contributions

Docs, research, education, advocacy, public goods, community leadership

  • No airdrop farming

  • No self-claimed hype

Only proof-backed, ecosystem-recognized contributions

Validation Methods

To qualify for scoring, submissions must be proven using at least one of the following:

  • Trovebook Proofs (Individuals only)

    ZK-hashed content submitted to the user’s Trovebook and linked to their TRIS

  • Third-Party Attestations

    Submitted by DAOs, protocols, or ecosystem validators

  • Reclaim Protocol

    Verifies offchain account ownership (e.g., GitHub, X) using zkTLS

  • Manual Review

    Reserved for high-value edge cases with no automated proof path

  • Platform-Relayed Submissions (Individuals only)

    Vetted platforms may submit verified Pre-Protocol contributions via Decision Relays, provided:

    • The user’s TRIS is referenced

    • The contribution occurred before launch

    • The relay is properly tagged and signed

Contribution Rules

Rule
Description

One-Time Submission

Pre-Protocol inputs can only be scored once

Non-Repeatable

Duplicate or similar entries are rejected

Time-Bound

Must clearly pre-date Tythe’s public launch

Impact-Weighted

Contributions are scored based on reach, difficulty, impact, and trust context

Identity-Locked

Contributions must be bound to the TRIS ID holder (and attested by 3rd party validators)

Scoring Outcome

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

  • TCT is allocated to the Credibility Vault only

  • Scoring is non-recurring, permanently recorded, and non-transferable

  • Impact (not volume) determines weight

Tythe doesn’t erase history; it elevates it, if and when proven.

Why AI Agents Are Ineligible

AI Agents are fully excluded from Pre-Protocol Logic for structural and trust-layer reasons:

  • They did not exist prior to launch

    zk-KYA was not available; no agent identity could have credibly predated the system

  • They lack offchain proof provenance

    Pre-Protocol scoring requires human-originated data (GitHub commits, public threads, Reclaim-verified ownership) — all inaccessible to agents

  • Their credibility is strictly post-onboarding

    Agent trust is derived from sponsor stake, live performance, and Decision Relays

Allowing AI Agents to claim pre-launch credibility would:

  • Break identity anchoring

  • Introduce Sybil vectors

  • Dilute the value of earned, early human trust

Only verified Individuals may submit or receive Pre-Protocol scoring.

All AI Agent credibility begins at protocol activation, via Post-Protocol Logic, Relays, and TCT-backed Sponsorships.

Any earlier validations or endorsements may still be surfaced via sponsorship metadata but never converted into Pre-Protocol DISC.


“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

Last updated