# Virality Leaderboard

Lowering the barrier to creation is a necessary but insufficient condition. 

The fundamental failure of Web2 creator economies is not a lack of content, it is a lack of **verifiable attribution** and enforceable reward settlement. 

Even when fans produce high-performing content, the value chain between creation and compensation remains opaque: attribution is heuristic, payouts are discretionary, and platform intermediaries capture the majority of the surplus. 

Viral City replaces this with a fully instrumented attribution pipeline where every unit of distribution is measurable, every contribution is scored, and every reward is programmatically enforceable.

***

### Measuring Virality

The Virality Leaderboard is the system's core coordination surface. A real-time, continuously updated ranking engine that quantifies mindshare across two dimensions using a **hybrid evaluation stack** combining **AI-driven content analysis** with **verifiable on-chain and off-chain engagement signals.**

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><mark style="color:$primary;"><strong>Project Mindshare</strong></mark></td><td>Project Mindshare shows how much attention an on-chain asset captures relative to other on-chain assets in the ecosystem. </td></tr><tr><td><mark style="color:$primary;"><strong>Individual Mindshare</strong></mark></td><td>Individual Mindshare shows how much a specific creator/distributor contributed to a specific asset’s growth.</td></tr></tbody></table>

***

### Campaign Lifecycle

{% stepper %}
{% step %}

#### **Campaign Initialization & Parameter Commitment**

An on-chain asset initializes a Viral City campaign by defining campaign parameters: duration, narrative constraints, eligibility rules, and a committed reward pool locked in an escrow contract.
{% endstep %}

{% step %}

#### **Content Generation & Provenance Registration**

Users generate content through the AIGC Layer. At the point of creation, the system records full content provenance,  cryptographically binding each output to the creator's identity, the source asset, the template used, and a content fingerprint hash, establishing an immutable attribution chain.
{% endstep %}

{% step %}

#### **Continuous Mindshare Scoring & Indexing**&#x20;

The Mindshare Scoring Engine runs continuously across campaign epochs, ingesting cross-platform engagement data via an oracle layer that aggregates off-chain signals (platform API metrics, view counts, share events) and normalizes them into a unified scoring schema.&#x20;

AI-assisted evaluation modules perform content-level analysis, assessing hook effectiveness, narrative coherence, brand alignment score, and sentiment contribution, layered on top of raw engagement metrics to produce a composite mindshare score resistant to vanity-metric inflation.
{% endstep %}

{% step %}

#### **Epoch-Based Reward Settlement**

Rewards are settled programmatically at epoch boundaries based on each contributor's scored share of the asset's total mindshare delta, distributed via on-chain settlement with full auditability.
{% endstep %}
{% endstepper %}

***

### **Anti-Gaming and Sybil Resistance**

Any incentivized leaderboard is a target for adversarial manipulation. The scoring engine incorporates multi-layered Sybil resistance:&#x20;

1. Engagement signals are weighted by source credibility scoring (filtering bot-generated or farm-generated interactions),&#x20;
2. Content originality thresholds prevent low-effort duplication from accruing a meaningful score,&#x20;
3. Anomaly detection models flag statistically improbable engagement patterns (e.g., spike-and-drop view curves characteristic of purchased traffic).&#x20;

The combination of AI-evaluated content quality with verifiable engagement provenance creates a scoring surface that is significantly more robust than pure metric-count systems prevalent in existing creator reward programs.

The Virality Leaderboard comprises two core modules that operationalize this architecture:&#x20;

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><mark style="color:$primary;"><strong>Infomarket</strong></mark> </td><td>The mindshare measurement and indexing layer</td></tr><tr><td><mark style="color:$primary;"><strong>City Rewards</strong></mark></td><td>The reward distribution and settlement layer</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://city-protocol.gitbook.io/docs/attention-as-a-servcie/virality-leaderboard.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.