KOL Truster

How it works

Three roles, one contract per chain, two confirmations per milestone, and an arbiter that only steps in when the two sides disagree.

Roles

Project

Files a DYOR pack, agrees on milestones with a KOL, deposits the fee into the escrow. Gets back whatever is not earned.

KOL

Verified by hand before being listed. Sets their own rates. Accepts the deal on chain, delivers, gets paid per milestone.

Arbiter

Us. We review both sides before anything starts. On a deal we act only when one side opens a dispute: we measure, write a report both parties can read, and rule on chain.

Lifecycle of a deal

  1. 1Proposal. The KOL or the project writes the milestones, their shares, the currency, the amount and the deadline. The other side accepts or declines.
  2. 2Deposit. The project creates the deal on chain and deposits the full amount into the escrow contract. The money now belongs to the deal, not to us.
  3. 3Accept. The KOL accepts on chain. Until then the project can cancel and get everything back, no fee.
  4. 4Confirmations. When a milestone is reached, the KOL confirms it and the project confirms it, each with their own wallet. One confirmation alone moves nothing. The second one pays: 90% of the share to the KOL, 10% to the burn.
  5. 5Disputes. If one side will not confirm, either side opens a dispute on chain. The arbiter is notified, measures, writes a report and rules within a window (30 days by default). If both sides confirm in the meantime, the dispute ends by itself. If the arbiter does not rule inside the window, the share goes back to the project.
  6. 6Deadline. After the deadline plus a 7-day grace period, anyone can trigger the refund of every milestone that was never confirmed. Nobody, the arbiter included, can delay it.

Milestone types

Deliverable
A number of posts, spaces or videos, published and still online after seven days, with the sponsorship disclosed. Proof: the URLs.
Volume
DEX volume in USD over the window, read from the pool's swap events, excluding the wallets the project and the KOL declared. Undeclared wallets that trade like treasury wallets count against the milestone.
Holders
Net new unique holders above a minimum balance.
Market cap
Price averaged over 24 hours, not a single print, above the target, with liquidity above a minimum. A thin pool that spikes for a minute does not count.
Custom
Anything both sides can describe in a sentence and we can verify. Written into the proposal before the deposit.

Fee and burn

We take no cut. When a milestone is paid, 10% of that share goes to the fee sink of that chain. A keeper bridges the sinks to Robinhood Chain through Relay, buys $CASHCATSLLC and burns it, all of it. Every fee and every burn is listed on the burns page with its transaction.

What the arbiter can and cannot do

  • Can rule a disputed milestone reached or not reached, and nothing else. A milestone nobody disputed is out of its hands.
  • Cannot move funds in any other way. There is no rescue or withdrawal function in the contract.
  • Cannot stop the refund: after the deadline and the grace period, anyone can trigger it.
  • Has a bounded window to rule. Past it, the disputed share goes back to the project and the arbiter can no longer touch it.
  • Writes the numbers behind every ruling into a report both parties can read.

Disclosure

Every KOL on this platform discloses paid promotion in their posts. A deliverable that hides the sponsorship is not a deliverable.