threads
How to write a crypto Twitter thread people bookmark
How to write a Twitter thread for a crypto project: a hook-first opener, one idea per tweet, 5-9 tweets, links in the reply, Monday timing and a full example.
To write a crypto Twitter thread people bookmark, write the first line before anything else and make it a specific promise, then give one idea per tweet across 5 to 9 tweets. Keep links out of the body, publish educational threads on Monday morning, and stay in the replies for the first hour. Below is how to write a Twitter thread for a crypto project step by step, when a thread is the wrong format, and a full example to take apart.
This guide is part of our crypto Twitter marketing guide. The project in the example is fictional.
Thread, single post or quote-tweet?
Threads are for explaining. Used for anything else, they tend to get padded. Choose the format from the situation:
| Situation | Format |
|---|---|
| Reacting to a specific post or news | Quote-tweet with your take |
| A thesis, or "how X actually works" | Thread of 5-9 tweets |
| One fact or number carries the point | Single post with a chart |
| Your project's milestone | Quote-tweet the announcement and add your breakdown |
| A sharp opinion | Short post, no image, open to pushback |
| A meme | Image with a short caption |
| Any link | The first reply under your own post |
If one post and a chart can carry it, post that. A quote-tweet with real added value often travels further than a reply would. A thread on something that needed two sentences teaches readers to skip your next thread.
Still, for a project account, the thread that joins data into a thesis is the category we see bring the most new followers and bookmarks. It is also why the pinned post on a new account should be a thread, as we explain in how to grow a crypto project on X from zero.
Write the hook first
The first tweet decides whether anyone opens the second. Our playbook treats the hook as most of a thread's outcome, so write it first and spend the most time there.
Hooks that work give a reason to expand:
- A number: "The APY on a lending vault is usually four things blended into one figure."
- A contrast: "RWA yields look boring until you see where they come from."
- A defensible claim: "Points programs don't count users. They count wallets."
- A pain the reader has felt: "If your LP position keeps trailing the pool's APR, one of three things is happening."
Hooks that don't:
We're excited to share a thread about our vault architecture.
A thread on DeFi yields (1/9)
gm! Let's talk about something important.
Each of these announces a thread without giving anyone a reason to read it. "We're excited to announce" with no specifics is the corporate voice CT scrolls past. CT-native openers like "few understand this" can work, but only when the next tweet delivers something the reader did not know.
A good hook also hints at what the reader leaves with: how to check something, where a number comes from, the mistake most people make. Do not promise what the thread cannot pay off. Readers who feel baited mute accounts, and in the ranking weights Twitter open-sourced in 2023 negative feedback scored -74 against 0.5 for a like. Those weights have since changed, and in the ranking xAI open-sourced in 2026 muting an author still weighs -58.8, so the lesson has aged well.
One idea per tweet
Threads travel in pieces. Someone quotes tweet 4, not the whole thing, so every tweet should make sense on its own.
- One claim per tweet, with its reason or example.
- Short lines and white space. A dense paragraph looks worse on a phone than it does in your drafts.
- Plain claims over adjectives. "Utilization doubled after the rate change" says more than "massive growth".
- Slang is seasoning: one or two words across the whole thread, if it fits your voice.
- Numbering (1/, 2/) helps readers keep their place. It is optional; be consistent if you use it.
5 to 9 tweets: a structure that holds
Most educational threads fit this skeleton:
| Tweet | Job |
|---|---|
| 1 | Hook and promise |
| 2 | Why it matters to the reader |
| 3-7 | One point each, in an order that builds |
| 8 | The recap, the tweet people screenshot |
| 9 | A genuine question, and a note that sources are in the reply |
Under five tweets, it probably wants to be a single post. Over nine, it is probably two threads.
Close with a question you would like answered, not "like and RT if this helped". A real question brings replies, and replies you answer early are what keep the thread in front of people.
Links go in the first reply
Keep every link out of the thread body. Put docs, dashboards and sources in a reply under your own post, and say in the last tweet that they are there. The thread reads as content rather than a redirect, and anyone who wants to verify a claim finds the receipts one tap away. We follow this on every account we run, threads and single posts alike.
When to post: Monday morning for educational threads
Our content plan puts educational threads on Monday morning. CT is rested and in bookmarking mode, and a Monday thread earns the longest tail of quotes through the week. The other post categories have their own slots:
| Post category | Slot in our plan | Why |
|---|---|---|
| Educational threads | Monday, morning | Readers are saving things to get through this week |
| Product updates and ship logs | Tuesday-Wednesday | Peak attention; releases posted on a Friday night vanish |
| Community and contests | Thursday-Friday | People have weekend time to take part |
| Status and traction | The same day as the news | Numbers are news for 24 hours, history after |
"Morning" means morning where most of your audience lives. The full weekly rhythm is in the crypto content plan guide.
After you post, stay in the replies for the first 30-60 minutes. Answer substantive replies in a way that invites a second one. The crypto Twitter reply strategy covers how.
How to write a Twitter thread for crypto: a full example
Vaultic is a fictional protocol that runs lending vaults. Here is an educational thread from its account, written to the rules above.
1/
The APY on a lending vault is usually four things blended into one figure.
Most depositors only ever see the total.
Here's how to take it apart, on any vault, ours included.
2/
Why bother: when the headline number jumps or drops, the reason sits in one of the four parts.
Know which part moved and you know whether to care.
3/
Part one: the base rate.
This is what borrowers pay. It rises when utilization (borrowed / supplied) is high and falls when it's low.
It's the only part paid for by real demand.
4/
Part two: incentives.
Token emissions or points on top of the base rate.
The protocol pays these, not borrowers, and they have an end date. Find out when.
5/
Part three: the strategy layer.
Some vaults loop, lend collateral onward or route deposits into other protocols.
Every extra hop adds yield and adds a way to lose it. Check which protocols your deposit touches.
6/
Part four: fees.
A performance or management fee comes off the top.
Check whether the number you see is before or after fees. It isn't always labeled.
7/
How to check it yourself:
- the vault's docs, for strategy and fee terms
- onchain utilization, for the base rate
- DefiLlama's yields pages, for the pool's history
- a Dune dashboard, if the protocol has one
8/
The short version:
base rate = demand
incentives = temporary
strategy = extra risk
fees = off the top
When the APY moves, find out which one moved.
9/
On Vaultic we show all four separately on every vault page. The total alone isn't enough to decide on.
Which part do you check first?
Docs and our Dune dashboard are in the reply below.
Reply under the thread:
Sources for this thread
Vault docs, strategy and fees: [link]
Vaultic dashboard on Dune: [link]
Why it holds up:
- The hook makes a specific promise about a number every DeFi user has seen.
- Each part gets its own tweet, and tweets 3 to 6 all work when quoted alone.
- The product shows up once, in tweet 9, after the thread has already been useful.
- There are no yield promises and no figures that would need a source.
- Links sit in the reply, and the closing question is one readers can answer in a word or a sentence.
Editing checklist
Run through this before a thread is scheduled:
- Would a stranger expand the first tweet? Does it say what they get?
- Does every tweet carry one idea and make sense quoted alone?
- Is it 5-9 tweets, with anything repetitive cut?
- Are all links in the reply, none in the body?
- Has every number been checked against DefiLlama, Dune, the docs or GitHub, with the source in the reply?
- Is it free of price calls, return promises, "guaranteed" and "risk-free"?
- If it is paid or sponsored, is the disclosure clear? See crypto Twitter ad disclosure.
- Is slang limited to a word or two, and only if it is your voice?
- Has someone who built the feature read any technical claims?
- Does it end with a real question?
- Is it scheduled for the right slot, with someone free to answer replies for the first hour?
On the accounts Grapevine runs, threads with technical claims always go through that last human read before they are queued.
FAQ
How long should a crypto Twitter thread be?
Five to nine tweets for most educational threads. Fewer than five usually means the idea fits a single post; more than nine usually means you have two threads or you are padding.
What is the best time to post a crypto thread?
In our content plan, educational threads go out on Monday morning, when CT is rested and in bookmarking mode, and a thread has the whole week to collect quotes. Use the morning of the time zone where most of your audience is, and be available to reply for the first hour.
Where should links go in a Twitter thread?
In a reply under your own post, never in the thread body. Mention in the last tweet that sources are in the reply, so readers who want to verify know where to look.
Should a thread mention our own product?
Once, near the end, after the thread has taught something. A thread that is useful without the product earns the one mention. A thread that pitches in every tweet gets read as an ad.