Main Characteristics of the Protocol
1. General-Purpose Decentralized Task Protocol
Lioth enables requesters to distribute tasks and campaigns to cohorts of contributors and receive verified outputs through the Distribution Layer. This supports microtask workflows and higher-skill tasks without relying on a centralized intermediary for truth finalization.
2. Human Verified Outputs Via PHK
Lioth secures quality through Proof of Human Knowledge (PHK), a composable framework that combines validator review, audits, dispute/arbitration paths where enabled, integrity signals, and economic enforcement. PHK finality remains canonical truth: no Foundation operator, protocol service, or admin control rewrites accepted/rejected outcomes.
3. Datasets Are an Optional Packaging Layer
Lioth can package validated outputs into HVD datasets when tasks are structured for aggregation and reuse. Dataset assembly is optional: many campaigns produce HVOs only. Packaging can produce off-chain artifacts, manifests, and delivery references without making dataset mode mandatory for every campaign.
4. Privacy by Default; Cohort Targeting Without Identity
Contributors are not required to reveal real-world identity. When campaigns require specific attributes (region, expertise, role), participants can prove eligibility with zero-knowledge credentials, enabling cohort selection without deanonymization.
5. Defense-In-Depth Integrity Restrictions
Lioth uses multiple independent signals to deter automation and manipulation: task constraints, throughput controls, validator review, audits, clustering/integrity signals, and economic penalties after due process where enabled. Integrity restrictions can reduce routing or validator availability in some implementations, but they are not, by themselves, canonical proof of fraud or collusion.
6. Reputation and Operational Access Can Be Distinct
Lioth keeps protocol performance tracks and runtime access controls separate. Reputation tracks (R_work, R_valid) summarize finalized performance. Bootstrap or testnet implementations may layer a separate operational access score, such as Account Trust, on top of those tracks for caps, validator readiness, launch access, settlement timing, or reward shaping. This keeps protocol truth and runtime access semantics distinct.
7. Bootstrap Validator Availability Without Bootstrap Truth Authority
Bootstrap or testnet deployments may distinguish:
- policy eligibility under the active access rules;
- bootstrap approval, where used, to expand validator supply during cold start; and
- effective runtime readiness after account, safety, and integrity restrictions are all considered.
Bootstrap approval expands validator participation during bootstrap. It does not let an operator decide canonical outcomes.
8. Scalable and Cost-Efficient On-Chain/Off-Chain Separation
Lioth keeps content-heavy and sensitive data off-chain, while storing only critical commitments and receipts on-chain (validation results, finality receipts, provenance hashes, licensing references, and optional enforcement artifacts). This preserves privacy and enables throughput at scale.
9. Auditability and Transparent Quality
Validation rules are explicit. Campaign-level reports can summarize agreement, rejection, audit, duplication, and delivery metrics. Manual bootstrap or safety actions, when present, must be audited so operator intervention is visible without being confused for PHK truth.
10. Flexible Distribution Modes
The Distribution Layer supports multiple delivery paths: public distribution, private enterprise delivery, subscription feeds, and direct API/integration delivery. Lioth does not require outputs to be traded in a marketplace to be useful. Implementations can expose completion and delivery readiness as explicit states rather than treating acceptance alone as sufficient delivery.
11. Long-Term Incentives and Compounding Rewards
Participants are rewarded for quality and durability. Finalized outcomes compound reputation, bootstrap/testnet implementations may layer additional operational access policy on top, and contributors may earn future reuse value when packaged datasets are licensed over time. Bond-heavy participation can be enabled by later governance-controlled phases without changing the PHK trust boundary.