Relays

Relays are structured attestations submitted by verified platforms to confirm that a TRIS identity (whether an individual or an AI Agent) has performed a meaningful, score-relevant action. They are one of Tythe’s three primary inputs and serve as real-time signals for the DISC Engine.

Each Relay includes:

  • tris_id – The identity performing the action (Individual or AI Agent)

  • action_type – Type of interaction (e.g., lp_stake, doc_authored)

  • category – One or more DISC Score metric domains

  • criticality – Relative importance of the action

  • platform_id – Verified TRIS ID sender of the relay

  • timestamp – Auto-generated and immutable

All relays are:

  • Metric-tagged – Mapped to one or more DISC Score categories

  • Criticality-weighted – Assigned a quantitative importance score

  • Source-authenticated – Signed or zk-attested by the verified platform

Relays ensure that off-platform behavior becomes onchain credibility; weighted, traceable, and tamper-resistant.

Why Relays Matter

Relays offer:

  • Third-party precision: Trusted external validation of actions

  • Modularity: Custom scoring via LogicCR per ecosystem

  • Privacy by default: No identity exposure needed

They allow organizations to become trust enforcers, feeding verified data into the global trust graph without invasive data sharing.

Who Can Submit Relays?

Only vetted onchain organizations with TRIS IDs may submit decision relays.

Entity Type
Examples

Protocols

Aave, Morpho, Zora, Farcaster, Gitcoin

DAOs

Optimism, Arbitrum, Developer DAOs

Blockchains

Base, Polygon, Injective

Launchpads

Superfluid, HyperLaunch

Indexers / Verifiers

The Graph, World ID,

These platforms become active contributors to onchain credibility, feeding verified data into Tythe’s scoring engine.

AI Agents and Relays

Relays are a core input stream for AI Agents on Tythe.

They are used to:

  • Confirm agent performance across chains or APIs

  • Attribute DISC-relevant behavior (e.g., “zk_proof_validated”, “fraud_flagged”, “governance_action”)

  • Enhance or penalize their DISC Score

  • Enforce accountability tied to their Registrant

AI Agent relays are especially important since agents do not submit their own Trovebook entries. Relays become the primary vector of verifiable reputation for autonomous actors.

Metric Mapping and Criticality Weights

Each relay must:

  • Tag one or more of the seven metric categories

  • Assign a criticality score to reflect action importance

Criticality Level
Weight

Minimal

0.01

Low

0.03

Moderate

0.07

High

0.10

Critical

0.14

Platforms set these via [LogicCR] → a configuration interface that lets them define scoring logic bespoke to their ecosystem goals and priorities.

Relay Lifecycle

  1. Individual or AI Agent takes action on an integrated platform

  2. Platform submits a signed or ZK-verified relay to Tythe

  3. Relay is validated and categorized

  4. TCT is issued to the TRIS identity

For Individuals:

  • 80% → Credibility Vault

  • 20% → Validation Vault

For AI Agents:

  • 100% → Credibility Vault

  1. DISC Score updates in real time

  2. Score becomes queryable (DISC Reports, Indexes, APIs)

Examples Use Cases

Each relay strengthens the trust graph and updates the TRIS holder’s DISC Score.

Metric
Example Relay Event

🟦 Financial

  • Onchain loan repayment (Aave, Morpho, Goldfinch)

  • Staking performance verification from platforms like Lido or EigenLayer, confirming uninterrupted validator uptime or restaking fidelity.

  • Liquidity consistency attestations from automated market makers (e.g., Uniswap, Balancer) for sustained LP participation across epochs.

🟨 Creative

  • Original collection launch attestation from NFT platforms like Zora, Manifold, or Foundation confirming asset originality.

  • Protocol design or UX audit credits verified by teams such as Safe, Aragon, or design DAOs like VectorDAO.

  • Code contribution proofs verified through GitHub integrations or signed by repo maintainers in projects like Injective, Optimism, or UniswapX.

🟧 Educational

  • Course creation or facilitation logs from learning platforms like Buildspace, Alchemy University, or Gitcoin Citizens.

  • Technical documentation authorship verified by core teams (e.g., documentation on Scroll, Base, or Polygon zkEVM GitBooks).

  • Public lecture or workshop recordings verified by hosts like ETHGlobal, Devconnect, or partner DAOs.

🟩 Behavioral

  • Sustained moderation activity validated by DAOs like BanklessDAO, Farcaster communities, or Gitcoin governance groups.

  • Proposal participation logs from governance interfaces like Tally, Snapshot, or Agora, confirming consistency and constructive input.

  • Delegation history demonstrating credible stewardship, validated by delegate rating systems such as Karma Protocol.

🟥 Security

  • Validator uptime and slashing immunity attested by node operation platforms such as Ssv.network or P2P.org.

  • Bounty completion and reward claims verified by platforms like Immunefi, Sherlock, or Code4rena.

  • Audit report co-authorship credited by auditing firms (e.g., Trail of Bits, Halborn, OpenZeppelin).

🟪 Compliance

  • zk-KYC or jurisdictional access attestation issued via zk-compliant ID rails like Quadrata, Fractal ID, or Gitcoin Passport. Standard KYC applications for centralized exchanges and DeFi protocols.

  • Cross-border activity declarations verified by ecosystem-compliant platforms (e.g., Circle, Anchorage, Maple).

  • Policy adherence attestations from protocols enforcing anti-manipulation or disclosure guidelines (e.g., Gnosis Safe, Opyn, or dYdX).

Note: 🟫 Social (Metric Exclusion)

Decision Relays are not used to compute the Social metric. Instead, social credibility is derived directly from self-verified identity proofs (e.g., X, GitHub, Lens, Farcaster) using Reclaim Protocol’s zkTLS module from Tythe's dashboard itself. This ensures user-controlled, revocable, and privacy-preserving validation of social presence.

Relay Restrictions

  • Only platforms with vetted TRIS IDs can submit

  • Relays must conform to predefined logic via [LogicCR]

  • Each submission is timestamped, validated, and stored

  • Sensitive relays can be zk-hashed and later proven

Tythe does not accept relays from anonymous or unverified sources.

Auditability and Transparency

All validated relays are:

  • Cryptographically signed or zk-validated

  • Time-stamped and immutable

  • Publicly queryable via:

    • The TRIS Profile

    • DISC Reports

    • Tythe APIs

They provide a machine-readable, zero-trust source of verifiable behavioral data.


“I the Lord search the heart and examine the mind, to reward each person according to their conduct, according to what their deeds deserve.”

— Jeremiah 17:10

Last updated