<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Stellar Nigeria</title>
    <description>The latest articles on DEV Community by Stellar Nigeria (@stellar_nigeria).</description>
    <link>https://dev.to/stellar_nigeria</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4063808%2Fc7beab8c-17af-4cc5-a18d-9ced787ec2de.jpg</url>
      <title>DEV Community: Stellar Nigeria</title>
      <link>https://dev.to/stellar_nigeria</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/stellar_nigeria"/>
    <language>en</language>
    <item>
      <title>The Builder's Circle is back!</title>
      <dc:creator>Stellar Nigeria</dc:creator>
      <pubDate>Wed, 05 Aug 2026 09:02:09 +0000</pubDate>
      <link>https://dev.to/stellar_nigeria/the-builders-circle-is-back-209m</link>
      <guid>https://dev.to/stellar_nigeria/the-builders-circle-is-back-209m</guid>
      <description>&lt;p&gt;And we're Stellar Nigeria now.&lt;/p&gt;

&lt;p&gt;It's been quiet here for a while now. Behind the scenes, though, quite a lot was going on. Some of it on our end, and a good deal of it on yours.&lt;/p&gt;

&lt;p&gt;On our end, the biggest change is that we rebranded. Stellar West Africa is now Stellar Nigeria. Focusing on Nigeria alone means we can better support the people here, whether you're building, contributing, or still working out where to start.&lt;/p&gt;

&lt;p&gt;We also spent that time listening to you. A lot of you told us what needed improvement, most of which had to do with needing a clearer path for contributing and building something of your own. We took all of that seriously, and nearly everything below came out of those conversations.&lt;/p&gt;

&lt;h2&gt;
  
  
  Meanwhile, on your&amp;nbsp;end
&lt;/h2&gt;

&lt;p&gt;While things were quiet here, a number of you carried on building anyway, which says more about this community than anything we could write.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;a href="https://www.koboxfinance.com/" rel="noopener noreferrer"&gt;Kobox&lt;/a&gt; received a $5,000 Instaward to validate their MVP. Kobox is a modern digital banking solution that grants you access to traditional finance and cryptocurrency in one place&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href="https://useblinkapp.com/" rel="noopener noreferrer"&gt;Blink&lt;/a&gt; was awarded $75,000 worth of XLM. Blink is a mobile app that lets businesses accept crypto as payment over Bluetooth and settle instantly in their local currency, while letting users spend their crypto like cash.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href="https://www.jumpa.xyz" rel="noopener noreferrer"&gt;Jumpa&lt;/a&gt; was awarded $89,700 worth of XLM. Jumpa is an automated payment platform designed to make cross-border transactions simple, fast, and accessible for users in emerging markets through chat-based interfaces and USSD.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href="https://fundable.finance/" rel="noopener noreferrer"&gt;Fundable Finance&lt;/a&gt; was awarded $96,499 worth of XLM. Fundable Finance is an on-chain financial operations platform for global teams, handling automated payouts, payment streaming, and crypto-to-fiat offramping across emerging markets.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A funding pipeline that has already been&amp;nbsp;tested
&lt;/h2&gt;

&lt;p&gt;This year alone, West African projects have received over $1.3 million in XLM to build on Stellar. So it is established that we have a route into SCF funding that works. Now that our focus is on Nigeria alone, the Builder's Circle is where that route begins. It's where you learn about the ecosystem, make your first contributions, find a gap worth building into, and get proper help with your grant application before you submit.&lt;/p&gt;

&lt;h2&gt;
  
  
  It isn't only for&amp;nbsp;founders
&lt;/h2&gt;

&lt;p&gt;We also want to be clear about something: you don't need a product idea to belong here.&lt;/p&gt;

&lt;p&gt;Members of this community are consistently earning on &lt;a href="https://www.drips.network/wave" rel="noopener noreferrer"&gt;Drips &lt;/a&gt;and &lt;a href="https://grantfox.xyz/" rel="noopener noreferrer"&gt;GrantFox &lt;/a&gt;for contributing to Stellar repos. &lt;a href="https://dev.to/stellar_nigeria/over-400000-went-to-stellar-contributors-this-year-33jd"&gt;Over $400,000 has gone to contributors on Stellar this year&lt;/a&gt;, and a lot of that has come to people in this community. That is another path in its own right, and we're building around it now.&lt;/p&gt;

