Verified Royalties

The model behind every settlement on Ultimate Creator AI: royalties computed from measured exposure, backed by signed proof artifacts you hold and can check yourself — offline, without trusting us.

What This Model Does — and Does Not

Receipts and passports are point-in-time proofs, not claims about live account state. When measurement is unavailable, billed seconds fall back to the requested length — flagged requested, never passed off as measured. Revocation propagates as evidence, not as enforcement: platforms re-verify at decision time. Every settlement names its basis and carries the arithmetic, so an honest fallback is visible and a fabricated one is detectable.

Royalties, Not Rewards

A royalty is a contractual, auditable settlement: the asset was used, the exposure was measured, credits were split, and a signed record says so. It is not a discretionary payout whose formula lives inside someone else's accounting. On this platform, the amount, the split, and the exposure it came from are all on the receipt — and you do not need our database to check any of it.

What Creators Get

Per-second measured exposure. The render worker probes the delivered artifact — the file that actually shipped, not the request — and meters how long your avatar was on screen, your voice in the mix, your music in the timeline. A buyer who requests ten seconds but shows your avatar for three is billed for three. A render that carried none of your asset bills nothing, and that zero is a real measurement, not missing data.

A signed receipt per settlement. Each settlement produces an HMAC-signed receipt: the license, the credit split, the measured seconds and their basis. It is portable and offline-verifiable — any language with HMAC-SHA256 and JSON can check it. The signature is computed over canonicalized bytes, and the verifier's arithmetic cross-checks (non-negative amounts, gross equals creator share plus platform take) catch a mutated receipt before cryptography is even reached.

Revocation that is provable. Revocations land on a public, append-only, hash-chained feed. Pin the head, recompute the chain later, and any difference is tampering — by us or against us. Your right to pull an asset from circulation is not a promise in a support ticket; it is evidence with a hash chain on it.

Per-asset earnings analytics. Which assets earned what, on which renders, at which exposure seconds and basis — attribution rows back every movement in your balance history.

Three Proof Artifacts You Hold

Verification is not a dashboard you have to believe. It is three artifacts, each answering one question without the issuer:

  • The royalty receipt answers: was I paid, and for what? Signed proof of a settlement — amounts, split, exposure seconds and basis. Offline-verifiable against the public spec.
  • The content passport answers: what is this file, and which licenses does it carry? Signature, credentials, and license bindings, all verifiable offline.
  • The pinned feed head answers: what happened to my revocations? A hash-chained public feed; recompute it and any diff is tampering.

Together they close the auditable chain: content → exposure → settlement → payment, with revocation as the public transparency channel. Each link is independently checkable.

The Honest Limits

Proofs are point-in-time. A receipt proves what settled; a passport proves what was signed. Neither is a claim about live account state, and a receipt grants nothing — it is replayable by design.

requested is a real basis, and a limited one. When telemetry was absent, the job's target length was billed instead. That is an upper bound on exposure the buyer agreed to fund — it may over-bill the actual artifact and never under-bills it. It is honest precisely because it is flagged in the signed receipt; an unflagged fallback would be a fabricated measurement, and the two-value basis vocabulary makes those invalid.

Revocation propagates as evidence. The feed proves a revocation exists and when. It does not reach into other platforms' pipelines and delete files — a conforming platform re-verifies passports and feed state at decision time. Proof travels; enforcement is the consumer's responsibility.

Any Platform Can Do This

The model is public contracts, not proprietary plumbing. The specification documents are implementation-independent — a platform can produce and verify receipts with the document alone — and a conformance kit lets any implementation self-certify against machine-readable vectors, including a reference monitor for the revocation feed:

Read the Mechanics

For the engineer-level detail of one artifact — canonical bytes, signature, cross-checks, key rotation — see Royalty Receipts. For the content half of the audit chain — signed proof of what a generated asset is and how it was made — see C2PA Content Credentials.