// four ways to plug in
Start where it costs you nothing.
Every partnership starts with a briefing, and no rung requires a budget to begin. Where it goes next depends on what your project actually is. Institutional projects with no retail user base often go straight from a briefing to a data partnership, and never run a campaign at all.
I publish first. A page on your project goes live on my site, built from primary sources, every claim labeled confirmed, announced or speculated, and the gaps stated plainly where I could not verify something. Then thirty minutes with someone technical on your team to correct anything I got wrong and fill what I could not reach. You check facts. Conclusions stay mine.
Anything your product can gate or reward: access codes, early feature access, a trading competition, whitelist spots. I build the creative, screen every signup for farming, deliver by verified email, and report redemption numbers that survive your own team's scrutiny. The full engine is documented below, in production today.
A recorded conversation with your founder, cut into clips and distributed on my channels. The accuracy is already established upstream by the briefing, so the clips carry substance instead of soundbites.
A recurring feed of real usage numbers becomes recurring, evidence-tier coverage. Your figures carry weight because an independent party with a public correction record stands behind them, which is the one thing you cannot manufacture by publishing them yourself. Earned by accuracy over time, not sold.
// built, not promised
The campaign engine, already running.
Rung two is not a pitch deck. It is live infrastructure: automated delivery, a three-part onboarding sequence, and a farming filter that has held a real coordinated attack during a live drop while legitimate registrations went straight through.
Anti-farming built in
I audited my own first batch, found fake signups in it, and built this filter in response. It has since held a coordinated farming attempt against a live campaign. Fakes are caught before a code ever ships.
Redemptions, not claims
A claim is a signup. A redemption is someone actually using your platform. I count and report only the second: numbers that survive your own team's scrutiny.
An audience that reads
My readers come for educational content, not hype. A smaller audience than a shill account reaches, but one that reads, clicks through, and actually uses the products it gets access to.
Verified content standards
Every claim I publish is labeled confirmed, announced, or speculated, and my mistakes get corrected in public. A mention from a source that visibly checks facts carries real weight.
Verified email delivery
Codes arrive from one authenticated address, and I tell your users exactly which one in the campaign itself. Any code email from anywhere else is instantly recognizable as fake.
Full campaign package
Card creative, drop copy, timing with your team. You send the incentive and a logo. I do the rest.
You provide the incentive
Codes, early access, competition entries, whatever your product can gate. Plus a logo. That's the whole ask.
I run the drop
I build the card and the copy, screen every signup, and time the launch together with your own posts so both land at once.
You get clean numbers
A report of how many codes reached real, verified users. No inflated totals, no asterisks.
Partnership buys distribution. Not coverage.
Editorial independence is stated with every partner up front. Anything I publish about a partner project meets the same evidence standards as everything else, and partners fact-check mechanics, never conclusions. That's exactly why a mention here means something. No paid placement, no promoted threads, no sponsored posts. Nothing on this site can be bought.
Building on Canton?
Start with a briefing call, or bring a campaign idea. The first conversation costs nothing, and the numbers you get back are real either way.