&lt;h3&gt;
  
  
  Starting this&amp;nbsp;August:
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Monthly themes. Every month, we pick one Stellar topic and learn it together, whether that's accounts, Soroban, wallets, or something else. Our weekly syncs are becoming classes, so once a week, we'll explore that month's topic. If you're looking to learn about Stellar, that's your way in, and no prior knowledge is assumed.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;A monthly raffle for Drips and GrantFox contributors. You're already earning over there, and now your participation gets you a shot at something from us as well.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Weekly games night. Skribbl, Kahoot, or whatever the group votes for, with data subscriptions going to three winners every week.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Referral rewards. Bring your developer friends along, and members with the most valid invites win from the referral pool each month.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Come build with&amp;nbsp;us
&lt;/h2&gt;

&lt;p&gt;If you joined us during the residency and left afterwards, kindly reapply. As mentioned already, some of the best work out of this community has come from people who stayed consistent and carried on regardless.&lt;/p&gt;

&lt;p&gt;And if you've never contributed to open source before, start with our guide to making your first contribution to a Stellar repo. It assumes you know nothing.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://bit.ly/stellarwabcircle" rel="noopener noreferrer"&gt;Apply here&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>blockchain</category>
      <category>grants</category>
      <category>web3</category>
      <category>osdc</category>
    </item>
    <item>
      <title>Over $400,000 Went to Stellar Contributors This Year.</title>
      <dc:creator>Stellar Nigeria</dc:creator>
      <pubDate>Wed, 05 Aug 2026 08:48:39 +0000</pubDate>
      <link>https://dev.to/stellar_nigeria/over-400000-went-to-stellar-contributors-this-year-33jd</link>
      <guid>https://dev.to/stellar_nigeria/over-400000-went-to-stellar-contributors-this-year-33jd</guid>
      <description>&lt;p&gt;This year, the Stellar ecosystem pivoted towards supporting open source contributions. If you've never contributed to open source, you couldn't have picked a better time to get started.&lt;/p&gt;

&lt;p&gt;In January, &lt;a href="https://www.drips.network/wave" rel="noopener noreferrer"&gt;Drips &lt;/a&gt;launched its Wave program with Stellar. Each month, for an 8–10 day period, developers resolve issues in selected GitHub repos, and everyone gets paid in USDC based on the issues they closed. The first four waves paid out ~$250,000, while the most recent one had over 700 contributors across 500+ repos.&lt;/p&gt;

&lt;p&gt;Next, &lt;a href="https://grantfox.xyz/" rel="noopener noreferrer"&gt;GrantFox &lt;/a&gt;arrived to fill the space OnlyDust left behind. Here, projects post work for contributors to claim and get paid in USDC after their work is accepted. Their first two campaigns put up over $75,000.&lt;br&gt;
Altogether, over $400,000 in USDC has been disbursed to contributors on Stellar this year, with more to come in the coming months.&lt;/p&gt;

&lt;p&gt;This guide will walk you through contribution basics: what counts as a contribution, how to select issues that suit you, and what good contributors do differently.&lt;/p&gt;

&lt;h2&gt;
  
  
  Firstly, you don't have to write&amp;nbsp;code.
&lt;/h2&gt;

&lt;p&gt;This is usually what stops more people than anything else. From having a misconception that contributing to OSS only involves writing code, to being afraid of writing shitty code in someone else's repo. But before we address the latter, let's discuss what counts as contributions. "Contributing" is a whole category of activities that encompasses the following:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Documentation&lt;/strong&gt;: improving unclear explanations, stale sections, and providing missing examples. This is usually the most needed work in almost every organisation's repos, including Stellar's.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Bug reports&lt;/strong&gt;: finding something broken and writing it up clearly.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Bug fixes&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Writing tests&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Adding new features&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Design and UX contributions&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Finding the right&amp;nbsp;issue
&lt;/h2&gt;

&lt;p&gt;Look for issues that are at the intersection of these three things:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Your stack&lt;/strong&gt;: For code contributions, your first contribution shouldn't also be your first day with the programming language. Let the process be the new thing you're learning, not the language, too.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Your skill level&lt;/strong&gt;: For a newbie, you want to filter for issues containing the "good first issues" label, until you have a hang of the project you are contributing to.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Your interest&lt;/strong&gt;: You're doing this in your free time, and sometimes, attention runs out fast on unrewarded work. Look for projects and issues that you already have an interest in.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;It is very important to avoid overreaching on your first contributions. Say you're ambitious and looking to get noticed by the maintainers, so you pick something hard, and then you get stuck. And because you want to ship by yourself with any means necessary, you paste the whole thing into an LLM and submit whatever comes out.&lt;/p&gt;

