Skip to main content

Turn your Token-2022 trilogy into a social thread

Spread the word about your DEV post.
Turn your Token-2022 trilogy into a social thread background
View Your Submissions
Challenge

Turn your Token-2022 trilogy into a social thread

The Scenario

The most underrated part of shipping a feature was the post-launch tweet. Not the announcement from the company account. The one from the engineer who actually built the thing, walking through what they shipped and why anyone should care. Those posts were where junior developers learned how senior developers think, where recruiters discovered talent they could not find on LinkedIn, and where strangers in your industry first learned your name.

You have a portfolio now. Your Day 50 and 51 mint skims a fee on every transfer. Your Day 52 mint compounds interest on top of that fee. Day 53 you audited every extension you had baked in. Day 54 you built a token that refuses to move at all. Yesterday you bundled that trilogy into a single DEV post so the work could outlive your terminal history.

Today you do the engineer’s tweet. You take the same trilogy and translate it into a short, scannable social thread that pulls developers into the post, into the repo, and into the conversation about Token-2022. The dev.to post is the artifact. The social thread is the front door.

The Challenge

What you’ll need

  • The published DEV post from Day 55, with its public URL
  • At least one social account you are willing to post from publicly: X, LinkedIn, Bluesky, or Warpcast all count
  • A screenshot or two from your terminal showing one of the three mints in action (the transfer fee being skimmed, the interest accruing, or a blocked transfer attempt on the non-transferable mint) to use as visual hooks
  • The #100DaysOfSolana hashtag, plus one or two platform-native tags like #Solana or #Token2022

Steps

  1. Open the DEV post you shipped on Day 55 and skim it as if you had never seen it before. Note the three things that would make a stranger stop scrolling: the moment a token charges a fee, the moment interest accrues without a cron job, and the moment a transfer is refused. Those are your three hooks.
  2. Pick a primary platform. If you have an existing developer audience on X, start there. If your professional network lives on LinkedIn, start there instead. Pick one, draft for that platform first, then adapt for the others.
  3. Draft a hook post. One or two sentences, no jargon, that names the surprising thing. Something like: “I spent four days building tokens on Solana that charge fees, pay interest, and refuse to move, and the protocol does all of it natively. No middleware. No custom program. Write-up in the thread.” That is the post that earns the click.
  4. Draft three follow-up posts, one per mint. Each one should name what the extension does, show a one-line code or CLI snippet, and link the relevant section of your dev.to write-up. Keep each under the platform’s character limit. On X that is 280 characters per post unless you have a paid account. On LinkedIn, treat each follow-up as a paragraph in a single longer post.
  5. Draft a closing post. Link the full dev.to article, invite replies from anyone who has shipped with Token-2022 extensions you have not tried yet (memo transfer, confidential transfers, default account state), and add #100DaysOfSolana along with one or two ecosystem tags.
  6. Attach visuals. Screenshots of terminal output beat stock images every time. A clean shot of spl-token display showing your extensions, or a failed transfer error message, will out-perform any graphic you could design.
  7. Post the thread. On X, post the hook first, then reply to your own post with each follow-up to build the thread. On LinkedIn, post as a single long-form update with paragraph breaks. On Bluesky, use the thread feature in the composer.
  8. Cross-post. Take the same content and adapt it for at least one other platform. The translation is part of the skill. A LinkedIn audience wants the career framing (“here is what I shipped in week eight of learning Solana”). An X audience wants the technical hook. A Warpcast audience wants the on-chain primitives angle.

Run it

There is no terminal command today, but if you want a quick reusable text-art preview of your thread before you post, drop your draft into a file and word-count each post:

cat thread.md | awk '/^---$/{print NR": "n; n=0; next}{n+=length+1}END{print NR": "n}'

Each numbered line is a post in your thread with its character count. Anything over 280 needs a trim before it goes on X.

What Just Happened

You just did the part of shipping that most engineers skip. You took a real piece of technical work, the kind that lives in a private terminal until it is forgotten, and you put it in front of strangers in a format they will actually read. That is amplification, and it is the closest thing the open source world has to a performance review. Recruiters, grant programs, and hackathon judges all read the same social platforms you just posted on, and they form opinions of developers based on exactly this kind of artifact.

There is a second thing that just happened, and it is less obvious. You translated the same idea three times: once as a dev.to article, once as a hook, and once as a thread. That translation is the muscle that separates engineers who can ship from engineers who can ship and grow a network around what they ship. The Token-2022 trilogy was the test case. The muscle is yours now, and you will use it every time you post about something you build for the rest of this challenge.

Resources

Submission

Share your DEV posts on the platforms you used today and include the #100DaysOfSolana hashtag in every post so the rest of the cohort can find your work. Link to your posts or share screenshots below.

Submit your project