Kutip Deployment Log

Tracks on-chain deployments as they happen.

Kite Testnet

Gas used (actual)

Deploy Steps

1. Fund wallets

1. Create (or reuse) a dev wallet in MetaMask.
2. Add Kite testnet network:
   • RPC: https://rpc-testnet.gokite.ai/
   • Chain ID: 2368
   • Currency: KITE
   • Explorer: https://testnet.kitescan.ai/
3. Visit https://faucet.gokite.ai → claim KITE (gas).
4. Acquire mock USDC (address 0x0fF5393387ad2f9f691FD6Fd28e07E3969e27e63). Options:
   • Mint via the contract's public mint on KiteScan (if exposed).
   • Ask in Kite Discord #testnet-support for a drip. You need roughly DEFAULT_QUERY_PRICE × demo queries ≈ 10 USDC for the service wallet.

2. Fill Kutip/.env

From Kutip/ root:

# Already gitignored — just edit in place
notepad .env        # Windows
# or: nano .env

Required keys:

For a solo hackathon demo it's fine to use the same address for deployer + operator + ecosystem fund.

3. Deploy contract

# From Kutip/contracts
forge script script/Deploy.s.sol:Deploy \
  --rpc-url $KITE_RPC_URL \
  --private-key $PRIVATE_KEY \
  --broadcast -vvv

On Windows PowerShell, $KITE_RPC_URL expands only if you source .env first. Easiest:

Get-Content ..\.env | ForEach-Object {
  if ($_ -match '^([A-Z_]+)=(.*)$') { Set-Item -Path "env:$($Matches[1])" -Value $Matches[2] }
}
forge script script/Deploy.s.sol:Deploy --rpc-url $env:KITE_RPC_URL --private-key $env:PRIVATE_KEY --broadcast -vvv

The script logs AttributionLedger deployed at: 0x.... Copy that address.

4. Wire address back into env

In Kutip/.env:

NEXT_PUBLIC_ATTRIBUTION_LEDGER=0x<address from step 3>
ATTRIBUTION_LEDGER_ADDRESS=0x<address from step 3>

Sync into the web app:

# From Kutip/
pnpm run env:sync

5. Fund the ledger's operator with USDC

The service wallet (= PRIVATE_KEY) must hold enough mock USDC to cover each query's totalPaid. Every attestAndSplit call:

1. transfer the full query fee to the ledger.
2. Ledger fans out 80 / 15 / 5 to authors / operator / ecosystem.

For a 2-USDC query the service wallet spends 2 USDC and receives 0.30 USDC back (15% operator share), so budget at least ~5 × queries × 2 USDC to run a smooth demo.

6. Verify on KiteScan

Visit https://testnet.kitescan.ai/address/<ledger> — you should see the constructor values (paymentToken = KITE_TESTNET_USDC, operator = ..., etc.).

7. Run the web app

cd web
pnpm dev

Visit http://localhost:3000/research → run a sample query → watch the 5-step agent progress → confirm step 5 lands a real tx on KiteScan.

Wallets

Fill these in after step 2.

Web app — Vercel + Blob storage

The Next.js app deploys to Vercel. Research summaries are persisted to Vercel Blob so /dashboard/history, /verify, and the receipt / reverse-x402 endpoints survive serverless cold starts.

1. Vercel dashboard → project → Storage → Create Database → Blob → connect to the project (all environments).
2. This injects the BLOB_READ_WRITE_TOKEN env var automatically.
3. Redeploy so the running deployment picks the token up.

The store is optional — without BLOB_READ_WRITE_TOKEN the summary store degrades to in-memory (per-instance, lost on cold start) and the app still runs. See web/lib/summary-store.ts.

Gas Estimates

Troubleshooting

• InvalidSplit revert at deploy — OPERATOR_BPS + AUTHORS_BPS + ECOSYSTEM_BPS must equal 10000.
• WeightMismatch revert at attestAndSplit — agent sends malformed citation weights. Check flattenCitationsForContract output sums to 10000.
• ERC20: insufficient balance — service wallet hasn't been pre-funded with mock USDC (step 5).
• Frontend says "not deployed" — NEXT_PUBLIC_ATTRIBUTION_LEDGER empty in web/.env.local. Run pnpm run env:sync after editing root .env.