&lt;p&gt;Now you've submitted a PR that you know nothing about. And during review, when the maintainer questions your approach, as they often do, you will have no justification. At this point, you've gotten noticed, alright, but not in the way you intended.&lt;/p&gt;

&lt;p&gt;This is not to discourage you from taking on difficult issues or using AI tools. But only do that when you have a decent understanding of the repo. This way, when you get stuck, you can communicate that properly to fellow contributors or the maintainers, and they can easily guide you to finding a solution yourself.&lt;/p&gt;

&lt;p&gt;Conversely, you want to avoid underreaching and going for easy issues all the time. PRs comprising things like typo fixes are safe and feel productive, until months later, you realise that you have a lot of merged PRs and still haven't learned anything since the first one. You should always aim for issues you are at least 60% confident about. Uncomfortable enough to teach you something, but achievable enough that you'll finish.&lt;/p&gt;

&lt;h2&gt;
  
  
  What good contributors do differently
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Read the repo's rules first. &lt;code&gt;CONTRIBUTING.md&lt;/code&gt; and &lt;code&gt;CODE_OF_CONDUCT.md&lt;/code&gt; tell you the conventions and how to approach contributing.&lt;/li&gt;
&lt;li&gt;Ask before you start. Comment on the issue, wait to be assigned. If someone's already on it, find another. And if anything happens to stall you, letting them know you are unassigning yourself lets someone else pick it up.&lt;/li&gt;
&lt;li&gt;One fix per PR. Fixing a bug? Fix only the bug. Reviewers must understand your whole diff before approving. Multiple unrelated changes mean more work to review, which could cause your PR to sit for a while.&lt;/li&gt;
&lt;li&gt;Name your branches and commits clearly. Follow the repo's convention. Most projects use &lt;a href="https://www.conventionalcommits.org/en/v1.0.0/" rel="noopener noreferrer"&gt;Conventional Commits&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Write a PR description that does some of the reviewer's work for them. Your description should include what changed, why, which issue it resolves, how you verified it, and a screenshot if visual.&lt;/li&gt;
&lt;li&gt;Reviews are not rejections. Everyone gets change requests, including experienced contributors. If a review comment confuses you, be sure to communicate that. If you disagree, explain your reasoning, then you may defer.&lt;/li&gt;
&lt;li&gt;Be someone people want to work with. Always thank reviewers and endeavour to help out other contributors.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Usually, the developers who get pulled into paid work and receive recommendations aren't always the most technically capable, but the ones who are easy to work with.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where to ask when you're&amp;nbsp;stuck
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxod3fdoutnbx41jrg4dh.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxod3fdoutnbx41jrg4dh.png" alt="Table showing questions to ask and&amp;nbsp;where&lt;br&gt;
" width="800" height="298"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Contribute?
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;A public record that beats any CV. This matters most for people with no formal credentials to point at.&lt;/li&gt;
&lt;li&gt;You learn how real software works. Tutorials teach syntax, but contributing teaches you how large codebases are organised and what production quality actually means.&lt;/li&gt;
&lt;li&gt;Money, of course. Between Drips and GrantFox, this is now paid work. And it compounds as time goes on, because your reputation determines what you get assigned next.&lt;/li&gt;
&lt;li&gt;The network. The people reviewing your PRs are the people building this ecosystem. That's how developers end up with jobs, grants, and co-founders, by being visibly valuable.&lt;/li&gt;
&lt;li&gt;A path to funding your own project.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Start this&amp;nbsp;week
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Get one PR merged. Go to the &lt;a href="https://stellar-oss-issues.vercel.app/" rel="noopener noreferrer"&gt;issues dashboard&lt;/a&gt;, filter for 'good first issue', find one that fits your stack, and comment to claim it.&lt;br&gt;
Paid platforms have maintainers who check your GitHub profile before assigning anything. An empty profile may get passed over, but two or three merged PRs change that. Do the free ones, then go earn.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;You can claim issues on GrantFox at any time and get paid while waiting for the next Drips wave to open.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Don't do it alone. The &lt;a href="https://bit.ly/stellarwabcircle" rel="noopener noreferrer"&gt;Builder's Circle&lt;/a&gt; is where Stellar Nigeria builds together. We provide support for builders, with a monthly reward pool to earn from while you learn and contribute, and a direct pipeline into SCF funding for your project.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;a href="https://bit.ly/stellarwabcirclehttps://bit.ly/stellarwabcircle" rel="noopener noreferrer"&gt;Apply now&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>blockchain</category>
      <category>opensource</category>
      <category>web3</category>
      <category>stellar</category>
    </item>
  </channel>
</rss>
