# ShillOS

ShillOS is Laika’s on-chain distribution layer.

It turns creator outreach into *programmable campaigns* — with briefs, escrowed budgets, proof-of-publication, and automatic payouts — so projects fund verifiable distribution instead of informal DMs.

***

### What ShillOS solves

* **Off-chain promises →** on-chain agreements (brief → escrow → publish → payout).
* **Opaque spend →** auditable budgets, addresses, and results.
* **One-off influencers →** repeatable creator cohorts with reputation and cost metrics.
* **Unpaid work / ghosting →** proof-based payouts and optional clawbacks.

***

### How it works (end-to-end)

1. <mark style="color:yellow;">**Create a brief**</mark>
   * Project/DAO defines the deliverable (e.g., thread, meme, video, Space co-host, TG post), target timing, required tags/links, and acceptance criteria.
2. <mark style="color:yellow;">**Escrow the budget**</mark>
   * Funds are locked in a campaign contract ($LAIKA, $DOGE, USDC, or project token).
3. <mark style="color:yellow;">**Creator opt-in**</mark>
   * Verified creators (wallet + socials) review the brief and accept the terms (rate card or tiered bounty).
4. <mark style="color:yellow;">**Publish & verify**</mark>
   * Creator posts the content; ShillOS records the post ID, URL and a content hash.
   * An on-chain oracle verifies proof-of-publication and basic criteria (tags, link, handle, time window).
   * Optional performance tiers (e.g., ≥X views/likes) unlock bonuses.
5. <mark style="color:yellow;">**Payout & reputation**</mark>
   * Smart contract releases the payout automatically when conditions are met.
   * Creator’s reputation score updates (completion rate, dispute rate, repeat funding).<br>

> Everything is visible in dashboards: who was paid, for what, when, and under which brief.

***

### Campaign types (presets)

* **X Thread / Tweet** – long/short form; mandatory tag & link; media required (Y/N).
* **Meme / Creative** – image/GIF/video; source file upload; brand kit adherence.
* **Space / AMA** – date/time window; co-host handle; recording link post-event.
* **Telegram Push** – channel post + forward count; pinned duration.
* **Quest Pack** – multi-action flow (follow, RT, join Discord, apply OG List) with per-action payouts.

Each preset maps to a pre-audited acceptance checklist and payout schema.

***

### Payout models

* **Fixed bounty** — pay on proof-of-publication.
* **Tiered performance** — base + bonuses unlocked by view/engagement thresholds.
* **Streamed** — payout streams over N days; clawback if content is deleted early.
* **Vested** — part paid now, part vested (aligns long-term advocacy).

Defaults are set per brief; projects can combine models (e.g., fixed + bonus).

***

### Verification & fraud controls

* **Read-only social linking (X/TG):** collects handle, avatar, follower count; no posting permission required.
* **Deterministic checks:** handle match, mandatory tags/mentions, canonical link, time window, content hash.
* **Gates (tunable):** minimum account age, follower threshold, prior completion rate.
* **Duplicate & plagiarism filters:** hash similarity and URL de-duplication.
* **Appeals:** short window to contest failed checks (manual reviewer or dispute module).

***

### Creator onboarding

* Connect wallet → link socials (read-only).
* Set rate card (flat, tiered, token-denominated ok) and preferred categories.
* Build reputation via completed campaigns; higher scores surface first for briefs.

***

### Default parameters (governance-tunable)

* **Content permanence:** must remain online ≥ 7 days (clawback if removed).
* **Grace periods:** publish within 48–72h of acceptance unless otherwise stated.
* **Appeal window:** 48h post-rejection.
* **Creator caps:** max concurrent campaigns per creator to prevent spam.
* **Budget assets:** $LAIKA, $DOGE, USDC, or project token; treasury routes set by DAO policy.
* **Disclosure:** compliance toggle for ad/sponsored tags where required.<br>

Active defaults are shown in-app; changes require governance.

***

### Roles & responsibilities

* **Projects/DAOs** — fund briefs, define targets, review dashboards, iterate budget mix (creators vs bribes vs buybacks).
* **Creators/KOLs** — deliver on brief, maintain content, grow reputation for better access.
* **Oracles/Reviewers** — verify proofs; adjudicate disputes within SLA.
* **veLAIKA voters** — may subsidize ecosystem-wide campaigns (meta-distribution) via governance.

***

### Safety & compliance (plain language)

* Laika/ShillOS never obtain posting rights to social accounts; permissions are read-only.
* Payouts depend on meeting objective criteria in the brief; not financial advice or performance guarantees.
* Creators are responsible for platform ToS compliance and legal disclosures in their jurisdiction.
* Campaign funds in escrow are programmatically released; unused budgets can be returned by the brief owner.

***

<mark style="color:yellow;">**TL;DR**</mark>

ShillOS makes distribution trustless, measurable, and repeatable. Projects fund *proof-backed* reach; creators become on-chain partners with reputation; DAOs see exactly what they paid for — and can double-down where it works.


---

# 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://litepaper.laikachain.dog/core-modules/quickstart-3.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.