Trust & methodology

How CodeCash works — in full.

The incumbent broke on opacity and fraud. Here is exactly how you're paid, what we transmit, and how we keep traffic honest. Nothing here is a black box.

The payout formula

Published and versioned — v1.0.0. Every signed receipt records the formula version it was paid under, so an old receipt stays verifiable forever.

# per monetizable event, all amounts in integer micro-USD gross = (CPM / 1000) × weight × quality # or 10% of order value for conversions net = gross × userShare # your money platform = gross − net

Event weights & split

Parameter	Value	Meaning
impression	×1	a verified, quality-gated view
engagement (click)	×8	intentional, far harder to fake
conversion	×60	or a 10% rev-share of order value
your share	70%	you keep 70%, platform 30%

The two invariants we will never break

No threshold throttling. The formula takes no balance, threshold, or lifetime-earnings input — it is mathematically impossible to taper your earnings as you approach cash-out. A unit test enforces this.
Reproducible receipts. Every receipt carries all its inputs. Anyone can re-run this formula and confirm the amount — your dashboard does it in your browser, trusting nothing.

Privacy promise

Your prompts and code never leave your machine. Targeting runs entirely on-device. The complete, exhaustive list of what a CodeCash client transmits is enforced in code by an allowlist — if anyone tries to add a field outside it, the client throws and the test suite fails.

What stays on your device, always

Prompts, agent conversations, code, file contents, file paths, directory and repository names, and the local signals used to pick an ad.

The only thing we receive

schema — a constant deviceId — a pseudonymous, rotating id (not your identity) periodStart — window start periodEnd — window end surface — a category like "agent-cli" (never which repo) events[] — per campaign: { campaignId, type, count, quality, cpmMicros } nonce — anti-replay

Aggregated counts, signed by your device key. No free-text field exists for context to hide in. The client is open source — read every byte that runs on your machine.

Fraud resistance

Advertisers pay real CPMs only when the traffic is real. CodeCash is built so impression-saturation — the attack that sank the incumbent — simply doesn't pay.

Verified impressions only. Payout is gated by genuine active-session signals (a real agent/build running, focused window, real time-on-screen). A tracker that fires on any render earns $0.
Device-bound signatures. Every counter must be signed by the key your device registered. You can't submit for a device you don't hold.
Replay protection & rate limits. Single-use nonces; bounded counters per device per minute.
Anomaly clamping & a daily velocity cap. Implausible volumes are clamped; a fixed $20/day gross cap bounds any single account — the same for everyone, independent of cash-out proximity.
Server-authoritative pricing. We credit using our own CPM and conversion values, never the numbers a client claims. Lying about CPM does nothing.
Weighted toward hard-to-fake events. Clicks (×8) and conversions (×60) dominate payout — far harder to fake than a view.
Sybil resistance at cash-out. Money only leaves to a verified payment identity, verified at withdrawal so honest users face no signup friction.