How it works
Nobody holds the money. Nobody edits the numbers.
Six steps, one honest limitation. The full specification is in the whitepaper.
- 01
Fund
Brand locks USDC. Rate, cap and rules freeze on deposit.
- 02
Submit
Creators post clips. Each one is hashed and checked against every clip ever submitted.
- 03
Accrue
7 days. Views counted through the platform's own API, under the creator's grant.
- 04
Survive
7 days. No new views count. The platform's own audit corrects what was fake.
- 05
Score
A published schema runs over the committed record. Anyone can rerun it.
- 06
Settle
The program pays creator wallets direct. Leftovers go back to the brand.
You get paid on the views that survived
Not the headline number. The lowest count after a clip stops growing, once the platform has finished auditing its own data. Real views only go up, so honest creators lose nothing. Bought views get deleted, and the rule catches it for free.
Fig. 1 — Settlement on the surviving count
5.00 USDC / 1,000 · cap 500 USDC · 7d accrual + 7d survival
Drag the plot, or use the arrow keys
- Reading
- D13·18:0056 of 56 committed
- Accrual value
- 96,365frozen at D07 · a 72-hour settlement pays 481.83 USDC on this
- Platform count now
- 28,865corrected down 67,500 by the platform’s own audit
- Surviving count
- 28,865lowest count observed since D07
Settles at
144.33USDC
337.50 USDC returned to the brand rather than paid on views that did not survive
Committed readings · append only
- D13·18:00eb810c9228,865
- D13·12:00132f867128,865
- D13·06:00bc298be728,865
- D13·00:003337ce9f28,865
- D12·18:00177ea82728,865
The platform’s own audit removes the purchased block during survival. The minimum captures both corrections automatically, at no cost to the protocol and with no detection it had to fund.
Synthetic illustration of two curve shapes. Not protocol data, and no campaign has settled.
What we removed, and what we could not
- CustodyNo operator can touch the money.
- Payout authoritySettlement executes on-chain, not by hand.
- Quiet editsReadings commit when taken. Append only.
- Secret rulesThe schema is public and versioned.
- The countIt comes from the platform. No chain fixes a wrong number at the source.
- The readerOne entity holds the API keys. It cannot touch funds, and every reading it signs is permanent.
- Live thresholdsHeld back while in force, published once retired.
The rest is in the whitepaper
Settlement function, bond maths, threat model, compliance, and every limitation we know about.