Katama·Docs
StatsWorkspace ↗

On-chain transparency

Every paying user's daily activity is logged to Base mainnet. Public, verifiable, no fake metrics. The platform's on-chain record is the source of truth that investors, auditors, and curious users can read directly off the chain.

Live data: katama.ai/stats · your own record: katama.ai/blockchain

What gets logged

Once per day, at 00:00 UTC, the platform writes one transaction per active user:

  • userIdHash — keccak256 of the internal user UUID (pseudonymous, no email or wallet exposed).
  • date — YYYYMMDD as uint32.
  • generations, creditsUsed — totals for the day.
  • videoCount, imageCount, otherCount — subset by kind.
  • kataBurnedWei — this user's share of that day's buyback burn.

What stays off-chain

  • Prompts, outputs, names, emails, wallet addresses.
  • Per-generation amounts (only daily roll-ups are written) — keeps individual usage private while platform totals remain public.

Who pays the gas

Katama. The user never signs a transaction, sees a MetaMask popup, or pays gas. The cron wallet on the VPS holds a small ETH balance on Base and signs the daily batch — the rest of the platform is a normal SaaS experience.

Cost is ~$0.001 per active user per day. At 1,000 active users that's ~$30 / month — irrelevant compared to the credibility of an on-chain audit trail.

Why Base

  • $KATA already lives on Base (bridged from ETH via Axelar ITS).
  • ~$0.001 per transaction — cheap enough for per-user logging at scale.
  • Coinbase ecosystem credibility for institutional reviewers.
  • EVM compatible — standard tooling, no custom wallet UX required.

How users see it

Three surfaces:

  • /stats — public, no auth. Total generations, credits, $KATA burned, recent batches with TX links.
  • /blockchain — per-user dashboard. Your own daily records, your share of the burn, links to each Basescan transaction.
  • Verified on Base badge — small chip on every generation in your history that has been recorded on chain.

Next: Architecture →