Obolus
HomeResearchCreatorsDemoDocsRun research
What Obolus doesHow to run a queryHow creators get paidx402 tolls and citation royaltiesClaims, quotes, and weightsWhat a receipt provesSystem architectureSecurity and adversarial testsHow to test the claimsCurrent limits

Truth in scope

Current limits

The build proves the loop, but open production onboarding needs stronger controls.

Known limits

  • The corpus is curated and small until more creators register owned assets.
  • Creator ownership proof is not fully permissionless yet.
  • Open registration needs stronger account, domain, or artifact ownership checks before scaling beyond a curated cohort.
  • The run execution path should move to a durable queue for production.
  • Semantic entailment checks are still a next layer beyond literal substring verification.
  • Sponsored mode spends a central testnet wallet and needs persistent rate limits before public scale.

What scales next

The useful next work is not a new payment mechanism. It is creator ownership verification, a larger opted-in source cohort, durable run orchestration, and stricter abuse controls.

Need the implementation-level version? Read the root README, Architecture, Security, and Adversarial Testing documents in the repository.