DEV Community: Shilika

How to Pitch a Web3 Security or AI Safety Story to Mainstream Business Press in

Shilika — Sun, 21 Jun 2026 18:30:51 +0000

How to Pitch a Web3 Security or AI Safety Story to Mainstream Business Press in 2026

There is a pitch sitting in a Bloomberg reporter's inbox right now that will never get a reply. It leads with token price. It name-checks the VC firm that led the round. It describes the audit finding in four sentences of Solidity-flavoured jargon. And it ends with a boilerplate line about "revolutionising decentralised finance."

That pitch is not the problem. That pitch is the problem.

Founders building legitimate, technically rigorous Web3 security companies and AI safety labs are sitting on story angles that Bloomberg, the Financial Times, Reuters, and the Wall Street Journal are actively hungry for. They just cannot see it, because they are pitching through the wrong frame. This guide is about rebuilding that frame from scratch.

Why Mainstream Business Press Is Actually Interested Right Now

The scale of the problem has crossed a threshold that makes it impossible for tier-1 financial journalists to ignore.

In Q1 2025 alone, over $2 billion was lost from Web3 protocols in ninety days, a 96% increase year-on-year. The Bybit breach in February 2025 accounted for $1.46 billion of that in a single event. North Korean state-sponsored actors stole $2.02 billion in cryptocurrency across 2025, a 51% year-over-year increase, while AI-enhanced phishing campaigns targeting wallets generated 158,000 reported incidents in the same period.

These are not niche crypto numbers. These are systemic financial risk numbers, and Bloomberg's cybersecurity desk knows it. Bloomberg's own coverage in May 2026 ran the headline "Hackers Armed With AI Stoke Fears for $130 Billion Crypto Sector," framed not as a Web3 story but as a financial stability story.

That is the frame you need.

Meanwhile, AI safety has its own tier-1 moment. The ECB convened European banks specifically to fix flaws exposed by AI models. The White House has been circulating an AI cybersecurity directive. These are governance and financial stability stories dressed in technical clothing, and the reporters covering them need expert sources who can translate between the technical reality and the business consequence.

The Core Reframe: Systemic Risk, Not Technical Exploit

The single biggest error Web3 security founders make is pitching the exploit rather than the exposure. Here is what that looks like in practice.

Wrong pitch frame: "We discovered a reentrancy vulnerability in Protocol X's bridge contract that could allow an attacker to drain the liquidity pool."

Right pitch frame: "A class of smart contract flaw that has now caused $400 million in losses across four DeFi protocols in the last eighteen months still has no industry-standard remediation requirement. Institutional investors are exposed to this risk through funds that hold these assets, and most of them do not know it."

The second version answers the question every finance journalist's editor will ask: Why does this matter to my readers? Those readers are portfolio managers, risk officers, pension fund trustees, and corporate finance directors who read the FT and Bloomberg to understand business risk. They do not read CoinDesk.

The principle applies directly. Once you expand a security story beyond the technology and into areas of economic consequence and human impact, your chances of coverage grow substantially. Journalists covering Bloomberg and the FT are looking for stories that matter to their audience, not product launches dressed up as thought leadership.

The Three Story Architectures That Land at Tier-1

When a Web3 security or AI safety angle gets picked up by Bloomberg, Reuters, or the FT, it almost always fits one of three story architectures.

1. The Systemic Contagion Story

Web3 protocols operate as interconnected money legos, relying on oracles, bridges, and external liquidity. A protocol's security is constrained by its weakest dependency. A manipulated oracle or compromised dependency can trigger cascading failures even when the internal logic is correct. Because smart contracts are open-source and composable by design, the concept of a fixed security perimeter is becoming obsolete.

This composability risk is genuinely underreported in mainstream press and genuinely frightening to institutional investors. Your pitch should frame it as follows: here is a vulnerability class that is structurally embedded in how DeFi protocols connect to each other; here is the dollar value of assets that are transitively exposed; here is why patching one contract does not fix the problem.

That is a systemic risk story. It belongs in the FT's capital markets coverage, not CoinTelegraph.

2. The Regulatory Arbitrage Story

Access control failures accounted for 59% of crypto hacks in 2025, costing $1.83 billion in stolen funds. Traditional security frameworks like ISO/IEC 27001 and NIST are ill-equipped to address AI-specific threats such as prompt injection and model hallucination. This gap has left Web3 platforms exposed to novel attack vectors that regulators have not yet caught up to.

Regulatory arbitrage stories are catnip for Reuters and the WSJ. Your pitch should connect a specific technical gap (audit requirements, signing infrastructure standards, AI agent access controls) to a specific regulatory vacuum that affects institutional participants. EU MiCA, the GENIUS Act, and SEC digital asset guidance all have obvious seams where security requirements are either absent or unenforceable. These seams are stories.

3. The Expert Source Offer

Not every pitch has to be a standalone story. Sometimes the most powerful pitch is simply: I have a credible expert who can speak to a story you are already working on.

Journalists are constantly looking for trusted sources they can call on when something happens. If you can introduce a spokesperson as the person who predicted the attack class that just hit the news cycle, you are not pitching a story. You are offering a source relationship. That is much easier for a journalist to say yes to, and it builds the kind of relationship that produces recurring citations.

The positioning must be sharp. Outline their expertise, why they have authority, and the specific topics they are prepared to take a stance on. A spokesperson who speaks as an industry expert rather than plugging your brand is the one who gets called back, consistently.

Which Journalists to Target, and at Which Outlets

Mainstream business press covers Web3 security and AI safety across three distinct beats, and pitching the wrong beat to the wrong reporter is worse than not pitching at all.

Bloomberg Cybersecurity Desk covers AI model flaws, crypto exchange security, nation-state hacking, and financial sector cyber risk. This desk ran the $130 billion crypto sector hacking story in May 2026. Stories must connect to financial market exposure or regulated institution risk.

Bloomberg Crypto, with Olga Kharif as the primary crypto beat reporter, reaches the institutional and traditional finance audience that moves large capital. Bloomberg's editorial standards, including source verification requirements and legal review, make these stories slower to produce but much more durable in credibility. Do not pitch product launches here. Pitch market structure risk and systemic exposure.

FT Alphaville and FT Technology run crypto and AI safety through a financial markets lens. Regulatory gap stories and institutional investor exposure stories have a home here, particularly anything connecting to EU MiCA compliance or ECB-level systemic concern.

Reuters FinTech and Risk covered the ECB AI model convening in May 2026 and runs a regular beat on financial institution cyber risk. Pitches that quantify dollar exposure and name specific regulatory frameworks perform best here.

WSJ Tech and Finance Crossover is currently covering AI safety as a governance and liability story, framing it around executive accountability, board-level oversight, and fiduciary duty. An AI safety founder who can speak to AI model failure modes in terms of corporate liability exposure (not just technical risk) has a real angle here.

The Pitch Mechanics That Actually Work

A media pitch is not a press release and it is not a marketing email. It is a direct, personal proposal that answers three questions clearly and quickly: Why this story? Why this journalist? Why now? If your pitch cannot answer all three, it is not ready to send.

For Web3 security and AI safety specifically, the mechanics that distinguish successful pitches are as follows.

Lead with the macro number, not the technical detail. "A novel class of access control exploit has now cost the industry $1.8 billion in eighteen months" is a stronger opening than any description of the exploit itself. The technical detail is supporting material, offered after the journalist has a reason to care.

Connect to a news peg within the last two weeks. Editors are always on the lookout for relevant and timely news stories, and aligning a pitch with current developments increases the likelihood of capturing the journalist's attention. If the Bybit breach or a new AI model flaw is in the news cycle, your pitch should explicitly connect your angle to that peg before offering the broader systemic view.

Offer data, not claims. Tier-1 journalists at Bloomberg and the FT use a significantly higher bar for source credibility than crypto-native outlets. Bringing original data (on-chain loss figures, audit finding rates, AI vulnerability disclosure timelines) gives journalists something to independently verify. The pitch that includes "I can share our analysis of 340 DeFi security incidents since 2023 showing the pattern" is far stronger than one that says "we believe bridge security is underestimated."

Make follow-up easy, not aggressive. A second follow-up is sometimes appropriate if the story has developed since the original pitch. A third is almost never appropriate and risks damaging the relationship for any future pitch.

Building the Journalist Relationship That Produces Recurring Citations

One successful pitch is not a media strategy. What produces recurring expert source citations in Bloomberg or the FT is a journalist relationship built over twelve to eighteen months, not a single email.

The practical cadence looks like this.

Months 1 to 3: Introduce your spokesperson with a brief bio and a clear statement of the three to five topics they can speak to on record. Make this a relationship introduction, not a pitch. Journalists remember sources who help them do their jobs well and reach out to those sources first when they need expert commentary.

Months 3 to 6: Send one piece of original analysis (a short briefing note, a data point, a pattern spotted in on-chain data) that is directly useful to the journalist's beat, with no ask attached. Share useful data, flag relevant stories, and engage with their work.

Months 6 to 12: When a relevant story breaks, be the first source in the journalist's inbox with a clear, concise on-record quote that does not require editing. Build the reputation of the source who makes their job easier.

Month 12 onward: You are now a recurring source. The relationship sustains itself through continued usefulness.

This is what a blockchain PR firm that understands tier-1 relationships actually builds. It is not a distribution service. It is a long-game relationship programme executed by someone who knows which journalists cover which beats, how they prefer to receive pitches, and what makes them feel confident enough to put your spokesperson's name in a Bloomberg story.

The Embargo Question for Security Stories

Web3 security stories have a complication that most other tech stories do not: responsible disclosure timelines.

If your angle is a live vulnerability or an active bug bounty finding, you cannot pitch freely before the protocol has been notified and patched. But once the disclosure window closes, you have a narrow and highly valuable news moment.

The right approach is to pre-brief one journalist under embargo before the public disclosure date. Offer them the exclusive on the technical detail, with the understanding that their story publishes simultaneously with the public disclosure. This gives the journalist a scoop, gives you the credibility of tier-1 coverage, and respects the responsible disclosure process.

If the embargo breaks, have your public statement ready to go immediately. The risk of an embargo break in security contexts is lower than in funding announcements because the disclosure timeline is usually coordinated across a smaller group of informed parties. But the preparation is identical: know your response, have it approved, and be ready to move.

What Not to Do

Four pitching behaviours guarantee your email goes unanswered.

Pitching token price as the story. No finance journalist at Bloomberg or the FT is writing about your token's price action. If your pitch mentions market cap, it is going to the wrong outlet.

Name-dropping VC investors as the credibility signal. Your lead investor's name impresses crypto media. It does not impress a Bloomberg reporter who has seen dozens of well-funded projects collapse. The credibility signal at tier-1 is your technical depth, your data, and your willingness to speak on record about systemic problems and not just your own solutions.

Sending the same pitch to multiple reporters at the same outlet simultaneously. Journalists talk to each other. If two reporters at the FT receive the same pitch on the same day, neither will run it, and your relationship with both is damaged.

Pitching without reading recent bylines. The journalist covering crypto insurance liability at Reuters is not the same person as the one covering AI model governance at Bloomberg. Read three recent bylines before you write the first word of a pitch.

The Window Is Open Now

The opportunity for Web3 security and AI safety to become a permanent mainstream business press beat is open right now. The losses are large enough, the institutional exposure is real enough, and the regulatory pressure is building fast enough that tier-1 journalists need credible technical sources who can speak in business risk language.

The founders who build those relationships in 2026 will be the ones who get called when the next major incident breaks. At that point, they will not need to pitch at all.

Founder-Led LinkedIn for Web3 and AI Builders: The 2026 Algorithm-Proof

Shilika — Sun, 21 Jun 2026 17:30:16 +0000

Founder-Led LinkedIn for Web3 and AI Builders: The 2026 Algorithm-Proof Operating System

Something broke for a lot of founders in Q1 2026. Posts that used to earn thousands of impressions started flattening out at a few hundred. DMs from investors dried up. Visibility that felt earned, compounded over months of consistent output, evaporated almost overnight.

This wasn't random. LinkedIn rebuilt its content distribution engine, and most founders, including a lot of smart ones in the Web3 and AI space, hadn't noticed the rules had changed.

Here's what's actually going on, and what to do about it if you're a builder in this space.

