--- title: "On-Chain Data as PR Ammunition for Web3 Founders" description: "TVL milestones, wallet growth, governance activity: your protocol generates journalist-ready data every day. Here's how to turn it into tier-1 coverage in Bloomberg, The Block, and Blockworks." author: "Shilika Jain" date: "2026-10-15T11:28:23.165+00:00" tags: ["defi pr", "blockchain pr", "web3 pr", "tier-1 crypto media", "web3 communications"] canonical: "https://www.shilikajain.com/blog/on-chain-data-pr-story-hooks-web3-founders" --- # On-Chain Data as PR Ammunition for Web3 Founders By [Shilika Jain](https://www.shilikajain.com/authors/shilika-jain) - 10/15/2026 TVL milestones, wallet growth, governance activity: your protocol generates journalist-ready data every day. Here's how to turn it into tier-1 coverage in Bloomberg, The Block, and Blockworks. --- # On-Chain Data as PR Ammunition for Web3 Founders Most Web3 founders treat on-chain metrics as a community update, not a media asset. They drop a "TVL milestone" tweet to the Discord, update the Dune dashboard, and call it done. Meanwhile, a reporter at The Block is actively looking for a data-backed story that explains what's actually happening in DeFi this week, and your protocol is sitting on exactly that data. That's the gap this post is about. You have something traditional tech founders genuinely can't replicate: publicly verifiable, real-time performance data that any journalist can check on DefiLlama or Nansen in 30 seconds. The question is whether you're packaging it as a story, or burying it in a Discord announcement. I spent six years placing Web3 and AI founders into tier-1 publications. The pitches that consistently land at Bloomberg, The Block, Blockworks, and CoinDesk aren't "we launched X" or "we raised Y." They're the ones that open with a verifiable data point that tells a story the journalist was already trying to tell. ## Which On-Chain Metrics Actually Travel as News Not every metric is equally pitchable. Here's how I rank them by media viability. **TVL milestones (with context)** are the most commonly cited on-chain stat and the most frequently misused. A raw TVL number means little to a finance journalist at Bloomberg who covers credit markets and institutional flows. "$100M TVL" needs a frame: Is that 3x growth in 60 days? Is it organic liquidity from non-incentivized depositors? Does it exceed competitor X for the first time? The headline isn't the number. It's what the number means for the category. One caveat I flag to every founder: TVL can be inflated by incentive campaigns, price appreciation in deposited assets, or circular liquidity flows. Journalists who cover DeFi seriously already know this. If you acknowledge it proactively, you protect your credibility when market conditions shift. If you gloss over it, a reporter will do it for you in the piece, and not kindly. **Wallet growth curves** are underrated as a pitch hook. A single wallet number isn't news. A 90-day cohort chart that shows users are returning 30 days after first deposit is news. Retention is something finance journalists and VC-focused outlets understand instinctively because it maps to a concept they already care about: is this thing sticky? DAU-to-MAU ratios, D7 and D30 retention among active depositors, growth in unique wallets completing a meaningful action (not just connecting): these are the stats that signal genuine adoption versus airdrop farming. **Governance participation rates** are almost completely untapped as a PR asset. A protocol where 40% of token supply is actively voting on major proposals is a fundamentally different story than one where 3% of tokens drive every decision. This stat signals decentralization health, community conviction, and long-term stakeholder alignment, all things that matter to a journalist writing about whether DeFi governance actually works. It's a narrative angle, not just a metric. **Protocol revenue** is the metric that crosses over most cleanly to mainstream financial press. Bloomberg, Forbes, and the Financial Times aren't going to report on your TVL, but they will cover a DeFi protocol generating $X million in annualized fee revenue with no VC backstop and no reliance on token inflation. That's a business story. The framing that works: compare it to a recognizable traditional finance benchmark. "More fee revenue per quarter than a mid-sized US credit union" is a sentence a Bloomberg reporter can use in a story without needing to explain what DeFi is. ## The Framework: Four Steps to a Data-Driven Pitch **Step 1: Build your running metrics file before you need it.** Every week, pull and log seven numbers: TVL and its 30-day and 90-day change, unique active wallets (distinct addresses completing a meaningful action), D30 wallet retention, weekly governance votes cast, protocol fee revenue, and total transactions. Don't wait for a milestone to start tracking. The story is always in the trend, not just the peak. > if the growth & BD teams knew how to write SQL, there would be better chances of analysing on-chain data to build effective marketing plans & valuable partnerships! > > [Shilika Jain on X, 25 Jan 2023](https://x.com/Shilika_jain/status/1618163344317505536) That's where the PR leverage is. Your growth team is already running SQL on your on-chain data. Add a weekly export to a shared doc and you have the raw material for 12 pitches a year, none of which require a press release. **Step 2: Anchor the data to a journalist's existing story.** The best pitch doesn't arrive in isolation. It arrives the week a reporter just published a piece on DeFi adoption slowdown, and your data is the counter-evidence. Or it arrives the morning of a macro event (Fed rate decision, USDT depeg scare, major exploit at a competitor) when your governance activity or outflow data is actually the cleanest signal of how real users responded. > Most crypto companies think PR = announcements. The best brands create narratives so powerful that every announcement becomes news. > > [Shilika Jain on X, 4 Jun 2026](https://x.com/Shilika_jain/status/2062437697978008001) This is the core shift. Stop treating your protocol's data as an internal dashboard and start treating it as a newswire. Every week, ask: what macro narrative is playing out in crypto right now, and what does my on-chain data say about it? **Step 3: Translate the data for the journalist's audience.** A Blockworks reporter and a Bloomberg Crypto reporter are covering the same protocols but writing for completely different readers. Blockworks readers are institutional-adjacent and understand terms like TVL, slippage, and liquidity depth. A Bloomberg reporter's audience might be a traditional asset manager who has never used a DeFi protocol. For trade press (The Block, Blockworks, CoinDesk): lead with the on-chain stat, include the Dune or DefiLlama link so the journalist can verify in one click, and frame it in relation to the protocol category. "Cross-chain stablecoin deposits grew 87% in Q3 while total DeFi TVL was flat" is a story about your category, with your protocol as the evidence. For mainstream financial press (Bloomberg, Reuters, FT): strip the jargon, convert to a traditional finance analogy, and tie it to a regulatory or institutional theme. "The protocol processed $2.1 billion in loans last quarter, entirely governed by token holders rather than a board of directors" is a governance story, not a DeFi story. **Step 4: Sequence releases to sustain coverage momentum, not create a single spike.** This is the mistake I see most often. Founders drop everything at once: TVL milestone, wallet growth, governance update, revenue figure, all in the same press release on the same day. One outlet might cover it. The story dies in 48 hours. The smarter play is sequencing. TVL milestone to The Block as a hard data exclusive (week 1). Governance participation rate as an op-ed angle in Blockworks (week 3). Protocol revenue contextualized for mainstream press with a CEO interview (week 6). Three separate story hooks from the same underlying data, spread across two months, keeping your protocol in coverage rotation without a single new product announcement. ## How to Contextualize On-Chain Data for Non-Crypto Journalists This is where most Web3 PR fails completely. Finance reporters at Bloomberg or the Financial Times are not intimidated by data. They are intimidated by jargon that requires them to explain Web3 concepts before they can even get to the story. The rule is: if the pitch requires you to define more than one technical term, the framing is wrong. Three translation templates that consistently work: | On-Chain Metric | Crypto-Native Frame | Mainstream Finance Frame | |---|---|---| | $500M TVL | "Top 10 DeFi protocol by assets" | "Manages more assets than most community banks" | | 40% governance turnout | "Active DAO with broad participation" | "More shareholder participation than most S&P 500 votes" | | $50M quarterly protocol revenue | "Strong fee generation for a DeFi primitive" | "Profitable without VC funding or token subsidies" | | 200K unique wallets, 30% D30 retention | "Strong user stickiness for a DeFi protocol" | "Higher retention than most fintech apps in year one" | None of these analogies are perfect. That's not the point. The point is to give the journalist a handrail so they can write the story without a glossary. ## Pitfall: When Your Data Becomes a Liability On-chain data is double-edged. A reporter can verify your numbers in seconds, which means they can also verify that your "500K unique wallets" are 80% created for an airdrop campaign and inactive for 90 days after claim. Or that your TVL spike corresponds exactly to a token incentive program that ended last week. The journalists who cover DeFi seriously at The Block and Blockworks are running their own Dune queries. Don't pitch data that doesn't hold up to a competent analyst. The credibility you lose on a bad data pitch takes 12 months to rebuild. Two rules I enforce with every client before we pitch anything on-chain: 1. Can the journalist verify this independently, and when they do, will it hold up? 2. Are we acknowledging the caveats (incentive-driven TVL, airdrop-inflated wallets, etc.) proactively, or waiting to be asked? ## Real Pattern: The Data Report Play One of the most repeatable structures I've run for protocols is a standalone data report. Not a press release. Not a product announcement. A PDF or microsite that packages your on-chain data into a quarterly or annual narrative: where the category is going, what your users are doing, and what the data says about adoption patterns. The Tangem self-custody survey I ran in 2026 is a good parallel from the hardware wallet side. One headline stat (66% of crypto users support self-custody) travelled across English, Korean, Japanese, and Dutch editions without a separate pitch per market. The journalists led with the stat, not the company. That's the goal: own the data, own the narrative. For a DeFi protocol, the equivalent is something like a quarterly liquidity health report, a governance participation index, or a cross-chain capital flow study. Tools like Dune Analytics, DefiLlama, Nansen, and Glassnode make it possible to build genuinely newsworthy data narratives without needing proprietary infrastructure. When I worked on Web3Auth's PR in 2023 and 2024, pairing a Google Cloud partnership announcement with a separately timed adoption report gave us two distinct news hooks in a single quarter. The partnership got the CoinDesk Protocol newsletter and Blockworks. The adoption report got Cryptonews and category-specific coverage. One set of news assets, two separate coverage cycles. The structure transfers: if you have an on-chain metric worth pitching, ask whether it can also anchor a report, and whether that report can generate a second wave of coverage two to four weeks after the initial announcement. ## The 72-Hour Window DeFi coverage moves on a news cycle, not a PR schedule. The strongest pickup for any data-driven pitch happens in the first 72 hours after a hard news event: a competitor exploit, a major governance vote, a sudden TVL shift across the category. If your protocol's data is the clearest signal of how the market responded to that event, you need to be pitching within hours, not days. This means your metrics file needs to be live and current, not reconstructed at pitch time. The journalist who is writing the "DeFi's reaction to X" piece at 2pm is not waiting for your PR team to pull the numbers together by Thursday. ## What This Looks Like as a Pitch Three to four sentences. Subject line contains the data point and the angle. Opening sentence states the fact. Second sentence gives the journalist a link to verify it independently. Third sentence identifies the named source available to discuss. Do not attach a press release. Do not CC five reporters at the same outlet. Do not pitch the data in the same week a competitor just had a major exploit and all available editorial attention is pointed elsewhere. The journalists at tier-1 crypto trade outlets are on the payrolls of their publications, not yours. They're not obligated to cover your milestone. The pitch that earns coverage is the one where your data genuinely advances a story the reporter was already trying to tell. If you want to audit your current metrics stack and figure out which numbers you're sitting on that are actually pitchable, [book a 30-min teardown with me](https://calendly.com/shilikajain/30min/). We'll go through what you have, what's missing, and what a 90-day data-driven coverage sequence looks like for your protocol. --- **Book a 30-min teardown with Shilika** - https://calendly.com/shilikajain/30min/ Canonical: https://www.shilikajain.com/blog/on-chain-data-pr-story-hooks-web3-founders