<h2 class="heading-node">The OG Glossary is Back</h2>The Solana Glossary accompanied us devs for years — a real reference that actually helped you understand what was going on, especially on the early days of this, at the time, alien ecosystem. Then it got quietly replaced by a generic "Terminology" page. Flat. Boring. Forgettable. No glow to the ssary.We're bringing it back. Expanded to 1000+ terms, structured as an SDK, ready for the new scale of consumer-app Solana and the agentic economy.<h2 class="heading-node">Overview</h2>We've built the data layer: 1000+ terms, cross-referenced, categorized, with i18n support (pt-BR + es). It's packaged as an npm package (hopefully released after your contribution) and available at:Repository: <a target="" rel="noopener noreferrer nofollow" class="link" href="https://github.com/solanabr/solana-glossary)">github.com/solanabr/solana-glossary</a>Now we need you to build something cool on top of it. And useful.Some ideas to get you started (but don't let us limit you):- A frontend for the glossary: searchable, browsable, beautiful. Something we can actually host and point people to - and it's actually fun.- Agentic tooling: MCP servers, RAG pipelines, Claude/GPT tools that use the glossary as context - cutting token and context.- Data expansion: automate adding more terms, keep definitions fresh, pull from Solana docs/repos/blogs.- Developer integrations: VS Code extensions, CLI tools, Anchor template generators with inline glossary context.- Educational tools: interactive quizzes, learning paths, onboarding flows for new Solana devs.The bar: it has to look great and work great. Otherwise you could just go read the boring Terminology page.Be creative. Surprise us. Turn a boring list of terms into something useful for all kinds of Solana devs &amp; aspiring builders.<h2 class="heading-node">Rewards</h2><ul class="list-node"><li>🥇 1st $1,500 USDG</li><li>🥈 2nd $1,000 USDG</li><li>🥉 3rd $800 USDG</li></ul>Total Prize Pool: $3,300 USDGRankings are based on total contribution value across all submitted PRs — quality, creativity, and usefulness all factor in.<h2 class="heading-node">Judging Criteria</h2><ul class="list-node"><li>Usefulness &amp; Impact [30%]: Does it solve a real problem? Would Solana devs actually use this?</li><li>Quality &amp; Polish [25%]: Does it work well? Clean code, good UX, no rough edges</li><li>Creativity [25%]: Novel approach, surprising use of the data, something we didn't expect</li><li>SDK Integration [10%]: Proper use of the <code class="inline" spellcheck="false">@stbr/solana-glossary</code> SDK or data layer</li><li>Documentation [10%]: Clear README, setup instructions, demo (video or screenshots)</li></ul>Bonus factors (can elevate your ranking):- Multiple high-quality submissions across different categories- i18n support (pt-BR, es) in your project- Live deployed demo- Deep dive writeup or video walkthrough of your implementation## Rules✅ Allowed- AI-assisted development (must be reviewed, tested, and production-quality)- Multiple submissions (separate PRs for distinct contributions)- Teams submitting under a single account- Building on any framework/language as long as it uses the glossary SDK or data❌ Not Allowed- Submissions that don't use <code class="inline" spellcheck="false">@stbr/solana-glossary</code> or its data <code class="inline" spellcheck="false">data/terms/*.json</code>)- Low-effort wrappers with no real value added- Breaking or modifying the core glossary data without a PR to the glossary repo itself- Closed-source submissions<h2 class="heading-node">Submission Requirements</h2>Submit through Superteam Earn with:- PR Link(s) — One PR per distinct contribution to [github.com/solanabr/solana-glossary](https://github.com/solanabr/solana-glossary)- PR should include setup instructions and/or a short demo (video or screenshots)- Twitter Post — Share your submission and tag @SuperteamBR and @SuperteamEarn- Brief Summary — 3-5 sentences explaining your approach and what makes it useful- Star the repo! It's rude not to.Your final ranking will be the sum of all your contributions.Check the <a target="" rel="noopener noreferrer nofollow" class="link" href="https://github.com/solanabr/solana-glossary#readme">README</a> for the full API reference.<h2 class="heading-node">Timeline</h2>- Submission Deadline: 7 days from listing- Review Period: 7 days after deadline- Winner Announcement: Within 10 days after deadline<h2 class="heading-node">Terms &amp; Conditions</h2>- All submissions must be original work- Code must be open-source (MIT license preferred)- Winning submissions may be featured and extended by Superteam Brazil- By submitting, you agree to potential follow-up collaboration- Judges' decisions are final<h2 class="heading-node">Questions?</h2>- GitHub: Open an issue on the <a target="" rel="noopener noreferrer nofollow" class="link" href="https://github.com/solanabr/solana-glossary">repo</a>, tag @kauenet- Discord: <a target="" rel="noopener noreferrer nofollow" class="link" href="https://discord.gg/superteambrasil">discord.gg/superteambrasil</a>- Twitter: <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://twitter.com/SuperteamBR">https://twitter.com/SuperteamBR</a> / <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://twitter.com/kauenet">https://twitter.com/kauenet</a>Skills: TypeScript, Frontend/Backend, AI/LLM tooling, Data Engineering, UX DesignEligibility: Brazil

Bring back (& super-power) the Solana Glossary