> For the complete documentation index, see [llms.txt](https://glow-docs.xrpl-commons.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://glow-docs.xrpl-commons.org/program-information/key-processes/submissions.md).

# Submissions

Contributors can submit their own projects to Glow directly, without needing a Scout nomination. This is the self-application path: if you've built or maintained something that contributes to the XRPL ecosystem, you can put it forward yourself.

## How Submissions Work

Contributors log in to the Glow Platform and follow a guided process to submit their own project:

1. **Select or create the project** — Find your project on the platform, or create a new entry if it doesn't exist yet
2. **Submit contribution details** — Provide detailed information about the specific contribution you're putting forward

### Project Management

#### Adding New Projects

When adding a project, contributors must provide:

* **Project name** (required): A unique name for the project
* **Project description** (required): A succinct summary of the project's main goals
* **GitHub repository** (required): The official project repository
* **X (Twitter) handle** (optional): The project's official X/Twitter account
* **Website URL** (optional): The project's website

### Making a Submission

#### Eligibility Screening

Before submitting, contributors must confirm:

* **Are you over 18?** (required)
* **Are you or any project team members located in a restricted region?** (Syria, Iran, Cuba, North Korea, or specific regions of Ukraine)
* **Are you or any project team members on any Sanctions List?**

Submissions that fail any of these eligibility criteria cannot be considered for funding.

#### Affiliation Disclosure

If you are employed by Ripple or an affiliated organization (XRPL Commons, XRP Ledger Foundation, etc.), you must disclose this when submitting. Affiliation does not disqualify a contribution — Glow welcomes independent work regardless of where you work — but the disclosure is shown to Voters, who weigh that context when deciding whether a contribution should be rewarded.

#### Submission Details

Contributors must provide:

* **Project category** (required): Select the category that best describes the contribution:
  * Solving Technical Debt
  * Improving the Core Protocol
  * Improving Existing Standards
  * Creating New Standards
  * Improving Documentation or Creating Example Code
  * Creating Community Tools
  * Supporting Infrastructure
* **Achievement description** (required): A detailed description of the specific contribution (max 2000 characters)

### Post-Submission Process

1.  **Review**: Submissions are first reviewed to confirm they meet basic eligibility and quality standards before being published. This step helps keep the platform free of spam and incomplete or out-of-scope entries.
2. **Community Voting**: Once approved, the contribution becomes visible on the community voting platform
3. **Judge Review**: Judges assess the submission based on specific criteria, including:
   * Verification the contributor is over 18
   * Confirmation they have genuinely contributed to the project
   * Verification the work was done within the last 6 months
   * Confirmation the work was not previously funded
   * Assignment of appropriate shirt size
4. **Application**: Contributors complete the application steps — accepting terms, verifying eligibility, and connecting a wallet
5. **Disbursement**: Approved contributors receive their reward after completing all required steps

## Submission Management

Contributors can view all their submissions for the current Wave, including:

* Project name
* Contribution description
* Submission date
* Current vote count

***

For questions about submissions, contact <info@xrpl-commons.org>.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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://glow-docs.xrpl-commons.org/program-information/key-processes/submissions.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.