Stellar Build Challenge

Move Money Faster, Win Lumens from Stellar.org

The Stellar Build Challenge is an ongoing program to reward
innovation and development in the Stellar ecosystem.

Submit your project by August 15, 2018!
Entries close at 10:00PM PST

Submit your project

#StellarBuildChallenge

2018 Dates

Stellar Build Challenge will occur approximately every three months – keep checking here for the next submission date!

  • August 15th

Entries must be announced on Galactic Talk by August 1st, 2018.

Judges award lumens per submission as they see fit. Judges aim for announcing winners within two weeks of submissions closing.

If you live in a restricted area — any country on the U.S. sanctions list, as well as the states of Alabama, Connecticut, Hawaii, New York, Vermont and Washington — regulations prevent us from sending you lumens. Unfortunately, therefore, residents of restricted areas are not eligible for an award.

All participants will retain the intellectual property associated with their submission. For a list of the winners of the most recent Stellar Build Challenge, click here, and for more information about past Stellar Build Challenges, click here.

Submissions

  • Submissions must be live and available somewhere so people can use/review them.
  • All entries must be announced on Galactic Talk by August 1st at the latest.
  • All relevant questions in the submission form must be filled out.

Submissions for each round must be done at least two weeks prior to judging in order to receive feedback. You must announce your project on Galactic Talk to get feedback from the Stellar Development Foundation and the Stellar community. This will give you time to improve your project prior to final judging.

Projects will be awarded based on their merit. We imagine there will be a comparable pool to previous build challenges, but we don’t want to discourage submissions and effort. High quality projects will receive higher awards. If they’re better than average, they will receive more. If they are low-quality, low-effort – they will receive less. While we won’t automatically discount new projects, we highly recommend that submissions are related to the two challenge goal categories listed below.

Be sure to spend some time reading over the best practices and fine print before you submit.

Build Challenge Best Practices

Wondering where to begin your build challenge journey? Below you’ll find some best-practices for submitting to the Stellar Build Challenge. Follow them, and you just might win. Don’t follow them and you for sure will not.

Have the open-source spirit

One of the most exciting aspects of developing on the Stellar network is that the code is freely available to view and modify. The Stellar Development Foundation is devoted to developing the codebase and the protocol, but they are not the gatekeepers. You can prove your concept by building on top of the framework set by the SDF, or you can build your own framework. If you have a great idea for an application, but the libraries don’t yet exist, create them. Libraries and resources often end up being more valuable in the long-run than the apps they were created to support. Toolkits, libraries, and other open-source resources allow the community to collaborate and expand the functionalities of the entire network.

Choose names wisely

Please refrain from using Stellar or Lumens in your project title. Confusing branding for your project will limit its odds of success; and if your name seems to imply an endorsement from the network or SDF, we will enforce our trademark. Be creative. It’s fine if your tagline is “A Stellar network application” but steer away from names like ‘StellarWalletXD’. A unique name helps your project stand out. Review our brand policy if you have any further questions regarding this.

Submit a detailed application

Be thorough. Shakespeare said that brevity is the soul of wit, but he never won a Stellar Build Challenge, did he? What a bag holder. The soul of applying here is detail. And explanation. Be clear about your project’s intended goals, how it is utilizing the Stellar network, and what are its use-cases. Give examples of how users would interact with your project or how your contributions will solve existing problems. Vague descriptions like “cool”, “clean”, and “best” don’t explain to the community or to the judges how your project will be used. Listing features, a roadmap, and goals will make your intentions clear.

Provide clear documentation

Documentation shouldn’t be an afterthought–without it no one will understand what you’ve built. We know the feeling of relief that comes with writing your final line of code. However, if other developers or users can’t decipher or use your submission, it won’t win. Take the time to write clear and concise documentation. It will help your project grow and it will signal to us that you care about your project’s long-term success.

Engage with the Stellar Community

There are several community forums and chat channels in which to discuss your project. If you find yourself stuck and needing some help, reach out to the many community developers willing to help. For excellent Stellar discussion, we recommend:

Challenge Goals

Contribute to an open-source project in the Stellar Ecosystem

We will reward new contributions to meaningful Stellar-related open-source projects. We’re looking for developers who:

  •  contribute new features and enhancements
  •  work on ‘help wanted’ issues
  •  expand project functionality
  •  improve the user experience
  •  even create or improve the documentation

In short, we want people to make a difference in an existing open-source project.

Develop one of these four new ‘cornerstone’ project ideas

This is your chance to “collaborate” directly with SDF. We’ve written up the following four specs; this is what we most want to see built for Stellar.

Take one of the specs and make something awesome.

For more details on these projects – read our announcement post.

Fine Print

Submissions must be live and available somewhere so people can use them – demos and proposals are not accepted. All relevant questions in the submission form must be filled out. All submissions must have some proof of use of the Stellar protocol. We recommend all entries be completed in English. Entries must be functional (again, no proposals) and accessible in the United States.

One project per submission form entry. One entry for one project. If your project consists of multiple parts / projects that potentially fall under multiple categories, please submit your project as a “Collective”. For example, if your project is a wallet, but with that wallet you’ve created 3 unique subprojects with your wallet — this is a collective.

All entries must be announced on Galactic Talk prior to the date given above. Failure to announce on Galactic Talk by the stated date will lead to disqualification. We require this in order to enable projects to receive feedback from the Stellar Development Foundation and the Stellar community. This will give time to improve the project prior to final judging.

Galactic Talk announcements should answer questions like “what does your project enable users to do,” “why is your project valuable for Stellar,” and “how does your project utilize Stellar.” They should additionally cover what the project supports or requires, for example, specific websites, mobile operating systems, etc.

Galactic Talk announcements for contributions to existing projects should answer questions like “which project are you contributing to,” “what are you doing for the project,” and, if submitting a fork, your motivation for the fork. Contributions to existing projects must be accepted pull requests.

If you live in a restricted area — any country on the U.S. sanctions list, as well as the states of Alabama, Connecticut, Hawaii, New York, Vermont and Washington — regulations prevent us from sending you lumens. Unfortunately, therefore, residents of restricted areas are not eligible for an award.

All participants will retain the intellectual property associated with their submission.

Push requests to, changes to, and forks of any official Stellar Development Foundation SDKs, technology, repositories, etc. are not qualified for the Stellar Build Challenge.

If you intend to utilize the Stellar logo in your project, it must follow the brand policy. Lack of adherence to these standards will result in disqualification. Use of the words “official” in regards to or ambiguity of connection with the Stellar Development Foundation will result in disqualification. Please try to avoid Stellar in your project name.

We review and read all entries. Please do not submit random strings with a valid address. These entries will not be considered.

ICOs, assets, tokens, anchors, and remittance applications are no longer eligible for the Stellar Build Challenge. Tutorials are not eligible for return submissions.

We highly recommend that you focus on this challenge’s goals and guidelines. However, you can submit your application if you have entered it in prior build challenges and not won (or only received an “Honorable Mention”). Please read our announcement blog for more information. Judges will be looking to see that significant improvements have been made. Bonus points will be awarded the more people are using your service. Additionally, it’s always helpful to provide documentation with your submission!

In accordance to US law, all winners will be required to submit KYC documentation and fill out the relevant tax form. Failure to do so will result in your rewards being forfeit.