Skip to main content
Sign In

Make your launch public

Publish a launch post that explains what you built and links to the live program on mainnet.
Make your launch public background
View Your Submissions
Challenge

Make your launch public

Your program is live on mainnet-beta. The upgrade authority is exactly where you decided it should be, the IDL is published, a typed client is generated, and a React frontend talks to it through the Wallet Standard. That is a real piece of software, running on a public network, that anyone in the world can call right now. The work is done. What is left is the part that builders skip far too often: telling people it exists.

Today is an Amplify day, which means the deliverable is not code. It is a public post that shares what you shipped, points to verifiable on-chain proof, and invites other people into your story. Five days of careful deployment work deserve more than a quiet commit. This is how a project finds its first users, its first contributors, and its first feedback.

The scenario

You finished the hard, invisible work. Promoting a program from devnet to mainnet-beta, taking deliberate control of the upgrade authority, publishing an IDL, generating a Codama client, and wiring a frontend through the Wallet Standard are the kinds of tasks that leave no trace anyone else can see. To the outside world, nothing visibly happened.

That is the gap an Amplify post closes. A founder you admire did not get noticed because their code was elegant. They got noticed because they explained, in plain language, what they made and why it matters, and they backed it with a link a stranger could click and verify. In an ecosystem where everything is public by design, “show me” is rarely an unreasonable request. You can answer it with a single explorer URL. Today you turn an internal milestone into a public one.

The challenge

Write and publish a launch post on the social platform you use most, anchored to live on-chain proof of your deployed program. The goal is a post a curious developer could read in thirty seconds and come away knowing what you built, that it is genuinely live, and how to look closer.

What you’ll need

  • The mainnet-beta program ID of the program you deployed earlier this arc
  • Your terminal with the Solana CLI still configured
  • A social account you actually post from: X, LinkedIn, or another platform where developers you respect already hang out
  • Optional: a screen recording or screenshot of your frontend connecting a wallet and calling the program, so the post has something to see

Steps

  1. Confirm your program is really live and grab its address. Point your CLI at mainnet-beta and ask it about your program. The command below prints the program ID, the current upgrade authority, and the deployed data length, so you are quoting facts rather than memory.
  2. Build the proof link. Open your program on the official Solana Explorer, making sure the cluster selector reads “Mainnet Beta,” not Devnet. The URL has the shape https://explorer.solana.com/address/<YOUR_PROGRAM_ID>. This single link is the strongest sentence in your whole post: it lets anyone verify your claim without trusting you. If you prefer a richer view, Solscan and SolanaFM show the same account with more decoded detail.
  3. Write the post around three beats. Keep it short and concrete:
    • What it is in one plain sentence. Skip the jargon. “I shipped a Solana program that lets anyone do X” beats any amount of architecture-speak.
    • One thing you learned the hard way. Maybe it was wrestling control of the upgrade authority, or catching wallet errors before they reached a user. Specifics are what make a post feel real instead of promotional.
    • The proof and the ask. Drop the explorer link, then invite one action: try the frontend, read the code, or just reply with questions.
  4. Add the visual. A clip of a wallet connecting and a transaction confirming does more than three paragraphs of description. If you do not have one, a clean screenshot of the explorer page showing your executable program account works well.
  5. Tag it so the community can find you. Use #100DaysOfSolana so other participants and the program organizers can see your launch. Consider also tagging @solana_devs on X, where the developer community gathers.
  6. Post it, then go one step further. Submit your project to the official Solana ecosystem directory and browse Superteam for bounties, grants, and other builders working on the same surface as you. Sharing is not a single broadcast; it is opening a door and leaving it open.

Run it

solana config set --url mainnet-beta
solana program show <YOUR_PROGRAM_ID>

What just happened

You converted a private accomplishment into something the rest of the world can see and check. The solana program show output you read is the same information anyone gets from the explorer link in your post, which is exactly why that link carries so much weight: in public infrastructure, a claim and its proof live at the same address. You did not ask anyone to take your word for it. You handed them the receipt.

There is a quieter thing happening too. Posting in public, with your name attached, is how the people who hire, fund, and collaborate in this ecosystem find each other. The blog posts on the 100 Days of Solana community and the projects in the ecosystem directory all started as someone deciding their work was worth talking about. Shipping is half of building. Telling the story so the right person reads it is the other half, and today you practiced it on something you genuinely made.

Resources

Submission

Share your launch post publicly on the social platform of your choice, include the live mainnet-beta explorer link to your program, and use the #100DaysOfSolana hashtag so the community can celebrate it with you. Submit the link below.

Submit your project