Technical Abstract
Lioth Protocol is a decentralized system for distributing structured tasks to humans, verifying outputs through a declared verification workflow, and delivering finalized results through a unified execution + verification + distribution pipeline. Lioth is designed for environments where provenance and quality assurance matter under adversarial incentives (low-effort work, automation, and AI-assisted submissions), and where participants may require privacy by default. Lioth produces two primary output types:
-
Human Verified Outputs (HVO): finalized task results delivered directly to a requester (e.g. microtasks, evaluations, reviews, extraction, research, QA, preference testing).
-
Human Verified Data (HVD): when tasks are designed for aggregation and reuse, validated outputs can be packaged into standardized dataset artifacts with quality reporting, source hashes, and licensing references.
Verification in Lioth is expressed as Proof of Human Knowledge (PHK): a campaign declares its rubric, tier configuration (quorum, audits, dispute/arbitration options), and assistance policy. Finalization produces a PHK Receipt that proves which rules were applied and what outcome was finalized. PHK does not claim "proof of truth" for subjective tasks; it claims that outputs were produced and reviewed under a declared rubric and tier. PHK also does not guarantee "one human, one account"; it targets bounded-risk outcomes through configuration, audits, and economic enforcement.
This whitepaper defines protocol invariants, trust boundaries, and intended architecture. Current live bootstrap/testnet behavior is documented separately in App Status and may evolve during bootstrap without changing the PHK-only finality model defined here.
Lioth supports privacy by design: contributors are not required to reveal identity to start participating in the protocol.
Cohort and specialization requirements can be satisfied through privacy-preserving credentials (e.g. zero-knowledge proofs of attributes) without deanonymization. Blockchain is used narrowly as a control plane for commitments (campaign specifications), receipts (finalization), and optional enforcement events, while sensitive task content, fraud artifacts, and deliverables remain off-chain.