What Changed in March 2026 (And Why Generic Advice Doesn't Cover It)

LinkedIn's "Authenticity Update," which rolled out in phases from January through March 2026, was the platform's most aggressive algorithmic overhaul in its history. The short version: the platform stopped rewarding how often you post and started measuring how deeply people actually engage with what you publish.

The new system, built on a 150-billion parameter model called 360Brew, evaluates what it calls a "Depth Score." Rather than counting likes, it tracks how long someone pauses on your post, whether they expand the text, whether they save it, and whether the resulting comments go anywhere substantive. Superficial engagement patterns, the "Great post!" replies, the reaction pods, the templated frameworks, now hurt reach rather than help it.

But there's a second change that most LinkedIn strategy guides haven't caught up with yet: the profile-to-content alignment check. The 360Brew model doesn't just evaluate your post in isolation. It cross-references what you're claiming against your headline, About section, and work history. If your profile says "DeFi Protocol Co-Founder" but you're posting about productivity frameworks, the algorithm registers a mismatch and suppresses distribution. If your profile and your posts tell the exact same story, specific, credible, and consistent, the system treats that coherence as an authority signal and amplifies accordingly.

For Web3 and AI founders, this changes the build order. Profile comes first. Content comes second.

Step One: Build a Profile That Earns Topic Credibility

The goal here isn't keyword stuffing. It's creating what the algorithm reads as a "logical loop," where every section of your profile validates every other section, all pointing at the same narrow expertise cluster.

Your headline should name the problem you solve, not your job title. "Co-Founder at ProtocolX" tells a VC or journalist nothing. "Building verifiable AI inference infrastructure for DeFi | Co-Founder at ProtocolX" tells them exactly what category you operate in, who cares about it, and why you're a credible voice.

Your About section should read like a thesis, not a biography. What do you believe is broken in your corner of the market? What did you build in response? What specific outcomes have users or partners seen? Skip the origin story. Investors and journalists who find you on LinkedIn care whether you understand the problem, not where you went to school.

Your skills and experience need semantic clustering. The algorithm looks for contextual validation: if you claim expertise in zero-knowledge proofs, your experience section should describe specific deployments, not vague responsibilities. The model checks for depth. Isolated keywords with no surrounding context read as shallow.

One critical update for 2026: Creator Mode was deprecated in March 2026. The follow button, Featured section, and LinkedIn Live access are now standard across all accounts. The algorithm no longer gives Creator Mode profiles any distribution advantage; it evaluates all accounts equally on behavior and content-profile alignment. If you've been relying on that toggle, it's gone.

Step Two: Content Formats That Actually Win Now

The format landscape shifted materially. Here's what the data shows for 2026.

Native vertical video is the single largest distribution opportunity LinkedIn has opened in years. Short-form vertical video (15 to 90 seconds, portrait orientation) gets preferential distribution, including reach beyond your existing followers, at a rate not seen with any other format. For Web3 and AI founders, this is underutilized. A 60-second breakdown of why a recent on-chain event matters, shot on your phone and posted natively, will outperform a carefully written text post by a significant margin. The caption matters: AI models extract meaning from transcripts and text, so don't skip it.

Document carousels (PDF uploads) remain the strongest native format for dwell time. They generate two to three times more time-on-post than single images or text updates, which directly feeds the Depth Score. The key distinction for 2026: the carousel "swipe for more" hack, thin insights spread across gradient slides, is now actively suppressed. Carousels need to deliver genuine frameworks, data, or decision-useful breakdowns that a Web3 operator or AI investor would actually save and return to.

Long-form text posts and LinkedIn articles drive AI citation probability. LinkedIn is now the second most-cited domain by large language models, generating roughly 170,000 monthly citations across platforms including Google's AI Overviews and ChatGPT. Roughly 75% of those citations point to individual member profiles, not company pages. Long-form articles and newsletters account for a disproportionate share of those citations, and they bypass the feed algorithm entirely for subscribers, giving you reliable reach that doesn't depend on the Depth Score.

What's dead: Polls (0.07% engagement rate in 2026, actively categorized as low-effort bait). Hashtag-heavy posts (hashtags are essentially irrelevant since the algorithm now uses semantic understanding of your text). Engagement bait phrases like "Comment YES if you agree" now trigger an algorithmic penalty. And generic AI-generated content, the "In today's fast-paced world" openers, the bullet-heavy frameworks with no personal voice, gets suppressed not because LinkedIn can detect AI specifically, but because it earns near-zero dwell time. Nobody reads it. The algorithm notices.

Step Three: The Cadence That Compounds Without Burning Out

The instinct for most founders is to post more when reach drops. That's the wrong move in 2026. Posting too frequently cannibalizes your own distribution, with each new post cutting off the previous one before it's had time to circulate.

The sustainable cadence that the data supports: three high-quality posts per week, sustained over 60 days, builds more algorithmic authority than daily posting for two weeks. That's it. The compounding comes from consistency over time, not volume in the short term.

A workable content mix for Web3 and AI founders:

40% carousels: frameworks, protocol analyses, comparison breakdowns, market structure explainers. Content your audience will save and reference.
30% native video: short-form takes on recent events, behind-the-build moments, plain-language explanations of technical concepts your investors or media contacts might misunderstand.
20% long-form text or articles: your actual views on where the space is going, the decisions you've made and why, the things you got wrong. This is the content that earns AI citations and investor DMs, and it's the content that gets you quoted.
10% reactive: your response to breaking regulatory news, on-chain events, or competitor moves. This is your newsjacking window. Posting within a few hours of a relevant event, with a specific and credible take, catches the algorithm's real-time relevance boost.

For the engagement strategy that reinforces all of this: spend 15 to 20 minutes a day leaving substantive comments on posts from investors, journalists, and peers in your specific niche. The algorithm builds a picture of your professional neighborhood from who you engage with, not just what you post. If you're a DePIN founder consistently commenting on infrastructure-layer discussions among people who matter in that category, your content reaches more of those people when you publish.

Step Four: How LinkedIn Visibility Converts to Investor and Media Inbound

This is the piece that's specific to Web3 and AI founders, and that generic LinkedIn advice almost never addresses.

The B2B buying journey has fundamentally shifted. Research shows that 32% of professionals now discover thought leadership through GenAI tools, and 45% of B2B buyers use GenAI specifically for vendor and product research before a conversation ever happens. In the Web3 and AI context, this means institutional LPs, VCs, and journalists are increasingly asking AI tools about founders and protocols before they reach out. What those AI tools say is shaped, in large part, by what you've published on LinkedIn.

LinkedIn's own internal data confirms that members with 3,000 or more followers show a meaningfully stronger probability of AI citation. Engagement also matters: posts with 10 or more substantive comments appear more frequently in LLM-generated responses than posts that go quietly. The implication is that the Depth Score and AI citation probability are optimizing for the same thing. Content that earns real engagement from real people in your space is also the content that teaches AI models who you are.

For converting visibility into concrete inbound:

For investor interest: Your most important LinkedIn asset isn't a single post. It's the pattern of posts over 60 to 90 days. A partner at a crypto-native fund who's seen you write substantively about sequencer decentralization or AI agent inference costs across a dozen posts isn't cold when you pitch. They already have a prior. The DM or warm intro that follows is a conversion event that started weeks earlier.

For media inbound: Journalists covering Web3 and AI at Tier-1 outlets search LinkedIn when they need expert sources. A profile with topical authority in a specific sub-category (DePIN, AI x crypto, RWA tokenization, agentic infrastructure) and a recent track record of substantive posts is a direct inbound channel for quote requests and interview invitations. Your LinkedIn presence is the always-on press kit that works while you're building.

For AI search visibility: The mechanics favor specificity. An AI model assembling an answer about zk-proof applications in DeFi will cite the LinkedIn article where you explained your specific architectural decisions over the generic "Web3 is the future" post that ten thousand accounts have published in some variation. Niche specificity is not a limitation. It's the entire strategy.

The Founder-Specific Mistake to Avoid

Most Web3 and AI founders who struggle on LinkedIn in 2026 are making one of two errors.

The first is topic sprawl: posting about their protocol one day, market sentiment the next, AI regulation after that, and personal productivity on Friday. The algorithm can't build a coherent picture of what you're an authority on. Neither can a VC or journalist who lands on your profile. Pick two or three pillars that are genuinely connected to what you're building and stay there.

The second is delegating the insight. Using AI tools to research supporting data, generate hook variations, or clean up a rough draft is completely fine and often smart. The problem is starting from an AI output and adding a thin veneer of personality. The algorithm's behavioral signal is brutal here: if your post doesn't contain a specific observation that only you could make, from your position, your team's experience, your on-chain data, nobody will read past the first two lines. No dwell time. No distribution. No inbound.

The original observation is yours. The AI can help you do everything else with it.

What to Build in the Next 60 Days

If you're starting from a LinkedIn profile that hasn't been updated since your last funding round, here's the sequence that moves the needle:

Audit and rewrite your profile (headline, About, and skills cluster) so it maps precisely to the two or three technical topics you'll be posting about.
Publish a native article (800 to 1,200 words) on the most specific, defensible position you hold in your space. This is your citation anchor, the piece that AI models will eventually surface when someone asks about your category.
Set your cadence at three posts per week: one carousel with a genuine framework, one native video explainer, one long-form take or reactive post. Block 90 minutes per week for this. Not per day. Per week.
Engage for 15 minutes per day: substantive comments on posts from investors, journalists, and technical peers in your specific niche.
Track the right signals after 30 days: saves, quality comments, profile views from your target audience, and eventually inbound DMs. Not vanity metrics. Not follower count.

The founders winning on LinkedIn in 2026 aren't the ones posting most often. They're the ones who've built a profile that earns the algorithm's trust, published content that earns their audience's attention, and done both consistently enough that the compounding kicks in.

In a space where every protocol sounds the same and every pitch deck makes the same claims, a founder who can explain what they're building, specifically, credibly, and in their own voice, has a durable edge. LinkedIn is where that edge becomes visible.

Cybersecurity Startup PR: How Web3 Security Firms Get Into Wired, MIT Tech

Shilika — Sun, 21 Jun 2026 16:30:17 +0000

Cybersecurity Startup PR: How Web3 Security Firms Get Into Wired, MIT Tech Review, and Tier-1 Crypto Media

Web3 security companies sit at an unusual intersection. They possess the most compelling proof points in all of crypto: live exploit data, on-chain forensic trails, multi-million-dollar bug payouts. And yet almost none of that material is freely available for a PR pitch. Vulnerability disclosures are embargoed with the affected protocol. Bug bounty payouts are confidential. Forensic conclusions belong to a client who may be mid-litigation. Audit reports are released on the protocol's timetable, not yours.

The result is a PR vacuum that most security founders fill the wrong way. They either say nothing and remain invisible, or they chase someone else's disaster by quote-tweeting a hack without positioning themselves as the authoritative voice on what happened and why.

This post is for founders of smart contract auditors, on-chain forensics firms, and bug-bounty platforms who need a repeatable earned-media flywheel, one that builds institutional credibility without compromising client relationships or triggering legal exposure.

Why This Is a Different PR Problem Than Generic Web3

Most Web3 PR playbooks are written for token launches, DeFi protocols, or L1 chains. The narrative levers are straightforward: TVL numbers, ecosystem grants, exchange listings, famous investors. Security firms have none of those levers. The ones they do have come with embedded risk.

Consider the stakes. DeFi has already suffered more than $10 billion in cumulative losses from hacks and bridge exploits. In 2025 alone, roughly $3.35 billion was lost across 630 security incidents, with the average incident size reaching $5.32 million. MIT Technology Review covered the Bybit breach, where attackers linked to North Korea stole more than $1.5 billion worth of Ethereum in a single weekend, as a mainstream technology story rather than just a crypto story. That editorial appetite exists. The question is how a security firm becomes the quoted authority in those pieces rather than a footnote.

The answer requires understanding what editors at Wired, MIT Tech Review, and The Block are actually looking for and what a generic Web3 agency almost always gets wrong.

Tier-1 Media That Covers Web3 Security With Depth

Before building a pitch strategy, get clear on the publication landscape.

MIT Technology Review publishes long-form investigative and explainer content on blockchain security that is read by technologists, policymakers, and institutional investors. Their coverage of digital asset security in early 2026, including features on AI-enabled threats and quantum computing risks to crypto custody, demonstrates genuine editorial depth. They want researcher-grade sources, not marketing quotes.

Wired covers AI, cybersecurity, and technology ethics with a technically literate audience that includes academics, policy professionals, and senior engineers. For Web3 security, the angle that lands is systemic risk rather than individual exploits. The structural question of why the same failure modes repeat across cycles, compromised admin keys, bridge configuration errors, phishing on multi-sig signers, is the story Wired will assign.

CoinDesk and The Block are the tier-1 crypto-native outlets. After every major exploit, including the $292 million Kelp DAO breach in April 2026 and the Drift compromise, these publications publish rapid-response coverage followed by detailed post-mortems. Security firms that are reliably available to explain the technical mechanics in plain English, on deadline, become recurring sources.

Decrypt covers security with a slightly more accessible editorial voice. The Record, from Recorded Future, covers blockchain security from a cybersecurity-native perspective that security founders will find receptive.

The common thread across all of these publications: technical accuracy, source reliability, and the absence of promotional language. A cybersecurity PR strategy must be built on technical credibility first. Marketing claims destroy journalist trust instantly in this vertical.

The Responsible Disclosure PR Flywheel

The most structurally powerful media moment for a Web3 security firm is a responsible disclosure. Your researcher finds a critical vulnerability in a third-party protocol, notifies the team, coordinates a patch, and then, with the protocol's agreement, discloses publicly.

This is also the most legally and relationally complex moment to manage. The process requires that you work with the affected vendor and that a fix is issued before going public. You must explicitly document that your firm acted as an ethical defender, not a reckless threat actor. Disclose too early, include proof-of-concept exploit code, or break an agreed embargo, and you lose client relationships, face legal exposure, and potentially trigger exploitation of un-patched systems before the fix is live.

Get it right, and you have a story with everything an investigative journalist needs: a verifiable on-chain vulnerability, a named CVE or equivalent, documented coordination with the protocol team, quantified potential impact, and a clean resolution. Here is how to package it.

Pre-disclosure: Establish the publication timeline in writing with the protocol team before any public announcement. Most responsible disclosure programs give vendors a 90-day window. In DeFi, expect faster turnaround given the live financial risk. Agree on who controls the story and whether your firm can be named publicly. Some protocols will want to own the announcement. Negotiate co-credit upfront.

Embargo the story: If the vulnerability is significant, offer an exclusive embargo to one tier-1 outlet before the fix goes live. This means giving a journalist a full technical briefing under embargo. They prepare the story, you coordinate release timing with the protocol, and the piece publishes simultaneously with the disclosure. This produces far better coverage than a reactive press release and builds a lasting relationship with that reporter.

The disclosure write-up: Publish your own detailed technical post-mortem on your research blog simultaneously with the public disclosure. This becomes the canonical reference document: the piece that journalists cite, that other researchers link to, and that LLMs pick up as a knowledge source. Include root cause analysis, the disclosure timeline, and if the protocol permits, the specific vulnerability class. Do not publish exploit code that could be replicated before equivalent systems are patched.

Pitching Researchers as Sources, Not Founders as Spokespeople

Most Web3 PR pitches lead with the CEO. In security PR, the researcher is the credibility signal.

When CoinDesk needs a source to explain why a cross-chain bridge configuration error enabled a $290 million exploit, they do not want a spokesperson from a security firm's marketing team. They want the person who audited a similar architecture, who can speak to the specific vulnerability class with technical precision, and whose professional background is verifiable.

This means your PR strategy must build the individual profiles of your senior researchers alongside the firm brand. Three specific actions matter.

Named research publication: Every significant vulnerability class your researchers identify, even when the specific client is confidential, can be published as generalized research. "We identified five smart contract audit patterns where cross-chain verification assumptions create systemic risk" is publishable without disclosing any client. This creates a body of citable work that establishes your researchers as domain authorities.

Conference appearance strategy: Security-native conferences, including EthCC security tracks, Devcon, ZK Summit, and academic venues like IEEE Security and Privacy, carry more credibility with tier-1 technical journalists than general crypto marketing conferences. A 20-minute technical talk from one of your researchers on a specific vulnerability class generates lasting reference material that journalists can cite long after the event.

Journalist source registration: Introduce your senior researchers to security beat reporters at the relevant outlets before a crisis, not during one. A brief note explaining that your lead researcher worked extensively on cross-chain bridge security and would be available as a technical source when the next bridge exploit hits, sent weeks before a major incident, establishes the relationship at zero cost. Reporters remember who was useful when it mattered.

Building the Earned-Media Flywheel Without Client Proof Points

The practical reality of running a Web3 security firm is that most of your best work is confidential. Four PR asset types do not require client disclosure.

1. Annual threat research reports. Producing an annual "State of Web3 Security" report, with original data on vulnerability classes, on-chain exploit patterns, and attack trends, is the single most effective PR asset a security firm can build. Immunefi publishes this category of research and gets cited in The Block, CoinDesk, and mainstream tech press every year. The report generates coverage at launch, functions as a media reference throughout the year, and compounds in LLM citation footprints. Ground the data in on-chain analysis. Publicly available transaction data is your raw material, and it is verifiable by any journalist who wants to check your methodology.

2. Exploit post-mortem commentary. When a major exploit hits, and the pace has accelerated, with DeFi losses surpassing $750 million in the first months of 2026, your researchers should publish detailed technical breakdowns within 24 to 48 hours. Not speculation. Not hot takes. Technical root-cause analysis of what went wrong, based solely on on-chain data that is publicly visible. This positions your firm as the authoritative source on exactly the kind of story that MIT Tech Review and Wired are assigning. The key discipline: maintain strict neutrality. Do not blame the protocol or the auditors who reviewed it. Explain the architecture, the failure mode, and what a different design choice would have prevented.

3. Educational bylines. Op-eds that explain complex Web3 security concepts for non-technical audiences land in Wired, MIT Tech Review, and Forbes when they are framed around systemic risk, not product promotion. The editorial pitch that works: here is why the same cross-chain verification assumption keeps enabling nine-figure exploits, and what the architecture of a genuinely secure bridge actually requires. That angle serves the publication's audience. A pitch that begins with your firm's credentials serves no one but you.

4. Proactive bug bounty transparency. If your firm operates a bug bounty platform, publish aggregate data on payouts, submission volume, and vulnerability severity distribution on a quarterly basis. Chainalysis publishes on-chain forensics data and gets cited globally. Immunefi publishes bug bounty data and earns recurring coverage. This category of voluntary disclosure, without revealing any individual client details, signals institutional maturity and gives journalists recurring story hooks tied to your brand.

The Legal and Relational Lines You Cannot Cross

Web3 security PR has hard limits that a generic PR agency will not know about and will not ask about.

Never disclose a client vulnerability before the patch is live. Even with the protocol's permission, if there is any possibility that a malicious actor could use your disclosure to exploit an un-patched system, the reputational and legal exposure is catastrophic. This applies even if the journalist promises not to publish until an agreed embargo lifts.

The protocol owns its announcement. If your firm audited a protocol that was subsequently exploited, even if the exploit was in code you did not audit, you should not issue public commentary without coordinating with the protocol team first. The legal exposure is significant, and the relational damage is permanent.

Attribution of stolen funds is a legal claim. On-chain forensics can identify wallet clusters, transaction patterns, and mixing behaviors. The jump from "this wallet received the stolen funds" to "this entity stole the funds" requires legal precision. Any public attribution in your research or media commentary needs legal review before publication. Getting attribution wrong, or making it prematurely, creates defamation exposure and can compromise active law enforcement investigations.

Respect the embargo culture. The crypto journalist community is smaller than it appears, and embargo breaks travel fast. If you give a journalist an embargoed briefing and a competitor outlet publishes before the agreed lift time, the damage to your media relationships is lasting. Build the embargo coordination discipline that token launch PR firms have developed, but apply it with the additional sensitivity that security disclosures require.

The Publications That Validate Institutional Credibility

Not all coverage is equal for a security firm pitching enterprise protocols, institutional investors, or CISO-level decision makers. The media placements that move the needle on institutional credibility are:

MIT Technology Review: validates technical depth and independent research
Wired: validates relevance to mainstream technology risk conversations
The Record (Recorded Future): validates cybersecurity-native credibility with InfoSec audiences
CoinDesk and The Block: validate crypto-native authority with protocols and investors
IEEE Security and Privacy (for published research): validates academic rigor with enterprise security buyers

The mistake that most Web3 security firms make is over-indexing on crypto-native media and under-indexing on the crossover publications that institutional buyers actually read. A CISO evaluating your firm for an enterprise blockchain security engagement reads Wired and MIT Tech Review. They do not follow CoinTelegraph.

Build the earned-media footprint that matches your actual buyer. If your buyers are institutional, your media map should look more like a cybersecurity firm's than a DeFi protocol's.

The Fractional PR Advantage for Security Firms

One reason most Web3 security firms have weak PR programs is that their options are limited. Generic Web3 agencies do not understand responsible disclosure. Traditional InfoSec PR firms do not understand on-chain mechanics. In-house hires cost more than the PR problem warrants at the early stage.

The fractional model works particularly well for security firms because the PR need is episodic and high-stakes. Deep expertise is needed during a responsible disclosure event, a major exploit that creates commentary opportunities, or a funding announcement. It is not needed for a full-time retainer producing weekly press releases that no security journalist will read.

A fractional PR partner who understands both the cybersecurity disclosure framework and the Web3 media ecosystem can execute the earned-media flywheel described above without the overhead of a full-service agency or the misalignment of a generic Web3 shop. The security sector carries premium retainer budgets for exactly this reason: the PR complexity is real, the downside risk of getting it wrong is significant, and the compounding upside of building a credible researcher-as-source media presence is substantial.

The firms that build it early, before the next nine-figure exploit creates an inbound media frenzy, are the ones that answer the journalist's call when it matters most.

Web3 Protocol Post-Hack Trust Recovery: The 90-Day Communications Playbook

Shilika — Sun, 21 Jun 2026 15:30:17 +0000

Web3 Protocol Post-Hack Trust Recovery: The 90-Day Communications Playbook

The hack itself rarely kills a protocol. What kills it is the silence that follows.

The data makes this brutal to ignore. Twelve Web3 hacks were reported in April 2026 alone, and social engineering now accounts for 74.7% of total hack losses, up from 28.7% in 2021. Average annual fund recovery has stayed below 10% since 2020. And yet technical incident response continues to eat nearly all of the post-hack budget, while the communications work, the thing that actually determines whether a community stays or dissolves, gets jammed into a single all-hands tweet.

This playbook is not about patching contracts. It is about the earned-media and community-trust rebuild that happens in the 90 days after an exploit, written for protocol founders and CMOs who have already survived the breach and now need to survive the narrative.

Why Most Protocols Lose the Communications Battle

Protocols that collapse after a hack rarely fail because the exploit was uniquely catastrophic. They fail because they follow a predictable, losing pattern of communication.

The three observable post-hack communication patterns are:

Pattern 1: Collapse. Radio silence for 24 to 72 hours, then a single technical post-mortem that addresses no user losses, followed by gradual team departure and token death. No designated spokesperson. No cadence. No acknowledgment that real people lost real money. Typically accompanied by the founder going dark on X.

Pattern 2: Struggle. Sporadic updates driven by community pressure rather than a plan. Public communications are reactive, inconsistent in tone, and often contradict each other across Discord, X, and Substack. The team is clearly overwhelmed. Journalists who would have written sympathetic recovery narratives stop calling.

Pattern 3: Recovery. A designated spokesperson is on-camera within hours. Updates follow a cadence, not improvised when things get loud. User losses and the remediation path are named clearly. The team uses on-chain transparency as a proof mechanism, not just a gesture. Media are briefed proactively, not chased reactively. The story that emerges in week six is the one the team actually wrote.

The gap between Pattern 2 and Pattern 3 is almost never technical competence. It is communications architecture.

The Four Case Studies: What They Actually Did

Bybit (February 2025): The Recovery Benchmark

When $1.5 billion in ETH was drained in what became the largest cryptocurrency heist on record, Bybit's CEO was on a public livestream within hours of detection, confirming the breach, detailing what was known, and explicitly assuring users the exchange remained solvent and could cover losses 1:1. By February 23, just 48 hours after the hack, all deposits and withdrawals had resumed to normal levels. Within 72 hours, Bybit completed a full proof-of-reserves audit that was published publicly.

The communications decisions that mattered: one designated spokesperson (the CEO), a public livestream instead of a written statement, an explicit 1:1 loss guarantee made verbally before a formal financial plan existed, and industry coordination surfaced publicly by naming Bitget's 40,000 ETH deposit and the $42.89 million in frozen funds as evidence of ecosystem support. Bybit's openness helped prevent the panic and speculation that triggers bank runs. The team understood that silence is never perceived as responsible caution in crypto. It is perceived as guilt.

Euler Finance (March 2023): The Comeback V2

Euler's $197 million flash loan exploit could easily have been a terminal event. The team imposed a communications blackout during the negotiation period, a deliberately strategic choice that protected their ability to recover funds, and it worked. The attacker ultimately returned the full amount. But the more instructive part of Euler's recovery is what happened next: the team chose not to relaunch V1. Instead, they used the incident as a forcing function to build V2, running 45 audits with 13 security firms over seven months. The V2 launch was accompanied by an incentive program designed around community discussions and opposition to points campaigns. Euler's TVL eventually crossed $1 billion. The lesson: the hack became part of the founding narrative of a better product. The communications job was to make sure the rebuild story landed before the distrust narrative hardened.

Ronin Network (March 2022): Reimbursement as the Message

The Ronin bridge hack, a $625 million breach attributed to Lazarus Group through a phishing attack on a Sky Mavis engineer, had one advantage Euler did not: the team made the commitment to full user reimbursement immediately and publicly. A $150 million raise led by Binance was announced within days and framed explicitly as a compensation mechanism. The bridge was rebuilt, the validator set was expanded, and the team published a detailed blog post describing both how the attack occurred and the steps being taken. The network reopened in June 2022 after full security audits and has since hosted multiple games and crossed millions of wallets. The on-chain rebuild was visible. The communications made the rebuild legible.

The Collapse Pattern: What Both Protocols Avoided

Contrast those cases with protocols that go dark. Two weeks after a significant bridge hack, the interface remains unavailable with no update. Forum posts from the team dry up. The community Discord fills with increasingly hostile speculation that the team is preparing to rug. By the time a post-mortem appears, trust is already gone. This is the collapse pattern, and it is preventable with basic communications architecture.

Days 1 to 7: Containment and Control

The first 72 hours determine whether you become Bybit or the collapse pattern. The decisions are operational and communications simultaneously.

The spokesperson rule. One person talks publicly. Engineers go silent externally. The spokesperson does not need to have all the answers. They need to be present, human, and honest about what is and is not known. A CEO on a livestream saying "we know this happened, we are covering losses 1:1" is worth more than a perfect technical statement published 48 hours later.

The first statement. Publish within two to four hours of detection. It needs five things: an acknowledgment that an incident has occurred; what is known about the scope; what is not yet known; what actions the team has already taken; and a timeline for the next update. Do not speculate about the attacker. Do not apologize in a way that sounds like you are preparing to exit. Do not make it technical-first. Users want to know about their funds, not your architecture.

The media briefing. Within 24 hours, brief two or three journalists who cover DeFi security, not with a press release, but with a call. Give them what you know, acknowledge what you do not, and tell them your next milestone. Journalists brought into the tent early are less likely to write the "disappearing team" story later.

On-chain proof. If you can demonstrate any freezes, coordination with exchanges, or forensic tracking activity, surface it publicly and on-chain. Transparency that lives in a verifiable ledger is more credible than a statement.

Days 8 to 30: Narrative Architecture

The second phase is about constructing the story that will dominate search results, community memory, and journalist files for the next year. Most teams skip this and wonder why the hack still comes up six months later in every piece of coverage.

The full post-mortem. By day 14 at the latest, publish a full post-mortem covering: the attack vector in plain English, not just technical notation; what detection and response looked like in real time; what is being done to ensure it cannot happen again; and what the user remediation plan is. Euler's post-mortem, published on their own blog in narrative form, became a reference document that demonstrated both competence and accountability. It is still cited.

The user remediation announcement. If you have a reimbursement or compensation mechanism, announce it before the community demands it. Protocols that wait for community pressure to announce compensation appear to have been forced into it. Protocols that announce proactively, even if the path is imperfect, appear to be in control. Sky Mavis's commitment to full reimbursement before the mechanism was finalized was communications-smart, even before the $150 million round was complete.

Earned media sequencing. Do not do a general press release. Brief journalists first in days one to three. Publish the full post-mortem on your own channels on day 14. Then proactively pitch the recovery narrative, not the hack narrative, to tier-two and tier-one crypto outlets starting in week three. The pitch is not "we were hacked." The pitch is "here is what we learned and what we have built since." Euler's V2 launch was a story about what came after the hack. That is the story you are building toward.

Discord and governance channels. Designate a community lead whose only job for 30 days is monitoring and responding to governance forums, Discord, and Twitter threads. Community questions that go unanswered for more than 24 hours become speculation. Speculation becomes accepted fact if it is not contradicted.

Days 31 to 60: Proof Mechanisms

This is the phase most teams skip entirely. The announcement work is done. The post-mortem is published. The team stops communicating. And the community, which is watching on-chain, sees that nothing has actually changed.

The audit publishing cadence. Do not announce that you have commissioned audits. Publish the results, in full, as they arrive. If you have commissioned three separate security firms, publish each one separately with context about what they examined and what they found. Euler spent seven months running 45 audits across 13 firms before launching V2 and made that process visible. That visibility was the communications work.

The on-chain transparency report. Publish a monthly, structured on-chain transparency report. It should cover: funds status (including recovered, frozen, and outstanding amounts); security improvements implemented with on-chain verifiable evidence where possible; changes to governance structures; and any community commitments and their current status. This is the most underused tool in post-hack communications. It is also the one that institutional investors actually read before re-entering a position.

Bug bounty announcement. Announce an expanded bug bounty program with specific amounts and clear scope, and push it through relevant security channels (Immunefi, Code4rena, security-focused social media). This is both a real security measure and a communications signal: it demonstrates confidence in the new architecture while inviting scrutiny.

Days 61 to 90: The Rebuild Narrative

The final phase is about converting the hack from a thing that happened to you into part of a founding story that demonstrates resilience and accountability. Earned-media coverage can reinforce that story, but only if you create the narrative infrastructure first.

The founder op-ed. Between days 60 and 75, pitch a founder-bylined op-ed to a tier-one crypto outlet. The angle is not "here is what we survived." The angle is "here is what we learned about building secure systems in an era where social engineering accounts for the majority of losses." It references your specific experience without centering the hack. It positions you as a practitioner with earned insight, not a victim with a story.

The proof-of-reserves cadence. If you are an exchange, establish a monthly public proof-of-reserves that lives permanently in your content archive. Bybit completed its first proof-of-reserves audit 72 hours after the hack. Make that into a permanent institution, not a one-time reassurance.

Community governance milestones. By day 90, there should be at least one governance action, a vote, a proposal, or a ratified security framework, that originated from community input post-hack. This is not just governance hygiene. It is the most powerful signal that the community has moved from spectators to participants in the rebuilt protocol.

The Earned-Media Stack: What to Pitch and When

The typical post-hack media pitch fails because it is pitched at the wrong moment (too early, when the story is still "hack"), to the wrong people (general crypto news desks rather than DeFi-specialist reporters), with the wrong angle (defense rather than insight).

The correct sequence works like this. In days one to three, run embargo briefings for three to five DeFi-beat journalists. Not a pitch. A briefing. You are giving them the story on background, building credit for later coverage. In week three, treat your post-mortem as a media asset. Structure it so that any journalist can pull three or four facts that become news hooks. Publish on your own channel first, then brief journalists on the key findings. In month two, pitch the security audit results as a standalone story. "Protocol completes audits with multiple firms after breach" is a legitimate news hook that tier-two outlets will cover. In month three, go with the op-ed and the rebuild narrative. The story of what the protocol looks like now and what it learned.

The goal by day 90 is that when a journalist searches your protocol's name, the most recent coverage is about the rebuild, not the hack.

What This Actually Takes

The 90-day framework is not complicated. Most of the individual components, a spokesperson, a post-mortem cadence, a monthly transparency report, a bug bounty, are well understood. What fails is the sequencing, the consistency, and the willingness to keep communicating when the immediate crisis pressure has lifted.

The protocols that recover do something that the protocols that collapse do not: they treat communications as an ongoing operational function rather than a crisis-only deployment. They understand that investor skepticism increases with silence, not with disclosure. They know that communities fill information vacuums with the worst possible interpretation, and they do not give those vacuums time to form.

The institutional capital that the industry needs depends on protocols demonstrating they can build and sustain trust even after a catastrophic event. The sub-10% fund recovery rate is the decisive barrier keeping institutions out. The security work matters. The audit work matters. But neither is legible to a community without the communications architecture to make them visible.

That is what the 90-day playbook builds: legibility, in the only window that actually matters.

How to Turn a Web3 Conference Appearance Into 30 Days of Earned Media: The

Shilika — Sun, 21 Jun 2026 04:30:16 +0000

How to Turn a Web3 Conference Appearance Into 30 Days of Earned Media: The Post-Event PR Playbook

You spent months securing the speaking slot. You built the deck, rehearsed the talk, flew to the venue, and delivered it on stage. You got the applause, the LinkedIn post, the handful of hallway conversations. And then, like most Web3 founders, you went home, opened your inbox, and moved on.

That is precisely where the PR value evaporates.

A conference appearance is not a deliverable. It is source material. The on-stage moment is the raw material for bylines, podcast pitches, journalist follow-ups, LinkedIn narratives, and Substack essays, if you activate it deliberately in the days and weeks that follow. Founders who treat the talk as the finish line extract maybe 10% of the available PR value. Founders who treat it as the starting gun can run a full month of compounding earned media off a single 20-minute panel.

Here is the exact post-event sequence to do that.

The 48-Hour Rule: What Has to Happen Before the Momentum Cools

There is a narrow window after any conference where you have natural relevance. Journalists are still filing stories about what happened. Their editors are still commissioning conference-adjacent content. Other attendees are still mentally present. Your name is still attached to the event in people's short-term memory.

That window is roughly 48 hours.

Within that window, two things must happen.

First: reach out to every journalist you had real contact with. Not a blast email. Send an individual message that references the specific conversation you had. If you met someone at the side event and discussed how your take on DeFi liquidity mechanics challenges the consensus view, say that. Remind them of the idea, not just the encounter. Keep it to three sentences: reference the moment, reference the idea, offer to go deeper. This is the move that converts a hallway exchange into a source relationship.

Second: send your talk transcript or slide deck to your PR person, or to yourself, with a single instruction: identify the three strongest standalone claims. Not topic areas. Specific, falsifiable, memorable assertions. Something like "stablecoin liquidity on L2s will consolidate to two protocols by Q3 2026" is a story angle. "The stablecoin market is evolving" is not. Those three claims are your content pillars for the next 30 days.

Mining One Talk for Three Distinct Story Angles

Most founders treat their conference talk as one story: "I spoke about X." But a well-constructed 20-minute talk contains at least three separable editorial angles, each addressable to a different publication and journalist beat.

Angle 1: The contrarian data claim. Identify the moment in your talk where you presented an on-chain metric, a trend figure, or a market observation that cuts against the prevailing narrative. That is your pitch to data-focused journalists and analyst-oriented newsletters. Package it as "here is what the data actually shows, and here is why the consensus has it backwards." This angle belongs in outlets like The Block, Blockworks Research, or DL News, where a chart and a thesis can anchor a standalone story.

Angle 2: The structural or policy implication. If your talk touched on regulation, protocol design trade-offs, governance mechanics, or interoperability questions, any topic with policy or infrastructure stakes, that is a separate pitch to journalists covering the regulatory and institutional beat. The framing shifts from "here's what the market is doing" to "here's what builders and regulators need to understand about where this is heading." This angle often travels to mainstream crypto finance desks, and occasionally to Bloomberg or FT crypto reporters who are actively looking for expert sources with operational credibility.

Angle 3: The founder or builder narrative. The human story embedded in your talk: why you built what you built, what you got wrong before you got it right, what the category looks like from the inside. This angle belongs in long-form profiles, podcast conversations, and founder-focused newsletters. It is the least urgent and the most durable. It is the byline you pitch to CoinDesk's opinion desk, the Substack essay you write for your own publication, the 45-minute podcast episode you record in week three.

Separating these three angles is what allows a single conference appearance to generate multiple distinct pieces of coverage. Not variations on the same quote, but genuinely different stories told in genuinely different editorial contexts.

The Week-One Journalist Follow-Up Sequence

By days three through five, you should be following up with journalists more broadly. Not just the ones you met in person, but the ones who covered the conference or who cover your category and were present at the event. The timing matters here. Reaching out within two to four days of the conference ending keeps you within the editorial cycle for post-event coverage while ensuring you are not the founder who sends a pitch the moment they land home.

The structure of these follow-up pitches is specific.

For journalists who covered the event: Reference a piece they filed from the conference. Acknowledge what they got right. Then add a dimension they did not have. A data point, a follow-up observation, or a "the day after the conference, here's what the smart money was actually talking about" framing. Journalists who have already written one story about a topic are often looking for the second angle, not a repeat.

For journalists who cover your beat but were not at the event: Lead with the insight, not the credential. The fact that you said something on stage at TOKEN2049 is context, not the pitch. The pitch is the specific claim you made and why it is editorially valuable to their audience right now. Attach the stage as social proof, not as the hook.

For journalists on beats you want to enter: A conference appearance gives you a natural warm opener. You are not cold-pitching from nowhere. You are a speaker who just contributed to a discourse they cover. Lead with that framing briefly, then give them the angle. Never lead with your company name or funding round. Lead with the idea.

One practical note: do not follow up more than twice on any single pitch. The goal is to convert one or two journalists into ongoing source relationships, not to close a sale. Journalists who respect their source's time become reliable over the long term.

Repurposing the Talk Video: A Four-Format Content Engine

Most conference talks produce a video recording. Most founders let that video sit on YouTube or the event's content platform, unlisted and unloved. Here is how to turn that 20-minute recording into a month of owned and earned content.

Format 1: LinkedIn essay (Week 1). Pull the strongest two minutes from your talk. Find the moment where you made your most specific claim or told the most concrete story. Write a 600-word LinkedIn post that opens with that claim, expands it with the reasoning you gave on stage, and closes with an implication or question. Link to the full talk at the end. This does three things: it surfaces the content to your professional network, it creates a citable version of your argument that journalists can reference, and it positions you as someone who continues to develop ideas publicly rather than dropping them at the podium.

Format 2: Substack or long-form essay (Week 2). One of your three story angles should become a 900 to 1,200-word essay published under your own byline, either on your Substack, your company blog, or as a contributed piece to a third-party publication. The essay should go deeper than the talk: add the nuance you could not fit into 20 minutes, respond to the counterargument you anticipated in the Q&A, cite the additional data that has surfaced since the event. This is the version that will get indexed by search, picked up by LLM citations, and referenced by journalists who are writing about your topic six weeks from now.

Format 3: Podcast pitch (Weeks 2 to 3). A conference appearance with a specific thesis gives you a highly pitchable podcast premise. You are not proposing a generic founder interview. You are proposing a specific conversation around a specific claim that you can document and defend. Pitch three to five shows in your category with a one-paragraph topic brief that leads with the argument, not with your bio. The best pitches reframe the conference insight as a question the podcast's audience has been asking and that you are uniquely positioned to answer.

Format 4: Short-form clip amplification (Weeks 1 to 4). Extract two or three 60 to 90-second clips from the talk recording. Look for moments with a clear setup, a punchy insight, and a natural end point. Post these on X and LinkedIn with a brief framing comment. These clips do not need to go viral. They need to keep your name circulating in the feeds of the journalists, investors, and peers who were already paying attention before the talk. Consistency of presence matters more than any individual piece of performance.

Using Conference Momentum to Advance an Embargo or Exclusive Pitch

If you have an announcement in progress, a funding round, a partnership, a product launch, a protocol upgrade, a recent conference appearance creates a specific tactical opportunity. You now have demonstrated public visibility and a documented editorial voice. Journalists are more receptive to embargo pitches from founders they can point to as active contributors to a conversation, not just companies seeking coverage.

In the two to three weeks after a major conference, you can credibly write to a journalist: "I was on stage at [event] last week discussing [topic]. The announcement I am bringing you connects directly to what I argued there. I would love to brief you under embargo before we go live." This framing does two things: it gives the journalist narrative continuity, because your announcement is the next chapter of a story they have been tracking, and it positions the embargo as a reward for their prior coverage interest rather than a request for a favor.

Be precise about what the embargo offer includes. A specific lift time, a commitment not to offer the exclusive to competing publications simultaneously, and a clear offer of additional access, such as a call with the founding team, access to on-chain data, or an additional source who can corroborate the claim. Journalists who are offered genuine editorial value honor embargoes. Journalists who feel like they are being handed a press release in advance do not.

The 30-Day Post-Event Content Calendar

Here is what systematic activation looks like mapped to a calendar:

Days 1 to 2: Personalized journalist follow-ups to in-person contacts. Internal claim extraction from talk transcript.
Days 3 to 5: Broader journalist outreach to conference beat reporters and category journalists. LinkedIn essay drafted and published.
Week 2: Substack or byline essay published. Podcast pitches sent to three to five targeted shows. First short-form clip posted.
Week 3: Follow up on podcast pitches. Begin embargo or exclusive briefings if an announcement is in motion. Second short-form clip posted.
Week 4: Publish the third content piece, either a second byline on a different angle, a LinkedIn carousel built from talk data, or an AMA in a community channel relevant to your category. Start building toward the next conference or media moment with learnings from this cycle.

The logic of this calendar is compounding. Each piece of content creates another surface for discovery. Each journalist touchpoint deepens the relationship. Each clip circulates your argument to people who did not attend the original talk. By day 30, the talk itself is almost irrelevant. What matters is the month of evidence you have created that you are a consistent, credible source worth following and quoting.

The One Mistake That Kills Post-Event PR

Most founders who fail to activate post-event PR do not fail because they lack content. They fail because they treat each PR opportunity as an isolated event rather than a link in a continuous chain.

The founders who compound their visibility over time are the ones who decide, before they take the stage, what they want to be known for, and then use every subsequent surface to repeat and develop that same spine of ideas. The conference talk, the follow-up byline, the podcast episode, the LinkedIn essay, and the journalist source relationship are all expressions of the same underlying thesis. They reinforce each other. They make each subsequent piece of coverage easier to get, each journalist follow-up warmer, each future speaking slot more likely to be offered rather than applied for.

A single conference appearance, activated with intention, does not produce 30 days of coverage. It produces the first 30 days of a compounding media footprint. One that, if you maintain the discipline, keeps paying PR dividends long after the event itself has been forgotten.

That is the playbook. The question is whether you will still be building it when the next conference is announced, or starting from zero again.

Web3 Founder Substack Strategy: How to Build a Newsletter That Journalists

Shilika — Sun, 21 Jun 2026 03:30:16 +0000

Web3 Founder Substack Strategy: How to Build a Newsletter That Journalists Quote and VCs Forward

Here is a scenario that plays out regularly in Web3 in 2026: a journalist on a deadline needs a credible founder voice on a DeFi narrative. They search their inbox. The name that surfaces isn't the one with the loudest X presence. It's the founder whose Substack they've been reading for six months because it's reliably accurate, analytically sharp, and free of hype. That founder gets the quote. The others get passed over.

This is the compounding logic behind a well-run founder newsletter, and it's why the tactic has moved from "nice to have" to a core component of institutional credibility for Web3 builders in 2026.

Why Substack and Not X or LinkedIn

Every channel has a job. X is fast and contextual but algorithmic, impermanent, and increasingly noisy. LinkedIn skews toward soft professional signaling. Substack does something different: it delivers long-form, archivable, searchable content directly to opted-in inboxes without the platform controlling what gets seen.

The ownership dynamic matters enormously. On Substack, unlike other platforms, founders own their audiences. They are not renting a database. They are building a dedicated list they can tap into and lean on as they grow. That list is exportable at any time, which means the asset survives platform pivots.

The platform has also grown into something more than a newsletter tool. It now functions as a hybrid publishing, social, and community environment. Substack's Notes feature creates a short-form social layer sitting inside the same ecosystem as long-form posts, podcasts, and live conversations. For a Web3 founder, that means one presence can serve multiple touch-points across a single institutional audience.

The structural shift is real. The locus of reputational leverage has moved away from legacy media gatekeepers and toward direct channels and creator-led platforms. Founders now build credibility through newsletters that demonstrate expertise and deliver stories directly into the inboxes of industry peers, prospective partners, and investors. The newsletter doesn't replace earned media. It amplifies it.

Position Before You Publish

Most founder newsletters fail not because the founder can't write, but because they start publishing before they've answered a harder question: what does a journalist or a VC actually want from this specific voice?

The answer is almost never general Web3 commentary. There's too much of that already. The newsletters that become citable assets occupy a narrow lane with genuine analytical depth. A few frameworks that work in Web3:

The Infrastructure Interpreter. You build in a specific technical layer: ZK, modular infrastructure, RWA tokenization. Your newsletter translates what's happening at the protocol level into implications for markets, regulation, and institutional adoption. Analysts at funds can't write this. Journalists covering the beat would love to quote it.

The On-Chain Data Narrator. You publish original observations from on-chain data your team tracks anyway: TVL trends, wallet behavior, liquidity migration, framed as analytical commentary rather than self-promotion. The moment your data starts appearing in third-party research reports, the newsletter has become a primary source.

The Regulatory Translator. If your project sits at the intersection of institutional adoption and compliance (stablecoins, RWAs, tokenized funds), a newsletter that parses MiCA, the GENIUS Act, or CFTC guidance in plain language for operators becomes indispensable to the people making capital allocation decisions.

The test: if a journalist could get the same content from ten other newsletters, yours has no citation value. If your perspective is a genuine function of your position, technical knowledge, or access to proprietary signals, it becomes a source.

Structure for Institutional Readers

The people who cite and forward institutional newsletters are busy. They scan before they read. Structure accordingly.

Issue architecture that works for a Web3 founder newsletter:

A sharp lead take (200 to 300 words): Your primary analytical position on one thing that matters right now. This is what gets forwarded. It should be citeable as a standalone paragraph.
The evidence layer (300 to 500 words): On-chain data, protocol metrics, regulatory text, or market context that supports the lead take. This is what makes journalists comfortable attributing the quote.
Second-order implications (200 to 300 words): What this means for a sector, for institutional allocators, for regulatory timelines. This is what VCs forward to their portfolio.
A brief operational note (100 words): What your team is building, watching, or planning in response, kept factual and not promotional.

The format signal matters as much as the content. A newsletter that looks like a research note (clearly dated, properly sourced, with distinct analytical sections) reads as a professional document. One that looks like a founder diary reads as marketing.

Cadence is also a positioning signal. A biweekly newsletter that ships on time for two years says something different than a sporadic one. Readers form habits, and habits turn occasional readers into the people who recommend you when a journalist asks who understands this space.

The Cross-Promotion Loop with Earned Media

One of the highest-leverage uses of a founder Substack is as a flywheel for earned media, and the two tracks reinforce each other. Most founders treat them as separate channels and leave most of the value on the table.

From newsletter to press. When you publish a piece of original analysis on Substack, that post creates a citable, permanent URL. A journalist researching the topic finds it. They quote it with attribution, which drives new readers to the newsletter. Those readers include other journalists and analysts, which increases the probability of the next organic mention.

A founder who has published a sustained body of work in credible formats becomes the person reporters call for reaction commentary on industry news. That produces additional coverage without additional pitch effort. Your Substack archive is the evidence base for that credibility claim.

From press to newsletter. When you land coverage in a tier-1 outlet, the newsletter is where you go deeper. "We spoke with [outlet] about [topic]: here's what we couldn't fit into 800 words." That edition drives readers who found you through the press piece to subscribe, converting one media moment into a durable subscriber.

Using the newsletter as an embargo vehicle. A less obvious use, and one that requires care, is using your Substack to signal context around announcements before they go wide. A newsletter issue published the morning an embargo lifts, with the analytical framing for what the announcement means, gives subscribers (many of whom are journalists or analysts) a head start on interpretation. This earns goodwill without breaking any agreements. It positions your voice as the authoritative interpreter of your own news.

Building the Subscriber List That Matters

Subscriber count is a vanity metric for this use case. A Web3 founder newsletter with 800 subscribers, 400 of whom are journalists, analysts at crypto funds, and protocol operators, is worth more than one with 20,000 passive readers who signed up during a token hype cycle.

Build the list deliberately:

Seed with warm distribution. Your team's network, existing investor contacts, advisors, and ecosystem partners are the first 100 to 200 subscribers. These are high-quality readers who will forward issues to peers.

Cross-promote within the Substack network. The platform's Recommendations feature creates a discovery loop. According to data from Substack in early 2026, 40% of all new subscriptions now come from inside the Substack network. A few well-chosen recommendation swaps with newsletters that reach adjacent institutional audiences (DeFi research, infrastructure analysis, regulatory commentary) can build a high-quality list efficiently without paid acquisition.

Use conference presence as a subscription moment. Speaking slots, panel appearances, and side-event conversations all produce a natural call to action: "I cover this in more depth in my newsletter." The friction-free nature of Substack's subscription flow makes in-person conversion easy.

Repurpose strategically on LinkedIn and X. Pull the lead take from each issue as a native post on LinkedIn, where it reaches the institutional audience who may not yet be subscribers, with a link to the full piece. Doing this consistently turns single issues into multi-channel distribution events without adding meaningful production time.

Converting Readers to Relationships

The subscriber list is not an end in itself. It is a warm relationship infrastructure. The conversion mechanics here are different from a consumer newsletter selling subscriptions. A Web3 founder's newsletter converts in three ways:

Journalist citations. A journalist who has subscribed for six months before a major news event knows your analytical voice. When they need a quote or a source, they reach out. This is inbound media relations. It takes patience to build and is almost impossible to fake.

VC due diligence acceleration. When an investor receives a cold introduction to your project, one of the first things they do is research your founder presence. A Substack archive that demonstrates consistent, substantive thinking about the problem space functions as an extended pitch deck without the sales energy. It shows pattern recognition, analytical discipline, and communication ability: three things that are hard to convey in a thirty-minute intro call.

Retainer and advisory conversations. For founders who provide services or advisory work alongside their core project, the newsletter functions as a consistent demonstration of value that doesn't require active selling. A reader who has been absorbing your thinking for three months and then receives an issue that directly addresses a problem their organization faces will reach out. The newsletter creates the context that makes the conversation easy.

The key discipline is patience. New clients almost always refer to a newsletter as a loyal reader. The relationship forms before the commercial conversation, not during it.

The Honest Constraints

Substack is a rented platform. The platform's branding sits on top of yours, customization is limited, and the platform takes 10% of any paid subscription revenue. It also lacks native embargo management tools, CRM integration, and the downloadable media kit infrastructure that a full press office requires.

The practical implication: run Substack as the primary distribution and relationship layer, but maintain your own domain-hosted content (a press page, an archive of op-eds and data reports) as the authoritative record. The Substack newsletter builds the audience and the habit. The owned property carries the institutional credibility markers that journalists and investors look for when they go deeper.

The other constraint is time. A newsletter that ships on time, maintains analytical quality, and stays tightly positioned is a meaningful production commitment. Many founders launch with energy and let cadence slip after four to six issues. The ones who build lasting credibility treat publication dates as non-negotiable. Consistency is not a soft benefit. It is the product.

What the First Six Months Actually Look Like

Weeks 1 to 4: Define the positioning lane. Write three draft issues before publishing any. Establish format, cadence, and the core analytical frame you'll return to repeatedly. Seed the list with your first 100 warm subscribers.
Months 2 to 3: Ship consistently. Prioritize quality over frequency. Begin cross-promoting with two or three complementary newsletters. Start repurposing lead takes on LinkedIn.
Months 4 to 5: Use existing speaking opportunities to build the subscriber list. Begin noting which issues generate the most direct replies from high-value readers. That feedback shapes future positioning.
Month 6: Evaluate. Are journalists finding you? Are inbound conversations increasing? Is the archive functioning as a reference document for your analytical positions? If not, the positioning or format needs adjustment, not the frequency.

A Web3 founder newsletter is not a quick credibility shortcut. It is a compounding asset. The issues you publish in month one are still findable, still citeable, and still shaping what journalists and investors think about you when they do their research a year later. That permanence is the point. It is what separates a well-built Substack from every other channel you're likely already using.

How to Pitch Naavik, Blockworks Research, and The Block's Research Desk: A Web3

Shilika — Sun, 21 Jun 2026 02:30:16 +0000

How to Pitch Naavik, Blockworks Research, and The Block's Research Desk: A Web3 Founder's Guide to Analyst and Newsletter Placement

Most Web3 founders have a simple media map in their heads: CoinDesk for announcements, CoinTelegraph for volume, Decrypt for retail. That mental model is not wrong. It is just incomplete. It leaves out the channels where institutional capital actually does its reading before it writes a cheque.

A placement in Blockworks Research's deep-dive coverage, a mention in Naavik's Digest, or a feature in The Block's research arm reaches a smaller audience, but one with a higher average AUM than anything a token news wire can replicate. These are the formats that fund managers forward to their investment committees. Getting into them requires a fundamentally different pitch strategy than the one you would use for a breaking-news reporter.

This guide maps the landscape, explains what each format actually rewards, and gives you a repeatable pitch framework for earning analyst and newsletter coverage rather than purchasing it.

Why Analyst Coverage Moves Institutional Needles Differently

News journalism and analyst research serve different functions in an investor's workflow. A journalist covers what happened. An analyst explains what it means and whether it is worth capital.

That distinction matters enormously for a Web3 founder. When a Blockworks Research analyst initiates coverage on your protocol, that report goes into the reading queues of fund managers, allocators, and LPs who have already filtered out everything that lacks quantitative substance. When a Naavik deep-dive deconstructs your Web3 gaming title, it lands in the inboxes of hedge funds, private equity desks, and studios that subscribe to that newsletter specifically because it offers game-business analysis rather than hype.

The audience is smaller. The conviction level is higher. The downstream effect on investor perception, often including smart contract TVL or token price discovery, is disproportionately large compared to the placement's word count.

The broader context reinforces why this matters now. Institutional cryptocurrency adoption has crossed critical thresholds in recent years, with spot ETFs, digital asset treasuries, and tokenized RWAs all becoming standard institutional portfolio items. That means the analysts covering your sector are being read by a more sophisticated, better-capitalised audience than ever before. Getting in front of that audience through earned research coverage, rather than sponsored content, sends a signal about your project's credibility that paid placements simply cannot replicate.

Understanding Each Outlet's Research Logic

Before pitching any of these outlets, you need to understand what they are actually optimising for. Each outlet has a distinct research mandate.

Blockworks Research

Launched as a subgroup within Blockworks, the research desk operates with a specific mandate: be ahead of the narrative curve. Its analysts produce forward-looking, actionable long-form thematic and asset-specific research, on-chain data analysis, governance tracking, and investment memos aimed at institutional capital allocators.

The key word in that mandate is "forward-looking." Blockworks Research analysts are not trying to document what has already happened. They are trying to identify what sophisticated institutional audiences should be watching before it becomes a mainstream narrative. They cover topics before they become widely discussed, specifically to provide actionable signals to subscribers.

What this means for a founder: your project needs to fit a thesis the analyst is already building, or introduce a thesis they have not yet encountered. Announcing last quarter's numbers will not get you in the door. Providing on-chain data that illuminates a structural trend in your category, data the analyst cannot easily pull themselves, will.

Blockworks Research analysts are literally tasked with reaching out to founders and investors as part of their primary research process. They are looking for founders willing to provide deep protocol access, governance context, and economic model clarity. The question is whether you are visible and legible enough to be the founder they find.

The Block Research Desk

The Block's research operation sits at the intersection of institutional-grade data journalism and financial analysis. Its editorial positioning is deliberately research-led and markets-focused, with a readership weighted toward institutional and professional audiences. It rewards substance: data, structure, balance-sheet reality. It is unforgiving of hype.

The Block's research team produces comprehensive annual outlook reports, sector-specific analysis, and collaborative research with institutional counterparties. These reports cover everything from DeFi protocol mechanics to macro-level institutional adoption trends, and they rely on founders to provide primary source data, context, and access to support the analysis.

The Block also operates a pro-tier advisory service that has advised institutions on first crypto investments and helped publicly traded companies develop go-to-market strategies. That context matters: the team covering your sector might simultaneously be briefing pension funds on whether your category is investable. The quality bar for founders who want to be featured as positive case studies in that analysis is correspondingly high.

Pitch The Block research desk with numbers and named sources. Not narrative. If you can provide verifiable on-chain data, governance metrics, or user-cohort analysis that adds dimension to a story the research team is already building, you have a legitimate path to coverage.

Naavik

Naavik operates as a gaming research, consulting, and advisory firm. Its editorial output, including the Naavik Digest newsletter, deep dives, and podcast, functions as the public face of that research practice. Its analysts cover game mechanics, business models, company strategy, and market trends across the gaming industry, with a dedicated Web3 gaming vertical.

The Naavik research model is notably different from crypto-native research shops. Naavik has consulted with hundreds of gaming studios, financial institutions, and ecosystem companies. Its readers include hedge funds, private equity firms, venture capital funds, family offices, and investment banks. When Naavik covers a Web3 gaming title, its analysis is informed by deep comparative context across the games industry, not just the crypto gaming subset.

That makes Naavik coverage particularly valuable for Web3 gaming founders who want to earn credibility outside the crypto-native echo chamber. A Naavik deep-dive that places your game within the broader gaming business context, comparing your monetisation mechanics to established free-to-play titles and benchmarking your retention curves against mobile gaming norms, is the kind of third-party analysis that gaming investors and game studios at the growth stage actually trust.

High-Authority Crypto Newsletters

Beyond these institutional-facing research outlets, there is a tier of independent newsletters, some on Substack and some on their own platforms, that punch above their weight with specific institutional audiences. The Defiant has journalism-grade DeFi coverage with a readership that includes DeFi-native builders and investors. Bankless has become a primary reference for Ethereum ecosystem coverage. The Bitwise Weekly CIO Memo reaches financial advisors and institutional allocators at the intersection of traditional finance and crypto.

These newsletters share a common characteristic: their coverage is driven by editorial interest, not by commercial relationships. Getting a mention requires either providing genuinely useful primary data, being the subject of an analysis the writer was already planning, or becoming a trusted source the writer can reference across multiple stories.

The Four-Part Analyst Pitch Framework

The mechanics of pitching an analyst or newsletter are different from pitching a news journalist. A journalist covers what just happened; an analyst covers what is happening structurally. Your pitch needs to operate at that structural level.

1. Identify the thesis the analyst is already building

Before you pitch, do your research. Read the last three to five pieces the analyst has published. What category argument are they developing? What data gaps do they repeatedly acknowledge? What questions do they pose but leave unanswered? Your pitch should position your project as evidence for a thesis they are already investigating, or as a counterpoint that complicates a thesis they have already published.

A cold pitch that says "here's what we've built" is easy to ignore. A pitch that says "you argued in your March piece that X structural dynamic is emerging in this category. Our on-chain data over the past 90 days either confirms or complicates that, and I think you'd want to see it" is much harder to dismiss.

2. Lead with data the analyst cannot easily find themselves

Research analysts have access to on-chain data aggregators, protocol dashboards, and governance trackers. What they do not have is your internal metrics: cohort retention data, wallet-level engagement patterns, governance participation rates that are not yet surfaced in public tooling, or unit economics from your treasury model.

The most powerful analyst pitches offer proprietary data that adds new dimension to a story the analyst is already trying to tell. Be specific: "Our DAU/MAU ratio over the past two quarters, broken down by on-chain vs. off-chain wallet cohort" is a more compelling offer than "we have strong engagement metrics."

3. Make the access offer explicit and generous

Analysts operate on time pressure. The single biggest friction point in analyst outreach is the gap between a founder's willingness to share information in principle and their actual availability for a substantive conversation.

Your pitch should make the access terms explicit: offer a 30-minute call with direct access to your protocol's lead researcher or technical co-founder, not a PR intermediary. Offer to share a summary data package in advance so the call can focus on interpretation rather than background. Offer to make yourself available for follow-up questions without a PR gate.

That last point matters more than founders realise. Analysts frequently need to fact-check small technical details at 11pm before publishing. If your PR team introduces a 24-hour approval cycle for every response, the analyst learns quickly that you are not a primary source. You are a PR-managed account.

4. Calibrate exclusivity to the format

For research analysts at Blockworks or The Block, exclusivity of data access is more valuable than exclusivity of announcement. You can offer to share your proprietary data set with one analyst for a defined window, say two weeks, before releasing it publicly. That gives them time to build a substantive piece without permanently locking up your data.

For newsletters like Naavik or independent Substack writers, a more valuable offer is an early-access briefing: let the writer talk to your team and review your metrics before you announce publicly, so they can publish analysis that goes deeper than anything a same-day press release could support.

Common Mistakes That Kill Analyst Pitches

Pitching announcements as analysis. Analysts are not news desks. Sending a press release to a Blockworks research analyst and asking them to "cover" your product launch will simply train them to filter your emails.

Leading with valuation and token price. Institutional research outlets actively avoid coverage that can be read as price promotion. Starting your pitch with "our token has 3x'd since launch" is the fastest way to signal that you do not understand the format.

Sending through a PR intermediary for first contact. The most effective analyst relationships are direct. A pitch routed through a PR agency's distribution system, addressed to "Research Team," has near-zero conversion. Find the specific analyst covering your category, their bylines are public, and write to them directly.

Offering generic commentary rather than proprietary data. "I'd be happy to discuss trends in our space" is not an offer. Analysts can find generic commentary everywhere. The offer needs to be specific and exclusive: data they cannot easily get elsewhere, or access to a founder perspective that goes deeper than the public record.

Building an Ongoing Analyst Relationship

A single placement is valuable. An ongoing relationship with an analyst who follows your project over time is transformative. Analysts who have covered a project in depth become reference points for institutional investors who reach out for diligence. They become the people who cite your project as a case study in their broader category analysis. They become the intermediaries who, when they receive investor questions about your category, mention your project as an example of a team doing things right.

Building that relationship requires the same discipline as any institutional relations programme: consistent transparency, proactive data sharing when you have news, prompt responses when analysts have questions, and a willingness to engage honestly with critical coverage rather than simply chasing positive mentions.

The Web3 founders who earn durable analyst coverage treat these relationships the way TradFi companies treat sell-side analyst relationships. They view analysts as a long-term investor communication channel, not a transactional PR target.

The Opportunity Most Founders Are Missing

The search results for "how to pitch Blockworks Research" or "how to earn Naavik coverage" currently return almost nothing useful. That gap is the opportunity. While most Web3 founders compete for the same ten CoinTelegraph bylines and the same two CoinDesk news hooks, the analyst and newsletter tier sits comparatively uncrowded and comparatively underserved.

Your next institutional investor may never read a CoinTelegraph article about your project. But they almost certainly read the research reports their analysts forward every week. Getting into that reading queue, through data, access, and genuine analyst relationships, is the PR investment that actually moves the needle at the institutional level where your next round gets decided.

Web3 Gaming PR: How to Pitch Decrypt, Polygon Blog, and Gaming-Native Outlets

Shilika — Sun, 21 Jun 2026 01:30:16 +0000

Web3 Gaming PR: How to Pitch Decrypt, Polygon Blog, and Gaming-Native Outlets Without Sounding Like a Press Release

There's a stack of unread pitches in every gaming journalist's inbox right now. The subject lines are almost identical: "Revolutionary GameFi Token Launch," "Play-to-Earn Economy Disrupts Traditional Gaming," "Announcing Our Groundbreaking NFT Partnership." Most of those emails will never be opened past the first sentence. The ones that do get opened almost never result in coverage.

This isn't because the journalists are indifferent to Web3 gaming. It's because the pitches are written for the project's marketing team, not for an editor who has to justify every story to a skeptical audience that has been burned by speculative hype before.

The good news: the gap between what most GameFi founders pitch and what gaming-focused journalists actually want to cover is wide enough that getting it right creates a real competitive advantage. This guide breaks down the outlet-by-outlet logic, the data points that make pitches reactive and fast, and the cultural framing that converts a token announcement into a story worth publishing.

Why Generic GameFi Pitches Fail on First Read

Crypto editors at major outlets receive between 200 and 500 pitches a day. Most get scanned for less than five seconds. The triage is ruthless: source check, subject line specificity, news value. If any of those three fail, the pitch gets archived. Body copy never gets a chance.

The most common failure mode isn't bad writing. It's the wrong unit of content. Most founders pitch announcements, not stories. On their own, announcements rarely meet the threshold of what editors or readers care about unless framed within a broader narrative. A token launch is not a story. A token launch that reveals something unexpected about player behavior, ecosystem dynamics, or the future of in-game ownership might be.

The current editorial environment adds another layer of difficulty. The 2021 to 2022 cycle, dominated by the simplistic play-to-earn model, promised players a living wage for mundane tasks. It was an economic mirage that collapsed under inflationary tokenomics and a lack of genuine gameplay loops. Gaming journalists who covered that era have become structurally skeptical. It's no secret by now that most gamers hate crypto. There's been heavy community backlash around announcements such as Ubisoft Quartz. Editors know their readers know this history. A pitch that reads like it hasn't absorbed that context will be rejected before the journalist even reaches the ask.

The landscape is genuinely changing, which creates opportunity. Web3 gaming is long past its glory days as an industry-defining narrative. For the last two years, the market has been continuously punishing hollow token-first playbooks, and now studios are forced to build entertaining games that can stand beside traditional titles, with blockchain as part of the stack rather than the entire story. That shift is exactly the kind of editorial tension journalists can write into. A project that embodies the new model has a story. A project still pitching the old model has a press release.

What Decrypt Actually Covers in the GameFi Vertical

Decrypt is best for consumer dApps, GameFi projects, tutorials, and deep-dive blog posts. That editorial focus tells you something important: the publication's gaming coverage is user-facing, not investor-facing. The audience is someone who might actually play your game, not a VC running a portfolio screen.

Decrypt wants accessible storytelling that connects crypto to broader culture, business, or technology trends. That's a meaningful constraint. A pitch about token vesting schedules won't get traction at Decrypt unless it connects to something a non-crypto-native gamer cares about. A pitch about how a small team in the Philippines built a game that outperforms mainstream mobile titles on retention metrics might.

The practical implication: lead with the human story or the cultural hook, not the mechanics. If your game has a community that formed around it, talk about the community. If your DAU numbers tell a counterintuitive story about player behavior, lead with that. If a Web2 gamer wouldn't understand why your story matters within the first sentence, rewrite it.

Decrypt's preferred formats also shape the pitch. Deep-dive blog posts and tutorials reward projects that have something to explain. If your game introduced a novel economic mechanic, a piece that teaches readers how it works is more likely to land than a straight announcement. Consider pitching the explainer angle directly, offering to provide exclusive data or founder access that makes the piece possible.

How to Reverse-Engineer the Editorial Angle at Naavik and Delphi Digital

Naavik describes itself as a gaming research, consulting, and advisory firm, and its content reflects that positioning. The publication produces detailed structural analyses of distribution, monetization, and market dynamics. A pitch that arrives as a token announcement will be ignored. A pitch that offers exclusive data, an interview with a founder building against conventional wisdom, or a case study that challenges a Naavik thesis has a real shot.

Naavik's research analyzes challenges in the gaming industry, focusing on distribution and user acquisition, and explores opportunities in the Global South. That framing is a direct signal. If your game is seeing traction in Southeast Asia, Latin America, or Africa, that's a Naavik-relevant story. Mobile dominance is accelerating. The next 100 million blockchain gamers will come from mobile-first markets in Southeast Asia, Latin America, and Africa. A founder who can speak to what's actually driving that adoption, with real numbers, is providing editorial value.

Delphi Digital's gaming coverage operates at the intersection of research and investment thesis. Their audience is sophisticated and data-hungry. Demand from networks for healthy on-chain user metrics is only going to rise. Blockchain gaming generated, on average, 23x more on-chain transactions compared to DeFi protocols. This will make gaming a key candidate for boosting on-chain metrics. A pitch to Delphi that leads with on-chain transaction data, DAU growth curves, or wallet retention cohorts is speaking the language that analysts at that publication actually use. A pitch that leads with "we're excited to announce" is not.

Gaming-Native Substacks and the Pitch That Travels Sideways

There's a tier of GameFi coverage that lives between the crypto majors and mainstream gaming press: the independent researchers, gaming-focused Substack newsletters, and niche Discord communities that reach the exact audience most Web3 gaming projects want. In 2025, independent Substack writers, crypto KOLs, popular YouTube bloggers, and podcasters are a crucial part of effective Web3 PR. You can gain traction and credibility within specific chains, ecosystems, or developer communities here before larger outlets take notice.

These outlets often have small readership by traditional metrics but outsized influence on the people who matter most to a gaming project: other developers, early adopters, and the community members who become recruiters for your player base. A well-placed deep-dive in a respected gaming Substack frequently produces more meaningful traction than a brief mention in a tier-one outlet.

The pitch approach is different here. Independent researchers want access and transparency. They're building an opinion, not just covering an event. Offer them early data, a founder interview with no talking-point constraints, or access to your community metrics over time. The relationship produces better coverage and a genuine advocate who will reference your project in future pieces.

Leading With Player Metrics, Not Tokenomics

The single most common pitch mistake in GameFi is leading with token details. Tokenomics are not a story. They are a technical specification. Smart agencies help founders translate technical or tokenomic events into stories that matter to journalists, for example: "Daily Active Users up 212% in 30 days," or "Top DAO proposal draws 8,000 votes." This data-backed storytelling helps bridge the gap between blockchain's transparency and the media's hunger for legitimacy.

The metrics that resonate with gaming journalists in 2026 are player-centric, not market-centric. Day-7 retention rate. Session length by cohort. Monthly active wallets versus daily active wallets. The ratio of players who stay when token rewards decline. Games that lead with quality and treat blockchain as background infrastructure are showing retention numbers that match or beat top Web2 titles. If your retention data tells that story, say so in the subject line.

MapleStory N, Nexon's Web3 take on its beloved franchise, reached nearly 2 million lifetime accounts within months of its May 2025 launch. Retention during testing hit 54% at day seven, which is unusually high for any online game and exceptional for a blockchain title. That's the kind of number that opens doors. Not because it's a blockchain number, but because it's a gaming number that would make any games journalist pay attention.

Build a running list of journalist-ready data points before you send a single pitch. Update it weekly. Track the metrics that gaming press cares about: DAU, D7 retention, session length, NFT secondary market volume as a proxy for player engagement, and community governance participation as evidence of actual stakeholder investment. When a story breaks that your data speaks to, you can pitch reactively within hours, not days.

The Outlet-by-Outlet Pitch Structure

Decrypt: Three-sentence email. Subject line leads with the player metric or cultural hook. Reference the journalist's most recent gaming piece by name. Offer exclusive access to a specific founder, data set, or community event. No attachment, no wire-style header, no "About the Company" boilerplate.

Naavik: Pitch a research collaboration angle, not an announcement. Offer to provide on-chain data or internal metrics that would strengthen a piece they'd write independently. Frame your project as a case study that proves or challenges a thesis their readers already hold. Keep it to four sentences and a bullet list of the three most compelling data points.

Delphi Digital: Lead with on-chain metrics. Wallet growth curves, transaction volume relative to DeFi comparables, token velocity, staking ratios. Delphi's analysts are building investment theses. Your job is to give them data they don't already have.

Gaming-native Substacks: Offer access, not an announcement. Propose a founder interview with a specific editorial angle already roughed out. Show that you've read the newsletter closely enough to suggest where your story fits in their existing editorial arc.

For all of these: send to one or two journalists by name, not to a list. Personal pitches outperform broadcast pitches by a factor most founders underestimate. And the best pitches are short, reference the journalist's specific recent work, lead with the newsworthy element rather than the company name, and make the story angle immediately apparent.

Building a Reactive Pitch Infrastructure

The projects that earn consistent coverage aren't the ones with the biggest announcements. They're the ones that have a live archive of pitch-ready data points and can respond within hours when a story breaks that intersects with their project.

The practical system: maintain a shared document with the current version of your five most compelling metrics. Review and update it every two weeks. Tag each metric with the outlet type it's most relevant to (Delphi gets the on-chain data; Decrypt gets the player story; Naavik gets the market dynamics angle). When a major studio shuts down, when a funding drought story breaks, or when a new platform announces blockchain gaming support, you have a pitch drafted in twenty minutes instead of two days.

Timing matters: a pitch arriving the week after a relevant news event will receive more attention than the same pitch sent at random. The reactive pitcher who can say "I saw your piece on the Web3 gaming funding drought, and here's what our retention data shows about which projects survive it" is in a different category from the founder mass-distributing an announcement on a Tuesday morning.

What is collapsing in Web3 gaming is the speculative layer, token-first projects built for extraction rather than gameplay. Games that lead with quality and treat blockchain as background infrastructure are showing retention numbers that match or beat top Web2 titles. That's the editorial frame gaming journalists are actively using right now. Position your project inside it, with numbers that hold up, and the pitch almost writes itself.

The Trust Prerequisite

No pitch strategy closes the trust gap if the project behind it can't support scrutiny. Editors are cautious about exaggerated claims, vague tokenomics, and unverifiable teams. Regulatory scrutiny, scams, and market volatility make journalists and influencers more selective. Crypto projects must approach PR with clearer messaging, stronger validation, and more consistent storytelling than other startups.

That means having a public audit, being willing to share raw retention data rather than cherry-picked highlights, and having a founder who can speak on the record about what hasn't worked, not just what has. Gaming journalists are not adversarial, but they have been burned often enough that they'll probe for inconsistencies. The projects that earn long-term coverage relationships are the ones that show up consistently with honest data, available spokespeople, and a story that gets more interesting as the project matures.

The pitch is the beginning. The coverage is the outcome of everything that happens before it: the product decisions, the metrics, the community, and the willingness to treat journalists as partners in a story rather than distribution channels for an announcement.

Web3 Founder Thought Leadership Without a Ghost-Writer: A DIY Framework for

Shilika — Sun, 21 Jun 2026 00:30:16 +0000

Web3 Founder Thought Leadership Without a Ghost-Writer: A DIY Framework for Technical Builders

Most thought leadership guides assume you'll outsource the writing. Hire an agency, brief a ghost-writer, hand over your brain dump, and wait for polished copy that sounds vaguely like you. Except it doesn't, and your community notices.

Technical Web3 founders tend to resist this model, and for good reason. Your credibility is built on protocol depth. When an op-ed under your byline describes a governance mechanism in language that would embarrass a junior dev, the damage is real. A ghost-writer who doesn't understand calldata compression or validator incentive design isn't just unhelpful. They're a liability.

The alternative is not "write everything yourself from scratch on a blank page at 11 PM." The alternative is a structured extraction system: a way to turn the thinking you are already doing, including post-mortems, architecture decisions, and governance debates, into media-ready content without losing the signal that makes your voice worth reading.

This is that system.

Why Technical Founders Have a Structural Advantage (That They Waste)

Editors at crypto-native publications receive dozens of pitches per week from comms professionals who are excellent at framing and poor at substance. What they don't receive enough of is copy that contains an actual insight. Something derived from running a protocol, not from reading about running one.

Your structural advantage is that you have witnessed things. You've watched a governance proposal pass with 63% quorum only to get blocked at execution. You've run a liquidity incentive campaign and observed the exact block at which mercenary capital rotated out. You know the difference between the invariant that held and the one that nearly didn't.

That is your raw material. The framework below converts it into publishable form.

Step 1: Build Your Thesis Document

Before any individual piece of content, you need a single living document (call it your Thesis Doc) that articulates your point of view on the one or two questions that matter most in your area of the protocol stack.

A Thesis Doc is not a whitepaper. It is not a roadmap. It is 600 to 900 words of opinionated conviction organized around three questions:

What is broken or misunderstood in your corner of Web3 right now?
What will be true in 18 to 36 months that most builders are not yet pricing in?
What have you personally learned from building that contradicts the conventional wisdom?

Write this document badly the first time. That's fine. The purpose is to externalize a coherent worldview so you have something to mine. Most founders discover, when they try to write this, that they have three or four different theses competing with each other. That's useful information. Pick one.

Your Thesis Doc becomes the source of truth for every piece of content you produce for the next six months. An X thread is a paragraph from the Thesis Doc, expanded. A conference talk is the whole document, structured with evidence. A CoinDesk op-ed is the thesis applied to a news hook. A podcast appearance is the Thesis Doc delivered conversationally.

One document. Six months of content.

Step 2: The Content Extraction Audit

Once per month, spend 45 minutes doing a Content Extraction Audit. Scan the last 30 days of your own work product and ask: what did I write or say that contained a genuine insight?

Look in these places:

Internal post-mortems and incident reports. These are gold mines. A well-written post-mortem contains a root cause analysis, a sequence of decisions under uncertainty, and a set of hard-won lessons. Every one of those is a publishable idea.
Governance forum posts. If you wrote a 400-word reply to a governance thread, that reply contains an argument. Arguments are articles.
Engineering blog drafts. Even abandoned drafts contain at least one concept that non-technical readers would find illuminating.
Slack and Discord messages. Search your own messages for the week you were most animated. That's where your genuine opinions live.
Investor update emails. The section where you explain a setback or a strategic pivot often contains your most honest and interesting thinking.

Tag each item with a rough content type: Observation (something you noticed), Argument (something you believe that others don't), or Explainer (something you understand that your audience doesn't yet).

Step 3: The Conversion Map, From Source Material to Format

Different source materials convert naturally into different content formats. Here is the map.

Post-Mortem Converts to a CoinDesk Op-Ed

A governance or technical post-mortem is already structured as a narrative with a problem, a sequence of decisions, and a resolution. To convert it to an op-ed pitch:

Strip the internal jargon and technical specifics down to one paragraph of context.
Restate the core lesson as a claim that applies beyond your protocol. Not "our multisig threshold was misconfigured" but "multi-sig governance fails at the same structural point across DeFi protocols, and the pattern is predictable."
Connect the claim to a news hook from the last 30 days, such as a similar incident at another protocol, a regulatory comment, or an academic paper.
Write a 150-word pitch to the editor. The pitch should contain: the hook (why now), the argument (your specific claim), and proof of standing (one sentence about what you've built).

CoinDesk's opinion section, The Block's contributor program, and Blockworks' editorial desk all accept unsolicited pitches from founders with operational standing. They are not looking for PR copy. They are looking for a point of view backed by experience. A post-mortem is exactly that.

Engineering Blog Post Converts to a Decrypt Feature Pitch

An engineering blog post typically explains how something works. A Decrypt feature story typically explains why something matters. The conversion move is to extract the implication, not the implementation.

If your engineering post explains how you re-architected your oracle to reduce latency, the feature pitch becomes: "Slow oracles are a hidden attack surface in DeFi lending. Here is what we learned building a faster one, and why it changes the security assumptions every protocol should be making."

When pitching a Decrypt reporter, target the specific reporter who covers your beat rather than the editor in general. Frame it as a story tip, not a pitch. "I think there's a story here that would interest your readers, and I've built something that could give it a concrete angle." Reporters do not want founders telling them what to write. They want founders who can point them at an interesting problem and then be a useful source.

Governance Debate Converts to an X Thread Series

Governance debates compress well into X threads because they already have two sides. The format: open with the counterintuitive position (not the one you'd expect the protocol founder to take), spend three or four tweets building the steel-man of the opposing view, then pivot with the data from your vote and what it actually showed.

This structure works because it demonstrates that you've actually thought about the problem rather than just advocating for your own interests. Technical credibility on X is built by being someone who updates their view when confronted with evidence.

One governance thread per month, posted during a period when the debate is live in the broader ecosystem, compounds quickly.

Step 4: Build a Six-Month Content Calendar from One Thesis Doc

Here is a concrete content calendar structure based on a single well-formed Thesis Doc. This assumes one core thesis, three supporting arguments, and a handful of concrete examples from your own build.

Month	Output	Format	Source Material
1	Establish the thesis	Long-form X thread (12 to 15 tweets)	Thesis Doc, section 1
2	First supporting argument	Op-ed pitch to tier-1 crypto outlet	Governance post-mortem
3	Technical explainer	Engineering blog post adapted for Decrypt pitch	Architecture decision
4	Counter-intuitive take	X thread plus podcast pitch	Governance debate
5	Data-backed claim	Original research thread plus byline pitch	On-chain data you have access to
6	Synthesis	Conference talk proposal	Everything above

The conference talk proposal in month six is not arbitrary. It is the culmination of six months of public reasoning. By month six, you have a record of consistent thinking on a topic, which is exactly what program committees look for in a speaker who isn't a household name yet.

Step 5: The Pitch Stack, Run It Simultaneously Not Sequentially

One mistake technical founders make when they do try to pitch: they pitch one outlet, wait for a rejection, then pitch the next. The result is that a piece of content that was timely in January gets placed in March, if at all.

Build a pitch stack. For any given idea, identify three outlets or formats simultaneously:

Tier-1 outlet pitch (CoinDesk, The Block, Blockworks): highest bar, slowest timeline, most valuable placement
Mid-tier or niche outlet (Decrypt, Unchained, a protocol-specific publication): faster turnaround, more receptive to technical depth
Owned channel (your engineering blog, your X thread, your newsletter): publish here regardless of what the outlets decide

If the tier-1 pitch doesn't land within two weeks, escalate to mid-tier and publish the owned-channel version simultaneously. You keep the idea alive and in circulation without losing momentum waiting for a gatekeeper.

A Worked Example: DeFi Protocol Founder

Consider a founder who runs a lending protocol. Over three months, the protocol experienced a governance failure. A parameter change that passed on-chain was executed incorrectly, resulting in a brief window of incorrect collateral ratios. No funds were lost, but the incident was public.

Month 1: The founder writes an internal post-mortem. It's detailed, honest, and contains a structural insight: on-chain governance execution and off-chain parameter implementation are two separate systems that almost no protocol has formally synchronized. This becomes the thesis.

Month 2: They convert the post-mortem into a 900-word op-ed pitch for CoinDesk: "On-Chain Governance Passed. The Protocol Didn't Get the Memo. A Systemic Risk No One Is Tracking." The pitch includes data from five other protocols that have experienced the same gap. The editor commissions it.

Month 3: The op-ed runs. They post an X thread the same day expanding on one specific technical claim from the piece. The thread focuses on the architectural gap between governance modules and execution layers. The thread gets picked up by a podcast focused on DeFi infrastructure. They appear on the podcast six weeks later.

Month 4: They submit a conference talk proposal to a developer-focused conference. The title: "The Governance Execution Gap: What I Learned Running a Vote That Almost Broke Our Protocol." The proposal is accepted. They now have a speaking slot, a published byline, and a podcast appearance, all sourced from a single post-mortem written for internal use.

Total external writing time: approximately eight hours across four months.

The One Rule That Makes This Work

Everything in this framework depends on one precondition: you have to actually write your Thesis Doc.

Not a draft of it. Not a note that says "I should write this." The full 600 to 900 words, in your own voice, making a claim you would be willing to defend publicly.

Founders who skip this step find that every piece of content feels like starting from scratch. Founders who do it once find that they always know what to say next, because they know what they believe.

That document is the system. Everything else is distribution.

If you're at the stage where you have the thesis but need help converting it into a placed byline or a structured media strategy, that's the gap where fractional PR support is most useful. Not to replace your voice, but to handle the mechanics of placement so you can focus on the thinking.

DAOs and Decentralized Governance: The PR Playbook for When There Is No Single

Shilika — Sat, 20 Jun 2026 23:30:16 +0000

DAOs and Decentralized Governance: The PR Playbook for When There Is No Single Spokesperson

There is a question every crypto journalist silently asks before covering a DAO governance story: Who do I call?

The honest answer, "anyone with enough tokens can speak, but no one officially does," is not a PR strategy. It is a liability. The gap between how DAOs actually make decisions and how the outside world expects organizations to communicate is where reputations erode, coverage goes sideways, and institutional credibility collapses before a single vote is cast.

This post is a practical PR framework for DAOs. Not governance design theory. Not token-weighted voting mechanics. The actual communications infrastructure you need to build so that journalists, institutional investors, and token holders receive coherent, credible, timely information without you centralizing the thing you are supposed to be decentralizing.

Why DAO PR Is Structurally Different from Every Other Web3 PR Problem

Most Web3 PR is hard because the subject matter is complex. DAO PR is hard because the organizational form itself creates contradictions that standard communications playbooks were never designed to handle.

Consider the audience problem alone. A single governance vote lands differently for three completely different readers: a retail token holder who bought in six months ago and reads X threads, a developer contributor who lives in Discourse forums, and an institutional allocator who expects boardroom-level transparency and quarterly narrative consistency. The same announcement has to work for all three, and the framing that excites one audience can alienate another.

Then there is the spokesperson problem. Traditional PR logic says: identify a spokesperson, media train them, route all press inquiries through a single voice. DAOs, structurally, resist this. Founders and core contributors hold enormous informal influence even when the governance token distribution looks broad. Naming one person "the spokesperson" immediately invites the accusation that the DAO is not actually decentralized, which undermines the founding claim, spooks regulatory watchers, and gives critics a clean line of attack.

And then there is the speed problem. Community sentiment in a DAO can reverse in hours. A proposal that passes an informal temperature check on Monday can face a coordinated opposition campaign by Wednesday. A governance vote that looks settled can become a media story by Thursday if a single whale votes against it. Crypto journalists actively track governance votes, and coverage can reframe a proposal before the DAO itself has published an explanation.

None of this means DAO communications is impossible. It means you need a different architecture.

The Four-Layer DAO Communications Architecture

Layer 1: The Canonical Source of Truth

Before you touch media relations or spokesperson strategy, you need to solve a foundational infrastructure problem: your community does not know where to look.

Governance announcements scatter across Discord threads, Snapshot votes, Discourse forums, X posts, and governance forum discussions simultaneously. Members catch some updates and miss others. The vote opens on Snapshot while debate continues on the forum, and by the time many members find the active thread, the window to participate has already closed. This fragmentation does not just hurt participation. It creates a PR vacuum that outside observers, including journalists, fill with their own interpretations.

The fix is a single canonical governance hub that serves as the authoritative record. This is not a new product; most mature DAOs already use a governance forum. The PR discipline is in how you treat it. Every governance communication, including proposal drafts, discussion summaries, vote announcements, and outcome reports, must originate there first and link outward. Discord and X amplify. The forum governs.

Governance Announcement Template (pre-vote)

[PROPOSAL TITLE]: Community Discussion Open

What this proposes: [One-sentence plain-language summary]

Why now: [The problem or opportunity this addresses]

What changes if it passes: [Concrete, specific outcomes, not vague commitments]

What stays the same: [Explicitly state what is not affected, reduces fear-driven opposition]

Discussion period closes: [Date and time, with timezone]

Snapshot vote opens: [Date and time]

Where to weigh in: [Direct link to governance forum thread]

This template sounds simple. Most DAOs do not use one. The absence of a consistent structure is why proposals that should pass narrowly fail, and why journalists frame governance votes as "turmoil" rather than "deliberation."

Layer 2: The Credible Voice Without a Title

Here is the core tension every DAO communications strategy has to resolve: you need a credible human voice for media purposes, but you cannot appoint a "CEO" without undermining your decentralization narrative. These goals are not actually in conflict. But most DAOs handle the tension by doing nothing, which is the worst possible outcome.

The resolution is the contributor frame. Core contributors, foundation members, and active delegates are not spokespersons in the traditional sense. They are participants with deep context who speak to their own perspective, not on behalf of the protocol. This is a real and defensible distinction, and most crypto journalists understand it. The framing matters: "I am a core contributor and here is my read on what this proposal would mean" is factually defensible in a way that "I speak for the DAO" is not.

Practically, this means building a bench rather than a solo act. Identify three to five core contributors who are comfortable talking to press, understand the governance history, and are willing to be on call during major votes. This is not a media committee. It is an informal roster. Different contributors speak to different beats: a developer for technical questions, an economist or risk analyst for treasury and tokenomics questions, a community lead for sentiment and participation questions.

Many mature DAOs are already moving in this direction. Professional delegate frameworks with compensation and performance tracking are becoming standard at larger protocols, with delegates publishing governance reports and maintaining transparency dashboards. The same logic applies to communications: specialized contributor voices, not a single spokesperson, is both more authentic to the DAO form and more practically sustainable over time.

Separate protocol voice from personal voice. When a founder or core contributor posts on X, journalists will quote it regardless of what disclaimer is attached. Establish a clear internal norm: protocol-level communications happen in the governance forum. Personal analysis and opinion happens in personal channels. When a contributor writes a long thread about a proposal, they preface it as their personal read, not an official DAO position. This separation protects the DAO from having an informal statement treated as a binding commitment, and it gives journalists the attribution clarity they need.

The founder question. Most DAOs have a founding team that retains enormous informal influence even after token distribution. Journalists know this. Institutional investors know this. Pretending otherwise signals either naivety or deception. The better approach: founders can and should speak, as their own voice, with their personal perspective, about why they think a given proposal is or is not good for the protocol. This is not undermining decentralization. It is being honest about how governance actually works while respecting that the vote belongs to the community.

Layer 3: Contentious Vote Communications Protocol

This is where most DAO communications programs fall apart. The routine governance cycle is manageable. The contentious vote, specifically the treasury proposal opposed by a major delegate bloc or the parameter change that whale voters reject at the last minute, is what exposes whether you have a PR infrastructure or just a Discord server.

The first rule of contentious vote communications: treat it as a PR event, not a forum post. A contentious governance proposal that reaches Snapshot without a coherent public narrative will be defined by whoever frames it first, and that framing may come from an anonymous Twitter account, a disappointed delegate, or a journalist covering the vote.

The pre-vote window is your most valuable communications asset. In the week before a significant vote opens on Snapshot, publish three things:

A plain-language explainer in the governance forum, using the template structure above.
A short summary thread on X from a named core contributor, framed explicitly as their personal read.
A proactive media brief to two or three journalists who cover governance beats regularly, offering contributor access for background context.

That third step is the one most DAOs skip. Crypto journalists who cover DeFi governance are not waiting for press releases. They are watching Snapshot and governance forums in real time. A proactive background conversation before a major vote lets you provide context that shapes how the story is framed if it gets written. The alternative is a story written entirely from on-chain data and Twitter drama.

For close or contentious outcomes, speed matters more than polish. An honest statement published within hours of a narrow pass or a surprising result beats a legally reviewed statement published two days later. Specificity beats vague reassurance every time. Name what happened, why the result is legitimate, and what comes next for implementation. Silence reads as chaos. Even an imperfect statement reads as accountability.

For proposals that fail, communicate the same way. A failed vote is not a scandal unless you treat it like one. A one-paragraph post explaining what the proposal sought to do, that it did not reach quorum or majority, and what the next steps are (re-proposal with amendments, abandonment, further community discussion) keeps the narrative factual rather than allowing it to become a story about governance breakdown.

Layer 4: Media Relations for the Institutional Orbit

As DAOs grow their treasuries and attract institutional capital, the media relations problem shifts. Institutional investors do not read Snapshot. They read Blockworks, The Block, and occasionally Bloomberg or the FT. They expect consistent narrative, predictable communication cadence, and evidence that someone is minding the store even when the governance process is distributed.

Translate governance outcomes into institutional language. A "parameter change to risk thresholds" needs to be translated into what it means for protocol security, TVL, and tokenholder economics before it reaches an institutional audience. A treasury diversification vote is not just a governance outcome. It is evidence of treasury management discipline. Every significant governance decision has an institutional-investor-readable version; most DAOs never write it.

Create a governance summary cadence. Monthly or quarterly governance summaries, published in the forum, distributed via newsletter, and available to journalists on request, solve multiple problems at once. They give institutional investors a single document capturing major decisions and their rationale. They give journalists a reference resource. And they demonstrate the operational discipline that institutional allocators want to see before they take a position. The document does not need to be long. It needs to be consistent and on schedule.

Build journalist relationships before you need them. The reporters who cover DeFi governance are a small, identifiable group. They track protocols closely and have developed views about which DAOs communicate well and which go silent when things get complicated. Building relationships with two or three of these reporters before a major governance cycle, not to pitch stories but to offer background context and position contributors as knowledgeable sources, pays dividends when coverage is inevitable.

One tactical note for institutional positioning: governance history is a credibility asset. DAOs that can point to a public record of proposals, participation rates, vote outcomes, and treasury decisions over time are demonstrably more trustworthy to institutional allocators than those whose governance history lives in scattered Discord threads. Publishing structured governance summaries is not just communications hygiene. It is institutional investor relations.

The Three Communications Failures to Avoid

Fragmentation. Announcements scattered across Discord, X, Snapshot, and Discourse with no canonical source breed the "I did not see that" excuse that collapses participation and makes your community look ungovernable to outside observers. Pick a primary channel. Route everything through it. Cross-post summaries everywhere else.

Silence during controversy. When a contentious vote passes narrowly or a whale voting bloc acts against community sentiment, the instinct is to wait for things to settle before communicating. This is exactly wrong. The absence of a clear DAO voice gets filled immediately by speculation, mischaracterization, and FUD that is far harder to walk back than the original event.

The decentralization-as-excuse trap. "We do not have a spokesperson because we are decentralized" is not a PR strategy. It is a way of ensuring that every governance controversy gets covered on the terms of whoever is loudest in the room. Decentralization describes how decisions are made. It does not require that you refuse to explain those decisions in plain language to the outside world.

What Good Looks Like

The DAOs with the most credible external communications share a few observable characteristics. They have a canonical governance hub that is actually maintained and updated on a predictable schedule. They have a small bench of contributors who are comfortable with journalists and understand the difference between speaking personally and speaking for the protocol. They treat significant governance votes as PR events with advance preparation, not surprises to be managed after the fact. And they publish regular, structured governance summaries that give institutional-orbit readers what they need without forcing them to excavate Discord logs.

None of this is technically complex. Most of it is discipline, the kind of operational consistency that is easy to build when things are quiet and very hard to retrofit when a governance crisis lands at 11pm on a Sunday.

Build the infrastructure now. The contentious vote is coming.

Crypto Founder LinkedIn PR: The 90-Day Operating System for Institutional

Shilika — Sat, 20 Jun 2026 19:30:16 +0000

Crypto Founder LinkedIn PR: The 90-Day Operating System for Institutional Credibility

There's a meeting you don't know you've already lost.

A VC principal checks your profile while your cold intro email sits unread. A Bloomberg reporter quietly validates whether you're a credible source before responding to your PR partner's pitch. An exchange listing committee Googles the founding team. All three look at the same place first: LinkedIn.

And what do most crypto founders show them? Either nothing. A last-updated-in-2022 profile with "Blockchain Enthusiast" in the headline. Or something worse: a feed full of token price predictions, moon emojis, and reposted press releases that read exactly like the shill content institutional audiences are trained to ignore.

This gap is an opportunity. While every serious founder in fintech and SaaS has figured out LinkedIn, most Web3 builders are still treating it as optional. It isn't. In 2026, LinkedIn has become the primary credibility surface where institutional investors, VCs, and mainstream journalists quietly vet founders before taking a meeting or filing a story.

This post is the operating system you need to change that, across a deliberate 90-day arc.

Why LinkedIn Specifically? The Institutional Vetting Layer

X/Twitter is where crypto culture lives. Discord is where communities breathe. But neither platform is where allocators, compliance teams, and tier-1 journalists do their pre-meeting research.

LinkedIn sits in a different category. The platform has over a billion users, including 58 million companies actively engaging, making it uniquely fertile ground for Web3 professionals seeking to establish credibility with institutional investors, corporate partners, and regulatory bodies. Crucially, profiles of Web3 founders consistently see meaningfully higher engagement than company pages. In Web3, trust isn't in the company; it's in the individual.

There's also a structural advantage: the audience composition is different. Unlike X's fast-paced hype environment, LinkedIn's architecture minimizes noise and makes it ideal for credibility-building with institutional and mainstream professional audiences. VCs and journalists who would dismiss a crypto founder's X post as speculative will read the same founder's LinkedIn article with real attention, if it's positioned correctly.

Venture capital firms and institutional investors conduct extensive due diligence before committing to Web3 projects. Your media presence, or absence, significantly influences their perception of legitimacy and momentum. LinkedIn is a central input in that judgment.

The Profile Audit: Your Credibility Infrastructure

Before you post a single word, the profile itself must do its job. LinkedIn's 2026 algorithm enforces strict profile-to-content alignment. It cross-references the topics you post about against your professional background, job title, and listed skills. Post outside that alignment and your reach is throttled regardless of content quality. Your profile is no longer a static resume; it's a critical relevance-engine input.

The five elements that matter:

Headline: Not your title. Your thesis. "Building institutional DeFi rails for regulated custodians" is infinitely more useful than "CEO and Co-Founder at [Protocol]."
About section: One punchy paragraph on the problem you're solving, for whom, and why you have the right to solve it. No buzzwords. No token mentions.
Featured section: Your three best external signals. A tier-1 byline, a conference keynote video, a credible media mention. This is what a journalist or investor sees immediately after your headline.
Experience: Rewritten as a narrative of your earned expertise, not a job description list.
Skills: Must explicitly match the authority pillars you plan to own (more on that below). The algorithm uses this as a trust filter.

Spend real time here. A polished profile alone won't generate inbound opportunities, but a weak one will kill the credibility of everything you post.

Step 1 (Days 1 to 30): Identify and Own Your Three Authority Pillars

The most common mistake Web3 founders make on LinkedIn: posting everything. DeFi fundamentals one day, regulatory commentary the next, team culture the day after that. This scattered approach destroys the topical authority signal the platform uses to distribute your content.

Institutional credibility is built through specificity. Choose three authority pillars at the intersection of what you know deeply, what your target audience actually needs to understand, and what's genuinely underexplored in the conversation.

Strong pillar examples for Web3 founders:

Infrastructure and technical depth: The architectural decisions in your protocol, explained with intellectual honesty about the trade-offs.
Regulatory clarity: Translating emerging frameworks (MiCA, the GENIUS Act, evolving SEC guidance) into practical implications for builders and allocators.
Market structure: Where institutional capital actually flows in crypto and why; the mechanics traditional finance doesn't yet understand about on-chain assets.

Weak pillar examples to avoid:

"The future of Web3 is bright."
Token price commentary or market speculation.
Generic ecosystem cheerleading.

The strongest founder voices on LinkedIn in 2026 have clear theses on where infrastructure is overbuilt, where UX remains broken, and which narratives are misleading. That specificity is what makes journalists, analysts, and other founders treat you as a go-to expert rather than just another spokesperson.

During days 1 to 30, your only job is to draft a content brief for each pillar: the core argument, the audience it serves, the three to five sub-questions that sit beneath it, and the content formats you'll use to explore it.

Step 2 (Days 31 to 60): Build the Content Engine with the Right Formats

Once your pillars are defined and your profile is calibrated, you start publishing. But format selection matters enormously. The wrong format undermines otherwise good content.

The 2026 LinkedIn algorithm has shifted decisively toward depth over volume. A post that generates three thoughtful comments now outperforms one with thirty reactions. Saves carry significant weight, indicating to the algorithm that your content possesses evergreen, utilitarian value. Shares to direct messages are treated as a high-intent engagement signal, indicating content valuable enough to send one-on-one.

For Web3 founders targeting institutional audiences, the format hierarchy looks like this:

Document and PDF carousels (highest priority): Educational carousels, data-backed analysis, and genuinely useful frameworks generate the highest depth scores because users spend more time consuming and discussing them. LinkedIn's own data confirms that document posts drive higher dwell time. The performance gap is striking: document posts achieve roughly four times the engagement of other formats in real-world testing. Personal profile carousels also see 63% higher engagement than company page carousels, yet another argument for building under your name, not just the company handle.

Opinion posts (substantive text): Long-form posts built around a counterintuitive claim perform well when the argument is specific and well-supported. The best structure: a bold, specific hook in the first two lines (before the "see more" cut), a concrete argument backed by either data or first-hand experience, and a clear conclusion that forces a reaction. The hook matters more than anything else. The algorithm analyzes the first one to two sentences to determine whether your content deserves wider distribution.

Milestone posts with real context: Announcements dressed in insight. Not "We raised $X," but "We raised $X, and here is the one ecosystem dynamic we're betting on that most investors got wrong in their model." Context converts a self-promotional post into a genuine signal.

Format to avoid entirely: Posts with external links in the body. LinkedIn's algorithm penalizes off-platform links, reducing distribution by roughly 60%. Put links in comments.

Post cadence during days 31 to 60: three to four times per week, alternating between carousels (once a week) and substantive text posts. Consistency matters more than frequency. Gaps of more than ten days are read by the algorithm as declining relevance.

Step 3 (Days 61 to 90): The Compounding Layer, Ghostwriting, Media Crossover, and Inbound

By day 60, if you've executed the first two phases with discipline, you should have a body of content that demonstrates authority across your three pillars. Now you activate the compounding layer.

Ghostwriting effectively with a PR partner

The founder time constraint is real. Thirty to sixty minutes of strategic LinkedIn content every week, done properly, is more than most founders have available after running an active protocol. The right answer isn't to skip it; it's to build a production system.

Effective ghostwriting for a Web3 founder starts with a voice-capture session. A conversation, usually 45 to 60 minutes, where a PR strategist or ghostwriter extracts your actual opinions on each pillar, your war stories, your genuine predictions. They then translate those into content that sounds like you at your sharpest, not generic LinkedIn advice filtered through an AI model. The best agencies use AI as a drafting tool but have human strategists and editors creating the final output that sounds authentic.

The critical step most ghostwriting arrangements skip: every piece goes back to you for a reaction-read. Not editing. Just reaction. Does this sound like something you'd actually say in a partner meeting? If not, the voice-matching failed.

Triggering media crossover

By day 90, your LinkedIn body of work becomes your calling card with journalists. A reporter considering you as a source can now read three months of opinionated, well-structured content on the exact topics they cover. That's signal. It de-risks the quote for them.

Thought leadership compounds in a specific sequence. A quote in a tier-1 story today makes you likelier to get invited onto a podcast next month, which increases the reach of your next byline, which makes your next conference speaking submission far easier to approve. Each step makes the next one easier, but the sequence requires LinkedIn to be populated and consistent before media outreach begins.

Your PR partner should be using your LinkedIn archive actively. Pulling arguments from your posts as pitch angles for journalists. Surfacing your clearest explanations as supporting material for byline proposals. Tracking which of your posts are generating inbound DMs from relevant parties, a signal of emerging media interest before a reporter formally reaches out.

The inbound inflection point

For most founders running this system, the inbound shift happens somewhere between weeks 10 and 16. The first signals: journalists following you, then messaging you directly. VCs commenting on posts before scheduling calls. Conference organizers reaching out about speaking slots rather than requiring you to apply cold.

Building the compounding credibility that creates inbound media interest, investor recognition, and organic community growth typically takes three to six months of consistent execution. This timeline is not a bug. It is why starting now, before your next fundraise, your next token event, your next major announcement, matters so much.

What Destroys Institutional Credibility on LinkedIn

Since this is a playbook, it should also serve as a diagnostic. The following patterns are common among Web3 founders and read as red flags to institutional audiences.

Token price commentary: Anything that reads as a price signal, even framed as market analysis, will trigger the shill-detection instinct in every sophisticated investor and journalist. They've seen too many founders pump and exit.

Hype without specificity: "We're going to change finance" with no mechanism is noise. Specificity is the tell of someone who has actually thought it through.

Engagement bait: Tactics like "Comment YES if you agree" are now actively detected and penalized by the algorithm. More importantly, they look desperate to the exact audiences you need to impress.

Company-page reposting: Sharing your own company's press release as a personal post signals that you don't have original things to say.

Inconsistency: A three-week posting burst followed by six weeks of silence reads as reactive and unplanned. Institutional audiences notice when a project stops generating coverage.

The 90-Day Milestone Map

Phase	Days	Core Activity	Target Output
Foundation	1 to 10	Profile audit and rewrite; pillar definition	Optimized profile; three pillar briefs
Calibration	11 to 30	First posts, voice testing, engagement monitoring	8 to 12 pieces; baseline engagement data
Content engine	31 to 60	Weekly carousel plus three opinion posts; ghostwriting workflow running	20-plus pieces; first inbound signals
Compounding	61 to 90	Media crossover activation; LinkedIn archive used in pitch work	Journalist DMs, speaking invitations, pre-meeting profile views from VCs

The Final Thought: LinkedIn Is the Long Game You Should Have Started Last Quarter

Web3 PR often defaults to the launch spike. A big announcement, a media blitz, then silence until the next event. That pattern creates a credibility gap. Investors and journalists notice when a project stops generating coverage. One major push followed by silence reads as PR dependency rather than genuine authority.

LinkedIn, run as a genuine operating system rather than an occasional broadcast channel, is the antidote to that pattern. It creates a durable, searchable, compounding record of how you think. That record is available to every investor, journalist, and partner who wants to vet you before they respond to your email.

In a space where trust is the scarcest resource, that record is worth more than any press release.

Start building it now. The 90 days will pass regardless.

How to Get a Speaking Slot at TOKEN2049, ETHDenver, and Consensus: The PR

Shilika — Sat, 20 Jun 2026 18:30:17 +0000

How to Get a Speaking Slot at TOKEN2049, ETHDenver, and Consensus: The PR Strategy for Web3 Founders Who Want the Stage, Not Just a Badge

A speaking slot at a top-tier Web3 conference is not a marketing perk. It is a business development event with a two-to-three year compounding tail. The investors in that room will Google you the next morning. The journalists covering the conference will add you to their source lists. The podcast hosts in the audience will reach out within 48 hours. And the founders who heard you speak will remember that you were on stage, not just in attendance.

But here is where most founders go wrong: they treat the speaker application as the starting point. It is not. By the time you hit submit, the committee's mental model of you should already be formed. Your job is to build the credibility stack that makes the yes feel inevitable, and to use the speaking slot as a launch pad for a PR campaign that runs weeks before and after the event itself.

This is the playbook for doing exactly that.

Understanding the Stakes: Why These Three Events Matter

The numbers are not abstract. TOKEN2049 Singapore is projecting over 25,000 attendees representing 7,000+ companies, with more than 60% holding C-level or founder-level titles. The 2025 Singapore edition drew 25,000 attendees from 160+ countries, with 70% C-suite participation. A speaking slot at an event with that audience profile is not a vanity play. It is direct access to the decision-makers who fund, partner with, and write about companies like yours.

Consensus by CoinDesk operates at comparable scale, having welcomed over 500 speakers, 1,000 companies, and 25,000 attendees in 2025, with a programme spanning six stages and dedicated tracks for stablecoins, tokenization, and institutional adoption.

ETHDenver is a different kind of event entirely. Run by SporkDAO, a decentralized autonomous organization, it operates on a community-first, merit-based model rather than a corporate programme. The 2026 edition at the Stockyards Event Center drew over 25,000 participants from 125+ countries, with high-profile participants ranging from Vitalik Buterin's Ethereum roadmap keynote to the White House's first direct participation in a crypto conference. The community skews builder-heavy, which means your credibility currency is on-chain proof and technical depth, not just brand recognition.

Each event selects speakers through a fundamentally different mechanism. Getting that wrong is the most expensive mistake a founder can make.

How Each Event Actually Selects Speakers

TOKEN2049: Outbound-First, Relevance-Driven

TOKEN2049 is explicit about its process. The team receives a significant volume of inbound requests in addition to running its own outbound effort. The official guidance is blunt: submit early, be interesting, and be relevant. Applicants are asked to send an email detailing their preferred speaking role, the general topics they could cover, and relevant information about themselves.

That description has a critical implication. The TOKEN2049 programming team is actively hunting for speakers who fit themes they have already decided matter. Your application does not shape those themes. Your job is to map your expertise onto the themes they are already building content around, and to do so with enough specificity that you look like the obvious choice for a panel slot nobody else can fill.

For the 2026 Singapore edition, the dominant themes are real-world asset tokenization, institutional custody, AI-blockchain integration, stablecoin regulation, and DePIN models. If your protocol sits at any of those intersections, your pitch needs to be framed around the narrative tension in that space, not around your product's feature set.

The NEXUS Startup Competition is a parallel entry path worth knowing. Selection is merit-based, applying is free, and finalists receive all the perks of being a TOKEN2049 speaker, including access to the exclusive speaker reception and networking. For early-stage founders who have not yet built the media footprint for a main stage slot, NEXUS is the smartest way onto the stage, and it puts you in the speaker tier for every subsequent application.

ETHDenver: Community-Merit, Human-Review

ETHDenver's approach is structurally different. Applications are reviewed by Content Stewards, community members who assess submissions based on educational value, authentic perspective, and fit with the Summit themes the organizers have defined. The guidance is direct: invest thought and authenticity in your responses, and avoid automated responses such as those generated by AI tools. The committee explicitly values unique perspectives and genuine insights over polished but generic proposals.

For 2026, ETHDenver reorganized its programming into theme-based Summits covering areas like privacy and cryptography, governance, infrastructure, and DePIN. Every submission is evaluated against a specific Summit's focus. This means the first thing you need to do before applying is identify which Summit your expertise most naturally maps to, then write a proposal that could only have come from someone who has spent years building in that exact corner of the ecosystem.

ETHDenver also notes that community-merit-based content can be considered for featured sessions and keynotes. This matters. Your presence in the broader Ethereum developer community, on forums, in open-source repositories, in governance discussions, directly influences how Content Stewards perceive your application. Being accepted as a speaker does not automatically grant entry to the event, so plan the logistics accordingly. Speakers must also complete a separate General Admission Application.

Consensus by CoinDesk: Thought Leadership, Framed as Education

Consensus frames its selection process explicitly around amplifying the wisdom of the Consensus community and showcasing the industry's most important voices. To apply, founders propose engaging and relevant topics that exemplify their thought leadership. The editorial team at CoinDesk, which runs the conference, is evaluating whether your topic adds something to the conversation that their existing editorial coverage has not already exhausted.

That alignment with editorial priorities is the key insight. CoinDesk's journalists cover stablecoins, tokenization, institutional adoption, regulation, and AI-blockchain convergence. If you want a speaking slot at Consensus, your pitch should be something CoinDesk would theoretically want to write about: a genuinely novel argument, a contrarian take backed by data, or a case study that illustrates a trend their reporters have been tracking.

For early-stage founders, the PitchFest competition is the alternative entry point. A panel of CoinDesk experts evaluates all applications, selected startups pitch live at the conference, and the final rounds happen on the mainstage. Requirements: less than five years old, under $5M raised, and a core product in Web3, AI, or blockchain.

The Credibility Stack You Need Before You Apply

Here is the uncomfortable truth: the application form is not where speaking decisions are made. It is where they are confirmed.

Conference programmers are not reading cold submissions from founders they have never encountered. They are validating the impressions they have already formed from what they can find about you online, on-chain, and in the press. That means the six months before you apply are more important than the application itself.

Build the Media Footprint First

Conference organizers and hosts care less about your funding round and more about whether you can educate their audience on problems they are actively trying to solve. That shift in framing, moving from "promoting my project" to "solving a problem the audience has," is what separates the founders who get booked from those who do not.

The practical translation: you need bylined content that already exists before you apply. A piece in Decrypt or CoinDesk arguing a specific position on the theme you plan to speak about is worth more than any credential you can list in an application form. Bylined content establishes your personal perspective, demonstrates depth of thinking, and creates artifacts that continue working for you long after publication. When a TOKEN2049 programmer searches your name, they should find evidence that you have already been trusted to speak on this topic in print.

Establish On-Chain Proof Where Relevant

For ETHDenver especially, on-chain activity matters. Governance participation, protocol contributions, verifiable TVL milestones, audited smart contract deployments: these are the proof points that signal to a builder community that you have earned the right to speak about a technical topic. A founder who can point to a specific on-chain data set or an original research piece that illuminates something nobody else has quantified is dramatically easier to select than one whose case rests entirely on press release history.

Podcast Appearances as Warm-Up Stages

Landing podcast appearances before conference applications serves two functions: it builds the media footprint programmers search, and it sharpens the narrative you will ultimately take to the main stage. Treat each podcast as a working session for refining the thesis you plan to deliver on stage. The organizers at ETHDenver and TOKEN2049 do notice when a founder's name turns up as a guest on shows their community listens to. It functions as a form of social proof from people they already trust.

The key is targeting the right shows. A podcast with 5,000 engaged listeners who build protocols matters more than one with 50,000 passive listeners who chase airdrops. Prioritize hosts who ask technical questions, challenge their guests, and have built their own credibility through consistent output.

The Application That Works

Once the credibility stack is in place, the application itself needs to do three things precisely.

One: lead with the audience problem, not your biography. The strongest submissions start with a question the audience is actively wrestling with. Something like "Why do 80% of institutional tokenization pilots stall at custody?" works far better than "I am the CEO of a protocol with $200M TVL." The programming committee is building a programme for an audience, and they need to know your talk will serve that audience, not promote your project.

Two: propose a specific format for a specific theme. TOKEN2049 asks for your preferred speaking role. ETHDenver asks for your Summit fit. Consensus wants a topic that exemplifies thought leadership. Vague proposals fail. "I could speak about DeFi" is not a pitch. "A 20-minute solo session on why the current approach to oracle security makes institutional adoption structurally impossible, and how three protocols are solving it differently" is a pitch.

Three: include verifiable proof points, not claims. Links to published bylines, on-chain data, audit reports, or research that supports your thesis should all be included. The goal is to make the committee's due diligence effort as close to zero as possible.

Maximising PR Value: Before, During, and After

Getting the slot is step one. Extracting the full PR value from it requires a three-phase campaign.

Before the event (four to six weeks out): Announce the speaking engagement across LinkedIn and X, and use it as a hook to get a journalist conversation booked in advance. Blocking time slots for media interviews ahead of the event pays off significantly. Even ten minutes with a journalist in your niche is an ultra-high value interaction that provides an additional chance to get your name in the press. Share the announcement with your existing media contacts as a signal that the story you have been building has now been validated by a conference with institutional credibility.

During the event: Treat your session as a content production event, not just a presentation. Capture clips of key moments, live-post insights to X and LinkedIn as the talk happens, and make it easy for journalists in the room to pull a quotable line. The conference media list is a resource. Use it to get warm introductions to editors and reporters who are physically in the same building. A face-to-face conversation with a CoinDesk or The Block journalist at a conference is qualitatively different from a cold pitch email sent weeks later.

After the event: The PR cycle does not end when the booth lights go down. Post-conference work should include a written version of your talk pitched as a byline to a publication that did not cover the event, a LinkedIn summary that synthesizes the three most important things your audience walked away with, and targeted follow-up with every journalist who engaged with your session or your name during the week. Speaking at a conference about scaling challenges positions you as the person potential partners approach afterward, but only if you have made it easy for them to find you and the content you produced.

A Note on the Flywheel

Conference speaking and earned media are not separate tracks. They are the same flywheel, turning faster each time you engage it.

A byline in CoinDesk leads to a podcast invitation. The podcast leads to a conference speaking slot. The speaking slot leads to a journalist profile. The profile leads to the next byline, which leads to a larger stage at a higher-tier event. The founders who dominate panels at TOKEN2049 Singapore did not start there. They built the media footprint that made the yes feel inevitable, and they treated every stage, from a side-event panel to a podcast to a small-venue workshop, as a step in the sequence.

In a space where capital flows toward people who can explain where the ecosystem is going rather than just what they are building, the stage is not a reward for having arrived. It is the mechanism by which you arrive.

Start building the stack. The applications will take care of themselves.