# Open Track

The Open Track is for experienced builders exploring novel use cases on Stellar or Soroban. These projects should demonstrate strong teams, creative architecture, and the potential to unlock new ecosystem value.

#### ✅ Who This Track Is For

* Builders proposing novel protocols or primitives that solve for key ecosystem needs and do not fall under other Build Tracks
* Projects with existing traction or deep, proven Stellar / domain knowledge
* Teams who demonstrate a strong track record and development skills

#### 🚫 Who This Track Is Not For

* Builders without much prior experience in domain or the Stellar ecosystem

  → Better fit for [Instawards](/scf-handbook/scf-awards/instawards.md)
* Applications with traction primarily focused on integrating existing tools like wallets, anchors, or passkeys\
  → Better fit for the [Integration Track](/scf-handbook/scf-awards/build-award/integration-track.md)
* Teams replicating existing ecosystem solutions\
  → Explore the [Integration Track](/scf-handbook/scf-awards/build-award/integration-track.md). If you choose to move forward in the Open Track, your submission must clearly explain how your solution meaningfully improves upon existing solutions.
* Developers responding to a specific ecosystem need for dev tools\
  → Check the [RFP Track](/scf-handbook/scf-awards/build-award/rfp-track.md)

#### 💡 What Makes a Good Open Track Submission

* Clearly scoped, technically ambitious product or protocol
* Clear on-chain integration plan specific to the Stellar tech stack
* Milestones and deliverables mapped to mainnet deployment
* Thoughtful budget that reflects team size, timeline, and effort
* Clear articulation of of how your proposed solution will drive onchain growth, and how that growth will be measured
* Full-disclosure on the use of AI-generated and AI-assisted artifacts (docs, code, etc.)
* A market analysis with a focus on the business side and the technical aspects. How is the project different from other, similar solutions, and what value does it provide?&#x20;
* A unified source (like Gitbook) containing all project development documentation, including but not limited to planning, overall roadmap, diagrams, dev artifacts, test plan, and any UI/UX prototypes
* Evidence that your team has previously built and scaled similar products, and that you have the business expertise and commitment to do so again
* Shows a plan to utilize the network's latest strengths to ensure long-term scalability and leverage
* A well-put together video presentation showcasing the team.

#### 📅 Process & Timeline

1. Submit the SCF Interest form and indicate your interest in the Open Track.&#x20;

| Important: If you were referred by a member of the SCF community, make sure to include their unique referral code on this form. |
| ------------------------------------------------------------------------------------------------------------------------------- |

2. Eligible teams will be invited to submit to an upcoming Build round. Submit your Build form before the deadline and choose the Open Track.<br>
3. Submissions are reviewed by 2 reviewers from that quarter’s Open Track Delegate Panel.<br>
4. Teams receive feedback and may revise submissions<br>
5. Eligible submissions enter Community Vote<br>
6. Projects that meet quorum and pass the vote with strong panel reviews are awarded for the round, and receive the first payment of 10% of their total awarded budget.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://stellar.gitbook.io/scf-handbook/scf-awards/build-award/open-track.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
