Camp Network primary sources — 2026-05-11

Classification takeaway

Camp Network is best cataloged as AI-era IP-control-plane infrastructure rather than as a generic AI blockchain. Its main reusable mechanism is a provenance-and-rights stack that tries to make creative work, training inputs, derivative permissions, licensing terms, and royalty routing programmable onchain, then wraps those rights flows with usage-based payments, verifier security, and dispute processes.

Primary sources reviewed

1. Camp Network homepage — https://www.campnetwork.xyz/

   • Best first-party source for how Camp frames itself today.
   • Describes Camp as a Layer-1 blockchain built to modernize intellectual-property infrastructure and power AI agents on verifiable, user-owned IP.
   • Useful for capturing the project’s top-level positioning around ownership, sharing, monetization, and the autonomous IP layer framing.

2. Camp Network raise / architecture framing post — https://www.campnetwork.xyz/blog/camp-network-raises-30-million

   • Best directly fetchable first-party source in this pass for mechanism-level claims.
   • States that Camp prioritizes gasless IP registration and royalty distribution, supports isolated execution environments for AI agents, secure offchain-data handling, and native identity primitives, and centers the stack on a Proof of Provenance protocol.
   • Important because it makes clear that Camp is trying to package rights registration, derivative creation, licensing, and royalty flow as protocol infrastructure rather than only as marketplace UI.

3. AI’s Free Pass on IP: Are We Just Letting It Steal? — https://www.campnetwork.xyz/blog/ai-free-pass-on-ip

   • First-party problem statement from Camp.
   • Explains the training-data and attribution problem Camp is explicitly trying to solve: creators lose control when models train on scraped data without permission, licensing clarity, or payout paths.
   • Useful because it identifies Camp’s intended infrastructure surface: provenance, licenses, transparent audit trails, and automatic royalties.

4. AI Remixes Reality: The Battle for Ownership Rights — https://www.campnetwork.xyz/blog/ai-remixes-reality

   • First-party articulation of Camp’s derivative-works thesis.
   • Useful for how Camp frames style theft, voice cloning, derivative ambiguity, creator attribution, and automatic royalty routing.
   • Important because it shows Camp’s registry is meant to govern not just original creation timestamps but also downstream transformations and AI-mediated reuse.

5. Camp technical docs landing page — https://docs.campnetwork.xyz/

   • Official docs index page surfaced via search results.
   • Indexed snippet describes Camp as a purpose-built chain for AI agents trained on provenance-backed, user-owned IP and says Camp uses provenance to register user-owned IP onchain through Origin, turning IP into programmable, monetizable infrastructure.
   • Important because it names the main docs-level framing even though direct fetches from this environment were blocked by Cloudflare.

6. How Camp Works — https://docs.campnetwork.xyz/introduction/how-camp-works

   • Official docs page surfaced via search results.
   • Indexed snippet says Camp is a purpose-built blockchain for training and fine-tuning AI agents on decentralized, user-owned IP and that users can register assets through Origin.
   • Useful because it connects the rights registry to the agent-training surface more explicitly than the homepage alone.

7. L1 Architecture — https://docs.campnetwork.xyz/introduction/l1-architecture

   • Official docs page surfaced via search results.
   • Indexed snippets describe Camp’s Proof of Provenance stack, state that Origin Framework simplifies IP registration / management, and note a Decentralized Verifier Network (DVN) in the architecture.
   • Important because it reveals that Camp’s architecture is not just registry logic; it includes a separate verification/security layer.

8. Origin Framework — https://docs.campnetwork.xyz/introduction/l1-architecture/origin-framework

   • Official docs page surfaced via search results.
   • Indexed snippet says Origin streamlines registering and managing IP onchain and enables agents to mint and monetize new IP, including royalty-based transactions.
   • Important because Origin appears to be the product/control surface where registry entries become monetizable assets and workflows.

9. Staking — https://docs.campnetwork.xyz/introduction/l1-architecture/staking

   • Official docs page surfaced via search results.
   • Indexed snippets say staking secures Camp’s Decentralized Verifier Network (DVN), which validates high-value operations.
   • Important because it surfaces a separate stake-backed admission and security layer behind rights enforcement.

10. Technical Design Document — https://docs.campnetwork.xyz/origin-v1/technical-design-document

    • Official docs page surfaced via search results.
    • Indexed snippet describes Origin v1 as a trust-minimized IP marketplace where creators monetize data feeds as IPNFTs and buyers obtain time-boxed licenses to consume that data through onchain subscriptions.
    • This was the strongest clue that Camp belongs in the active corpus: it makes the rights object, time-bounded licensing, and subscription/payment surface unusually explicit.

11. x402 Payments — https://docs.campnetwork.xyz/origin-v1/x402-payments

    • Official docs page surfaced via search results.
    • Indexed snippet says creators can monetize IP assets with a usage-based pricing model where buyers pay each time they access or view the content.
    • Important because it connects Camp directly to machine-commerce style payment authorization rather than leaving monetization as an abstract royalty claim.

12. Origin dispute tutorials — https://docs.campnetwork.xyz/origin-v1/origin-dispute-tutorials

    • Official docs page surfaced via search results.
    • Indexed snippet says only users who have staked tokens in Camp’s staking vault can vote on disputes.
    • Important because it shows dispute resolution is tied to stake-weighted or at least staker-gated governance rather than purely neutral automation.

Retrieval caveat

• Direct fetches of the official docs pages from this environment were blocked by Cloudflare during this pass.
• I therefore used the official homepage and blog posts as the directly fetched first-party base, then supplemented them with indexed official-doc snippets surfaced by search results for specific Camp docs URLs.
• That means the broad mechanism is clear, but a future pass should capture the docs pages directly when access is possible, especially the technical design document, staking page, and dispute docs.

Why it stays in the active corpus

• Camp adds a distinct comparison point for provenance-backed AI-training and licensing infrastructure, not just for AI execution or creator-economy apps.
• It makes a useful split between registry/provenance, licensing/payment, verifier security, and dispute governance instead of collapsing them into one AI + IP narrative.
• It also creates a valuable bridge between several existing clusters in the corpus: crypto × AI infrastructure, payment authorization (x402-style usage pricing), provenance / authenticity systems, and governance over contested rights claims.

Follow-up comparison threads

• Compare Camp directly against Ritual and Allora so delegated compute / model markets do not get flattened together with rights registries and licensing rails.
• Compare Camp directly against Numbers Protocol so provenance-backed media history and AI-training-rights infrastructure do not get flattened into one generic authenticity bucket.
• Compare Camp directly against x402 / L402 / Graph Tally so usage-based payment authorization for IP access does not get flattened into ordinary royalty claims.
• Compare Camp directly against broader tokenized-IP or programmable-rights systems in a future pass so registry design, licensing templates, dispute rights, and verifier admission remain analytically separate.