Skip to main content
Sign In

Share what you learned

Share your learnings from this Arc with other develoeprs!
Share what you learned background
View Your Submissions
Challenge

Share what you learned

The Scenario

This week, you went deep into token fundamentals on Solana. You created a mint from scratch, gave it a name and symbol with metadata, attached transfer fees using the Token Extensions Program, reinforced the entire workflow end to end, experimented with non-transferable tokens, and then wrote a technical blog post documenting your journey. That is a serious body of work, and it puts you ahead of most developers who are still just reading about how tokens work without ever creating one.

But building things in private only gets you so far. The developers who grow the fastest are the ones who share what they are learning while they are learning it. Not polished tutorials months after the fact, but real, in-the-moment posts that show what they built, what surprised them, and what clicked. Today, you are going to take the best moment from your token-building week and put it in front of other developers.

The Challenge

What You’ll Need

  • A social media account on X/Twitter, LinkedIn, Bluesky, or wherever your developer community hangs out
  • A screenshot or code snippet from your token work this week
  • A few sentences describing what you built and what you learned
  • Your blog post from Day 34 (optional, but great to link to)

Steps

  1. Pick your highlight. Look back at the past six days and choose the moment that felt most meaningful. Good candidates include:
    • Your first successful token mint on devnet, with the terminal output showing the mint address
    • Your token appearing in Solana Explorer with its metadata (name, symbol, image)
    • The transfer fee configuration where you saw fees collected at the protocol level
    • Your non-transferable token experiment, where the blockchain itself rejected a transfer attempt
    • A code snippet from your Anchor program or CLI commands that made something click
  2. Capture the evidence. Take a screenshot of your terminal output, your token on Solana Explorer, or a key section of your code. If you wrote a blog post on Day 34, grab the link to that as well. Visual proof makes your post stand out in a feed full of text-only updates.
  3. Write your post. Keep it short and specific. A good formula:
    • What you built this week (one sentence): “I created a custom SPL token on Solana with metadata, transfer fees, and non-transferable extensions.”
    • What surprised you (one sentence): “I didn’t expect the Token Extensions Program to let you enforce economic rules like transfer fees directly at the protocol level, no off-chain logic needed.”
    • What is next for you (one sentence): “Next week I’m diving into how these tokens interact with real programs on-chain.”
  4. Add your tags and publish. Include #100DaysOfSolana so the community can find your post. If you are posting on X, consider tagging @solana_devs to connect with the broader Solana developer ecosystem. If you wrote a blog post on Day 34, drop the link in your social post to drive readers to the full write-up.
  5. Engage with someone else. Search for #100DaysOfSolana and find another participant’s post. Leave a genuine comment or reaction. Building in public works best when it is a conversation, not a broadcast.

What Just Happened

You just turned a week of hands-on learning into something that lives beyond your local machine. That matters more than it might feel like right now. When you share a screenshot of a token you created on devnet, you are not just showing off. You are proving to yourself and to other developers that you can do this. You went from zero token knowledge to creating mints, attaching metadata, configuring transfer fees, and experimenting with non-transferable extensions. That is real capability, and putting it on the record helps you own it.

There is a practical side to this too. The post you just published is a timestamp of your skills. Six months from now, when someone asks what you know about Solana token development, you can point to a public record of your work instead of trying to explain it from memory. Developers who build in public create a portfolio that speaks for itself. Every post, every screenshot, every blog link is another data point that says: this person ships.

If you linked back to your blog post, you also just created a content chain. Your blog post provides the depth, your social post provides the reach, and together they show that you can both build and communicate. Those are the two skills that every developer community values most.

Resources

Submission

Share your social media post using the #100DaysOfSolana hashtag.

Submit your project