Casper Agentic Funding Protocol

Documentation for AI-governed milestone capital.

CodeQuity combines AI due diligence, milestone-based funding, and Casper proof rails so capital releases only when startup progress is visible and verifiable.

Product

Overview

CodeQuity turns startup funding into a proof-gated workflow.

Investors create CSPR-backed rounds, founders prove execution, and the AI layer evaluates whether the startup has crossed a milestone threshold.

The important difference is that funding decisions are not buried in private updates. Score, reasoning, wallet readiness, and Casper proof are visible inside the product.

AI-governed traction scoring
Casper Wallet deposit and release signatures
Milestone tracker with release eligibility
Founder raise readiness and investor due diligence
Judges

Demo Flow

A five-minute path that proves the product works end to end.

The best judging flow is landing page, startup profile, create round, Casper Wallet signature, round detail, AI proof, and milestone release.

If testnet signing is slow during judging, use a seeded round with existing deploy hashes and explain the proof rail from the round detail page.

Show the one-line pitch from the landing page
Open a startup profile and explain raise readiness
Create or open a CSPR-backed round
Show Casper Proof Rail and AI Agent Proof side by side
Trigger or explain an eligible release
System

Architecture

Next.js frontend, Supabase state, AI/backend actions, and Casper settlement.

The frontend owns the investor and founder workflows. Supabase stores startups, investors, rounds, milestones, wallet public keys, and durable agent outputs.

The backend agent layer scores startups and generates memos. Casper Wallet signs money-moving deploys, and Casper testnet references are displayed back in the round proof rail.

Investor / Founder
      |
      v
Next.js Launchpad
      |
      +-- Supabase: startups, investors, rounds, milestones
      +-- AI/API: score, memo, enrichment
      +-- Casper Wallet: deposit and release signatures
              |
              v
        Casper Testnet proof
Blockchain

Casper Proof Rail

Casper is used where proof and settlement matter most.

CodeQuity uses Casper Wallet for investor and escrow signatures, testnet deploy hashes for deposit and release proof, and a contract workspace for score-gated escrow hardening.

The UI makes Casper visible. A judge should not need to inspect logs to know which action touched the chain.

Deposit deploy hashes link to CSPR.live
Release deploy hashes are shown per milestone
Escrow mode is explicit: wallet or contract
Startup recipient public key stays visible before signing
Intelligence

AI Agent Layer

AI output becomes funding context, not decorative copy.

The agent produces a traction score, verdict, explanation, green flags, red flags, and investor memo context. The result is persisted so the round can show why a milestone is eligible or blocked.

This makes the AI decision inspectable. The product does not ask users to trust an invisible model.

Startup score
Due diligence summary
Green flags and red flags
Signal interpretation
Suggested next improvements
Revenue

Business Model

CodeQuity monetizes the capital workflow, not attention.

The first customers are accelerators, ecosystem funds, hackathon organizers, grant programs, and angel syndicates. They already release money in stages and need a cleaner way to verify progress.

Revenue expands from paid diligence into SaaS fund operations, success fees, APIs, and white-label launchpads.

0.5% to 2% success fee on released capital
Monthly SaaS for accelerators and grant programs
Paid AI diligence reports
Usage-based score and memo APIs
White-label launchpad deployments
Developer

Setup

Run the frontend, connect Supabase, and prepare Casper testnet.

The frontend runs from the `frontend` directory. A complete demo requires Supabase environment variables, backend API URL, Casper chain name, and a configured escrow public key.

Seed data matters for judging. Prepare one ready startup, one approved investor, one eligible round, and one round below threshold.

cd Casper_codequity/frontend
npm install
npm run dev
Readiness

Reliability

The submission should fail clearly and recoverably.

The demo must not depend on perfect live conditions. Wallet mismatch, missing wallet keys, backend delays, and testnet timing should produce readable states instead of dead ends.

The strongest reliability signal is a seeded demo with saved agent outputs and existing Casper deploy hashes, plus live actions available when the environment is healthy.

Readable wallet mismatch errors
Seeded round with deploy hashes
Persisted AI output fallback
Pending states for optional Casper fields
Clear production environment checklist
Monetization

How CodeQuity Makes Money

StreamBuyerModel
Success feeInvestors / funds0.5% to 2% of released milestone capital
SaaSAccelerators / grant programsMonthly fund operations dashboard
AI reportsInvestors / analystsPaid diligence reports or report credits
API accessVenture tools / agentsUsage-based score and memo endpoints
White-labelEcosystems / universitiesSetup fee plus subscription