Skip to main content

Take your composed program public

Share what you've learned this week!
Take your composed program public background
View Your Submissions
Challenge

Take your composed program public

Yesterday’s DEV post was the long-form version of what you learned. It lives at a URL, it is searchable, and it will help future readers.

But long-form posts are slow ignition. The faster, noisier channel where Solana builders actually find each other is short-form social: X, where the @solanadevs account and the founders, auditors, and core contributors you have been reading from all hang out, and LinkedIn, where recruiters and engineering managers in the space are scrolling.

One thoughtful post about a working program is worth more than a dozen “I am learning Solana” updates, because it is evidence rather than a claim.

You are not pitching anything today. You are showing a thing you built, in a way that a stranger scrolling at the bus stop can understand in under ten seconds and a curious developer can dig into for ten minutes.

The challenge

What you’ll need

  • An account on X, LinkedIn, or both. Pick the one where your network already exists. You can cross-post later.
  • A public GitHub repository containing your composed program, with a working Anchor.toml and at least one passing LiteSVM test. If the repo is private, make it public before you post.
  • A screenshot or short screen recording. A clean terminal showing your test suite passing is fine. A snippet of the instruction handler doing the CPI is even better.
  • The transaction signature from one successful devnet run of your program, so you can link to it on Solana Explorer.

Steps

  1. Open your composed program and pick the single most interesting moment in it. The line where invoke_signed fires with PDA seeds is usually the strongest choice, because it is the line that proves the program is signing for an account no human controls. If you have a more surprising moment, like a CPI into Token-2022 that uses a transfer fee extension, lead with that instead.
  2. Take a clean screenshot of that snippet. Use a readable font and a dark theme if your audience prefers dark themes. If you want a nicer image, paste the code into ray.so or carbon.now.sh and export a PNG. Keep the snippet under 20 lines so it is legible on a phone.
  3. Write the post. Aim for a structure like this on X: a one-line hook that names what the program does, two or three short lines on the key idea (PDA-signed CPI, calling Token-2022 from your own program, or whatever your most interesting moment was), and a final line pointing at the repository. On LinkedIn you have more room, so add a short paragraph about why this mattered to you as someone moving from Web2 into Solana.
  4. Attach the screenshot or recording. Posts with media get materially more reach on both platforms, and a code image gives a curious reader something concrete to look at while they decide whether to click the repo link.
  5. Link to your GitHub repository in the post itself, not in a reply. Replies hurt distribution on X. If you want to add a bonus link to your devnet transaction on Solana Explorer, put it in a reply to your own post.
  6. Add the #100DaysOfSolana hashtag. On X, add one or two other relevant tags like #Solana or #Anchor, no more. On LinkedIn, three to five hashtags is the sweet spot.
  7. Hit post. Then drop the link into the program Discord or your study group so the people who already cheer for you can amplify it in the first hour, which is when the algorithm on both platforms is deciding whether to show it more widely.

Run it

Before you post, run your test suite one more time so the screenshot you grab is from a green run, not a stale one.

anchor test

What just happened

The thing you did today was practice the loop that working developers in this space run constantly: build a small thing, post the most interesting fragment of it, link to the full repo, move on. Doing it once is awkward. Doing it ten times turns into a portfolio, and that portfolio is what opens the door to the deeper conversations in the ecosystem.

Resources

  • @solanadevs on X, the official Solana developers account, useful for both following and being seen by the right crowd
  • Solana Developers Hub, the canonical landing page you can link curious readers to
  • ray.so, a fast code-to-image tool that produces clean snippets for social posts
  • Solana Explorer (devnet), so you can link to a real transaction signature as proof your program ran

Submission

Share your post on X or LinkedIn (or both) with the #100DaysOfSolana hashtag, and link to your GitHub repository in the post itself. Submit your post below!

Submit your project