BAD Status

Tythe’s BAD Status system is the protocol’s trust deterrent layer — a zero-tolerance enforcement mechanism for users or organizations who violate the terms of credibility.

While most of the DISC system is designed to reward merit and behavior, BAD Status is reserved for violations, not low credibility. It is not a score band — it is an active flag with enforced consequences.

What Triggers a BAD Status?

A TRIS may receive a BAD Status if it has:

• Attempted identity manipulation or Sybil behavior

• Participated in fraudulent activity, governance tampering, or exploit abuse

• Failed ZK-KYH or ZK-KYB re-verification after system request

• Been linked to credibility laundering (multi-wallet reroll attempts)

• Repeated moderation violations or cross-protocol flagging

BAD Status is not subjective. It is issued based on proof, flagged by:

• Tythe’s protocol logic

• Trusted platforms and verifiers

• Aggregated moderation signals from integrated partners

DISC Score Suppression (1–6)

Once assigned a BAD Status, a TRIS’s DISC Score is no longer based on TCT accumulation. Instead, it is overridden and locked within a 1–6 range based on the severity of the violation:

DISC Score 1–6 — BAD Status Mapping
6 – Minor Violation (e.g. spam, minor policy breach)
5 – Repeated low-severity offenses or manipulation attempt
4 – Proven Sybil attempt or false identity claims
3 – Exploit abuse or multi-wallet manipulation
2 – Severe fraud, governance tampering, systemic harm
1 – Protocol blacklisted: irredeemable, irreversible status

This status is visible on-chain and through any TRIS query.

It cannot be self-cleared or appealed unless the protocol explicitly supports decay or remediation for that violation type.

Key Enforcement Rules

• Credonation is disabled for and from BAD TRIS IDs

• Recognition Index visibility (Cred List) is revoked

• Credibility Vaults are frozen; TCT is not burned but no longer contributes to DISC

• Project access and governance participation are suspended

• Attempted re-rolls will automatically inherit the BAD flag if linked

Why This Exists

In trustless systems, credibility is valuable — and anything valuable can be gamed. BAD Status exists to:

• Prevent credibility laundering

• Penalize malicious behavior

• Ensure reputation permanence

• Maintain the integrity of credibility-based access control

This is not a slashing mechanism. It is reputation quarantine.

You don’t just lose credibility in Tythe. You lose the ability to pretend you ever had it.

---

“The way of the treacherous is their ruin.”

— Proverbs 11:3