If you’re building something, or you’ve come across something the rest of the industry should know about, we want to hear it. Some of the most useful stories we’ve published started as a short note from a reader.
What makes a good tip
- Something specific. A protocol behaving in a way it shouldn’t, a tool that genuinely changes a workflow, a design decision worth examining. Specific beats broad.
- Something checkable. Links to documentation, a repository, on-chain transactions, an audit, or anything else we can verify ourselves. We link to primary sources, so the more you can point us at, the faster we can move.
- Why it matters. A sentence on who is affected and why it’s interesting is worth more than a long description of what something does.
We’re less useful to you if you’re looking for price coverage or token promotion — we don’t publish either. Our Editorial & Corrections Policy sets out what we do and don’t cover.
How to send it
Use the contact form, or email legal@blockcritics.com.
Confidentiality
If you’d prefer not to be named, say so in your first message and we will not identify you in anything we publish without your agreement.
Please be aware of the limits of the tools here, though. Our contact form and email are ordinary, unencrypted channels: submissions are stored on our website and delivered by email, and our host records standard server logs including IP addresses. That is described in our Privacy Policy. We cannot offer technical anonymity through this form.
If your tip is genuinely sensitive — particularly if sharing it could put your job or your safety at risk — do not send it from a work device or a work account. Contact us with a minimal first message from a channel you control and we can agree on a more secure way to talk.
What happens next
We read everything. We can’t promise to reply to every message or to write about every tip, and we won’t tell you in advance whether something is going to run. If we do pursue it, we’ll usually come back to you with questions first.