# Overview Here are the articles in this section: * [Who are we](https://docs.onlydust.com/~/revisions/7IdkIjSMdhNXMn2ADS1I/overview/who-are-we) * [Team & Jobs](https://docs.onlydust.com/~/revisions/uxgoIhWZHG8NrpMsRfE3/overview/team-and-jobs) # Who are we > We find and fund elite developers working on side projects that are so complex that AIs/agents fail to help them code. Yep, that's us. \ But how did we come to this? #### **2023 - 2025:** Become the "Open Source home" We started in 2023 by building a platform to contribute to **open source**. Over the years, we’ve worked to: * Make it easy for any maintainer to get visibility, contributors, and actual help * Make it easy for any contributor to find a project and a good first issue (without reading 14 outdated READMEs) * Provide a "matching engine" where contributors are recommended projects based on their skills and interests. * Show metrics for maintainers: who’s looking at your project, who applied, and how experienced they are. #### **2025 - now:** ***We spent years mastering something most companies never crack: finding elite developers and funding their best work.*** By 2024, we'd distributed $15M to 400 open source projects, building an expertise in what makes truly exceptional code, and how to fund it without micromanagement. Then we moved to San Francisco, and the top AI labs pulled us aside with a problem: They confessed a hard reality: their coding agents were acing toy benchmarks but failing catastrophically on real-world systems, on the kind of intricate, closed-source, deeply contextual code that OnlyDust’s network lived for. That’s when it clicked. We reoriented everything toward a new mission: funding engineers whose code breaks AI. Today, OnlyDust (operating under our Ctrl+G brand for AI labs) partners with the world’s top research teams to turn elite, private codebases into the most rigorous coding benchmarks ever built. We no longer just fund open source.\ We fund the *impossible*, so machines can one day catch up to human ingenuity. # Vision & Roadmap We help people contribute to open source. That’s it. Whether you're a contributor looking for something meaningful to build, or a maintainer looking for actual humans to help - not bots - we're here. ### 2025 - Become the "Open Source home" Up till now, people may have known us as the place to contribute to Web3. That’s not wrong - but it’s not the whole story. In 2025, we wanted to change that perception. We're building the platform to contribute to **open source**, full stop. We’ve worked to: * Remove the crypto/web3-only label * Bring in projects from across the open source universe (infra, frameworks, devtools, AI, etc.) * Make it easy for any maintainer to get visibility, contributors, and actual help * Make it easy for any contributor to find a project and a good first issue (without reading 14 outdated READMEs) * Provide a "matching engine" where contributors are recommended projects based on their skills and interest. * Show metrics for maintainers: who’s looking at your project, who applied, how experienced they are. * Have a very simpley onboarding flow that doesn't block. **If you're talking about open source and onboarding, OnlyDust should be part of that conversation.** #### What is coming up: **AI-assisted collaboration (but still human)** We’re building tools so contributors and maintainers can: * Understand codebases faster * Write issues and PRs more confidently * Use AI to help review and improve contributions * Delegate repetitive tasks without losing control * Let contributors define features, set directions, and vote on priorities * Use agents to implement code, tests, docs, etc. * Let maintainers orchestrate, guide, and review - with as much or as little control as they want **Gamification (the good kind)** Contributing should feel rewarding. * XP, levels, badges (not just for fun - some perks included) * Better profiles contributors can show off * Visible progression tied to actual contributions (not vibes)
Our end-goal: OnlyDust to become the platform that powers AI-native collaboration. You bring the brains and intent. The machine handles the repetition and boilerplate. # How do we flow A common question we get: how does OnlyDust make money? The answer is simple: **sponsorships**.\ \ We partner with companies and organizations who want to support open source and reach developers like you. They fund the platform - and we put that funding to work where it matters. #### Where the Money Goes We reinvest the majority of sponsorship revenue back into the open source community. * In 2024, 72% of our income was distributed directly to maintainers and contributors for their work (PR activity and onboarding activity). * In 2025, this amount goes through our 3-month grant program, supporting long term contributors and maintainers across the space. * Every month, we add $15,000 of our own budget toward: * Exclusive merch * Travel and conference grants * Event tickets * And other meaningful rewards for active contributors Our goal is to make contributing to open source recognized, supported, and rewarding -not just technically, but financially and personally too.\` # History & Story #### **2022:** You don’t crack collaboration by being onchain After exiting our growth agency with Paco [(Germinal)](https://www.lesechos.fr/start-up/deals/marketing-spaag-rachete-germinal-la-start-up-fondee-par-gregoire-gambatto-1379869), we have decided to build in the web3 space. At this stage, there is something we are passionate about: collaboration. We want to create a decentralized world of work, by using the superpowers of DAOs (”group chats with bank account”). We are sure the future of the collaboration is on-chain. Transparency brings accountability. Instant money transfer brings distribution of the value created. Decentralization brings censorship resistanc After launching three products, we learned the hard way that blockchain technology isn’t solving everything. In retrospect, this conclusion was inevitable, but in the euphoria of the moment, it wasn’t so obvious. DAO tooling? No Bounty platform on Ethereum? No Bounty platform on Starknet? No Waiting for our transactions, we have begun to contribute to open source in the Starknet ecosystem. Collaboration at scale was happening for real in this world. But everything was broken. We have decided to find the biggest problem of the OSS ecosystem. It was money allocation. After launching a few [prototypes](https://www.notion.so/B2B-Content-Strategy-1af44b682a808099916ec3aa1832c6ce?pvs=21) (not onchain, you guess well), we were ready for the big launch.
#### **2023: Lack of funding is** not the real issue of open-source collaboration Metrics January 2023: * 15 active projects * 105 registered devs * 41 active devs 1st January, the launch of the product. We have successfully organized a few big [community events](https://www.notion.so/Starknet-Building-Tel-Aviv-9c4e15aea5a94be8b8f37e0b800cfcd3?pvs=21), and a first big [conference](https://www.starknet.cc/). The community begins to use the product, and gives us a lot of feedback. We are allocating more and more grants during our events. Yalaaaa. But it’s not scaling. The contributors connect to the platform for the unique purpose of withdrawing their money. They can’t do anything else. Maintainers have more possibilities, but let’s be honest, there is no value for them if they don’t have a grant to allocate. We contact a lot of ecosystems to sell them the possibility of using the platform to allocate grants. Over time, it begins to be obvious: grant allocation is just a feature. A way for some projects to reward, in some cases, contributors. We need to think bigger. We decided that our focus on grant strategy wasn’t enough, and we raised money on the thesis of becoming [the place for OSS contribution](https://www.notion.so/Situation-Report-OnlyDust-May-2023-ddd7958a5af54629b5ada660ad80caea?pvs=21) with [fabric.vc](http://fabric.vc) But our velocity is decreasing rapidly, so we decided to focus on it. A grand vision can’t be achieved without a great product.
#### **2024:** AI can kill the open-source collaboration Metrics January 2024 * 116 active contributors * 31 active projects * 1700 devs registered We launched the first version of our OSS online event (now The Wave) in less than one week. One year later, we had 400 contributors merging a PR, compared to 28 in the first edition. When you do something great with consistency, it compounds over time. Matching devs to work together has a real value. And the most important is yet to come. Working in the blockchain world helped us to understand something fundamental in our business. 2 things are very different in this industry, and they allow us to see the future → By default, everything is open-source → There is a direct potential upside to the open-source contribution So we have seen, in first hands, people trying to game the system. We have seen them using AI, the so-called “ChatGPT devs,” spamming maintainers in the hope of an airdrop or a financial reward. Know that this trend is everywhere. But we have seen it first, and it gives us an unfair advantage. At the beginning of the year, contributor were only able to withdraw their rewards with a KYC process. Now, they can apply to issues and discover projects. Maintainers can manage their contributors. The product is beginning to evolve in the right direction. It’s not enough.
#### **2025:** AI can solve the collaboration problem Metrics January 2025 * 7400 registered devs * 192 active projects * 1100 active contributors Greg moves to SF and discovers that the world is moving faster than expected. We need to accelerate. We need to serve the entire OSS ecosystem. Build trust in a very demanding community.
# Team & Jobs #### The Gang We are a team of 7. There is the growth, finance, and the tech team, along with our two co-founders. The tech team has back-end & front-end devs. All with their very own talents and specialties. They are the ones who help build the product that you see today. And debug in under 30 minutes. Yep, they are that reactive :wink: The finance team speaks for itself! This is where the team makes sure that we're not financing weird stuff and that those who use our platform are legit users. The growth team is probably the most "visible". They're the ones who are contacting you daily and making sure everything is going well. \ \ We are based in San Francisco. \ \ Every month, we gather together during our team off-site, because we like each other :).
#### Jobs Currently, we do not have any job openings! \ \ But hey, if we do, we will be sure to communicate on it. # Maintainers - hello! # How to get started The process is quite simple. All you need is your GitHub account. And your repo(s).
Then sign up and go through the very quick and easy onboarding steps. You will be asked to give GitHub authorizations for synching your organisation(s) & repo(s). We know this looks scary so we made a section ([Why GitHub authorizations](https://app.gitbook.com/o/MQQDjhOXRySQPsao0aZ0/s/FetEvDuVEZkpYJ6kurbf/~/changes/4/maintainers-hello/why-github-authorizations)) regarding that on the next page. #### The Steps 1. So first connect yourself with your GitHub account. 2. Once you've given access to authorize OnlyDust via GitHub, sync the organisation you'd like to have on the platform. 1. If you don't see you're organisation, add it in.
3. Then select the repo(s) you'd like to sync. Hope you like my repo name :wink:. Inside Joke. 1. If you can't find your repo, you can contact us. Make sure that you are owner of your repo or that you have been granted access by the owner.
4. Once that is done, you'll be able to see your cool dashboard. 1. In the "issues inbox" you'll be able to manage your issues, review applicants, track progress. Hence why it's important that you assign your issues! 2. In the "PR inbox" you can review and merge the PRs directly. 3. In the "Waves" section, you can list your repo(s) to onboard new contributors. [More on this in over here](https://app.gitbook.com/o/MQQDjhOXRySQPsao0aZ0/s/FetEvDuVEZkpYJ6kurbf/~/changes/4/maintainers-hello/oss-wave). 4. And then we have cool new things coming up :eyes:.
5. What if you'd like to add another repo to OnlyDust? \ a. Head over to the settings under your name. ![](/files/bMqRSomxzYcOHSEPtFOT) b. Once you've clicked on settings, you can either add in a new organisation or sync your repos:
c. If you have your organisation there already, go into "synced repositories" and add another repo to sync (click on "edit" to open up a tab to sync other repos):
And now that you're all signed up, you’ll get cool emails from our CEO. So that is your first touchpoint. Pretty cool, no? Your second touchpoint is joining our [community on Discord](https://discord.gg/sVDvdKqPqN).
# Why GitHub authorizations ### The overview It’s not scary, promise. We need the authorizations in order to allow you to have the BEST EXPERIENCE ever on OnlyDust. Or else it’s really limited and actually, not worth it 😟.
So why do we ask it: * We need to ensure that you’re truly owner of the GitHub organization (to avoid scams and unpleasant things). If you’re not, we need to you ask the owner (the admin) to grant the access. * Github enforces a rate limit on its API \~ 5000 calls/hours. It’s not enough when we have more than 20K repos on our platform that we need to sync, in real time. Hence, to bypass this limitation, we need to use integrations provided by GitHub with the GitHub app. * By accepting the authorizations, you’ll allow us to have “write rights” (tongue twister there!) so that when you assign/unassign issues on our platform, it shows up directly on GitHub. So, the best way to do that is through the Oauth token feature from the GH app. ### The details More info over here written by our Head of Engineering. The Contributor App and Maintainer App have **separate authentication flows**. That’s by design. They need different permissions, and they handle different types of GitHub interactions. *** ### GitHub Authentication Models #### GitHub OAuth App Used for logging in with a personal GitHub account. * The user connects their GitHub account and authorizes the OnlyDust OAuth App. * This allows us to **act on their behalf** using a personal token. * Example: when a contributor applies to an issue, we comment on that issue **as the user**. GitHub shows the user as the comment author. OAuth App is always linked to the user’s **personal GitHub account**, not an organization. *** #### GitHub App Used when someone installs the OnlyDust GitHub App on a GitHub **organization**. * This grants us access to the selected repos with the permissions defined in our app config. * We receive a GitHub App installation token, which we use to: * Call the GitHub API with the appropriate scope * Receive events via GitHub webhooks This is org-level access, managed through GitHub’s installation and permission flow. *** #### GitHub App with OAuth Enabled GitHub lets you enable OAuth on a GitHub App. * We use this setup to get **both**: * Access to act on behalf of the user * Access to the organization and its repos This hybrid approach is used in the Maintainer App. *** ## Maintainer App Maintainers log in using the **OAuth flow built into our GitHub App**. #### How it works 1. **Login via OAuth** Maintainer logs in with their personal GitHub account using the GitHub App’s OAuth flow. 2. **Install the GitHub App** After login, they are redirected to GitHub to install the app on an organization where they’re a member. 3. **Request or grant access** * If they’re a member (not admin), they request access * If they’re an admin, they can grant access immediately * They select the repos to grant access to 4. **Return to Maintainer App** Once installation is complete, they’re redirected back to OnlyDust to select which repos to sync. *** ### Why OAuth + GitHub App? In the past, we used the GitHub App alone. That had problems: * Users could manage repos without being actual members of the GitHub org * GitHub’s permission model wasn’t enforced Now, by adding OAuth: * We get a user token with the **real permissions** of that user on the org * GitHub enforces what actions they can and can’t do * Example: if a user can’t assign issues in the org, they won’t be able to do it on OnlyDust either More on [how this works here](https://docs.github.com/en/apps/creating-github-apps/authenticating-with-a-github-app/generating-a-user-access-token-for-a-github-app).
*** ### Permissions Requested by the GitHub App #### Repo-level permissions (all selected repos, including private) * Issues * Pull requests * Repository metadata * Collaboration settings These are visible during installation and defined in the GitHub App config. #### Organization-level permissions * Read access to metadata * Used to verify org membership * Enforces permission checks through OAuth intersection *** ### Why Maintainers Must Install the GitHub App #### 1. Enforce org-level access Only org members (or approved users) can install and manage repos via OnlyDust. One org **owner** needs to install the app and grant access. #### 2. Avoid GitHub rate limits GitHub caps API usage at 5000 calls/hour per token. That's not enough for our scale. Using GitHub App installations: * Each org gets its own scoped token * API usage is spread across orgs #### 3. Real-time events via webhook We receive webhook events from GitHub: * Issue creation * PR activity * Assignments, etc. This reduces the number of API calls and keeps data up-to-date. *** ## Contributor App `https://www.onlydust.com/` Contributors log in via the **OnlyDust OAuth App**. Here's how permissions work: #### Permissions requested **`read:user`** Used to: * Fetch contributor profile and public GitHub activity * Feed our recommendation engine and contributor scoring * Display profile data in the app We call the GitHub API using the contributor’s token. This avoids rate-limiting issues (5000 req/h per token) that we’d hit using a single platform token. No GitHub connection = no real login. Contributor gets read-only access. This is required only when applying to an issue. * First time: contributor is asked to grant this permission during the application modal * Later applications: no prompt unless the permission was revoked * If permission is revoked: we’ll ask again This permission lets us comment on GitHub issues **as the contributor**. [GitHub OAuth scopes reference](https://docs.github.com/en/apps/oauth-apps/building-oauth-apps/scopes-for-oauth-apps) over here.
# Using the dashboard Behold the lovely maintainer dashboard! Easy to use and makes your life much easier.
### Issues Inbox Remember, everything is synchronized between GitHub and OnlyDust. So over here, you'll be able to manage your issues, track their progress and assign to the contributor that you think best fits. * You can see those that applied to your issue * You can see the discussions in the issue * You can filter out the issues you would like to see as well as the repo * You can add the issues you want to participate to the Wave if your repo was accepted *(more info on that in next section)*
{% hint style="info" %} If you're project is participating in our OSS Wave, you can add the issues you'd like contributors to work on directly here. More info in next section. {% endhint %} * You can see the metrics/reputation of the contributors that have applied to your repo. For example with the below you'll be able to see that the contributor is highly recommended.
You can also see their pending applications, when they registered on GitHub and their language proficiencies. That way you can make a better decision on whether you want to assign or reject the application. It's a good way to filter out spammers. **Important!:**** We highly recommend that you assign a contributor to an issue. It allows the contributor to know that they can start working on it.** * Lastly, you can include issues you'd like to have participate in the OSS Wave. More on what this event is about in the [next section](/maintainers-hello/oss-wave). ### Pull Requests Inbox Over here, you'll be able to track the PRs that have been made. What you'll be able to see: * the link to the PR, the contributor that made the PR and the repo that the PR was made in. * the status of the PR. Is it in progress? In review? What's up? * when you click on a PR, you'll be taken back onto GitHub to finalize your review and merge or not the PR. * then, you can filter the PRs according to whether the PRs are still open, merged, in draft mode or those that you have closed. Better tracking!
* If you're flooded with PRs, you even have a handy search toolbar to search by title or contributor (author) name. {% hint style="info" %} What are the indicators? If the PR is of good quality, if the PR answered the issue at hand, if tests and CI has been passed. {% endhint %} ### Waves We'll talk more about the event in the next section, but in one quick sentence: these are monthly online events where you can attract and onboard a number of contributors onto your repo.
All you need to do is list your project, go through the steps to select the repos you want involved, fill in the application form and we'll validate if all is good.
**Special mention:**** During the filling out of the application form, make sure that you choose the category(ies) that most fits your repo. This helps when contributors filter out repos according to the category of their choice.** Once that is done, you can add issues to the Wave (this brings you back to the Issues inbox). An automatic label will be added to the issues you want for the OSS Wave for better visibility. Then all you need to do is wait till D-Day! We'll be sending out emails and catching up with you on [Discord](https://discord.gg/sVDvdKqPqN) so that you're not alone in the process. **FYI:**** If you didn't complete the listing of your project, you'll see on the dashboard that the status shows as "To Complete". Just click on it to go through the process. The Status changes to "Validated" or "Rejected" when it is final.**
# OSS Wave ### What's it about The best monthly event ever. Bragging a little bit, but it’s kind of true. It’s a moment in time when maintainers and contributors get together to ship, ship, ship! In just 10 days. We partner with strong repos that are looking to onboard motivated devs to help them fix their issues quickly. Over 5500 devs & 500 repos (probably more, can’t keep up!) have joined the Wave.
### Why participate? It’s the perfect time to attract motivated devs - contributors know maintainers are actively looking during this period.\ .\ It’s your chance to showcase your repo, onboard talent, and boost progress. Many maintainers have found long-term contributors through the OSS Wave, which is why we’ve been running it for over a year and a half now! **Bonus:** participating increases your chances to earn perks like grants and limited-edition merch. ([More info in the grant eligibility](/maintainers-hello/grant-eligibility)). {% embed url="" %} ### How it works *(Have a look at the using the* [*dashboard section*](/maintainers-hello/using-the-dashboard) *on step by step details).* If you have repo(s) that you'd like to have participate in the next Wave, simply register them.
When your repo is accepted, you'll be able to add in the issues you'd like to have contributors help you on (these steps are in the "[Using the dashboard](/maintainers-hello/using-the-dashboard)" section).
### Now in more detail When the OSS Wave starts, contributors will be looking at the repos that are participating in the Wave. All this is done through the OSS Wave page. Before it starts, you'll only be seeing this:
And boom, when it's live, a whole new page takes action! * The OSS Wave lasts \~10 days. * We strongly recommend contributors and maintainers stay active and communicative throughout the week. * To keep things smooth, make sure there's a clear way to reach you - Telegram, Discord, or whatever works best. * Contributors can submit PRs anytime during the week, but we **highly** recommend they submit all final work (even drafts) by Day 10 to show progress. * You’ll then have two extra days to review and merge. Keep us posted along the way. Any frustrations, any questions, or just to say hi. [Discord](https://discord.gg/sVDvdKqPqN) is the way to go. # Best Practices We've asked a few maintainers in the space to let us know what they considered is important to attract good devs to their repos. Here are a few of their thoughts: #### 1. Docs, Docs, Docs Good documentation is essential for attracting and retaining contributors. Make sure your repo includes: * A clear and informative README that outlines what your project does and why it matters * Well-defined contribution guidelines to help newcomers get started * A codebase overview so contributors can navigate the project confidently * A project roadmap highlighting priorities and where help is most needed * Info on how to set things up if needed * A contact method (email, Discord, Telegram, etc.) for better communication Basically, the easier it is to understand your project, the more likely others are to contribute. #### 2. Make issues look easy to contribute to Help contributors help you by preparing your issues properly: * Label your issues clearly (e.g. `good first issue`, `help wanted`, `frontend`, `bug`) * Write detailed and specific descriptions * Keep issues current and relevant This saves contributors time and lowers the barrier to getting started. #### 3. Be present & reactive Visibility matters. You are free to use our [Discord channel](https://discord.gg/sVDvdKqPqN) to connect with potential contributors: * Post about your project, especially during OSS Waves * Share what kind of profiles you’re looking for (languages, experience levels, etc.) * Stay responsive and available **-** especially during the first 10 days of an OSS Wave when most contributions happen :eyes: Also - feedback is also greatly appreciated. Tell the contributor when they've done a good job (always nice to hear!). But equally tell the contributor if they've done something poorly. No one likes to be left hanging. #### 4. Keep your repo active An active repo signals a healthy project. Merge PRs when ready, review and respond to issues, and regularly update documentation. Even small signs of activity can help reassure new contributors that their time will be valued. \ **5. Assign issues** Obviously, you can maintain however you want your repo, but we would suggest assigning your issues to contributors. It makes things easier for tracking and for the contributor to know they've been assigned to the issue and can work on it straight away. # Grant eligibility Some projects on OnlyDust may be eligible for grant funding. We work with sponsors who support high-impact open source projects and want to see them grow. Grants can reach up to $5,000 (*it can be higher*) over a period of 3 months, based on: * **Consistent activity**: regular progress on issues, merged PRs, and updates * **Contributor engagement**: welcoming and onboarding contributors effectively * **Clear direction**: execution on a roadmap, even if lightweight We also keep a few grant spots open for promising early-stage projects -especially those that show initiative, strong structure, and responsiveness. ### Where do the grants come from? The grants come from our sponsors. 72% of these grants go into projects and [fellowship program](/contributors-hiya/onlydust-fellowship). Currently, we have ongoing grants from Starknet, Stellar and Flare Network. ### How to increase your chances Participation and visibility go hand-in-hand. Here’s what can help you get noticed: * **Join the OSS Wave**: Projects in Waves are featured more prominently and reviewed more frequently * **Engage with contributors**: Be responsive, present, and communicative during contributor activity * **Structure your repo (check out the** [**Best Practices section** ](https://app.gitbook.com/o/MQQDjhOXRySQPsao0aZ0/s/FetEvDuVEZkpYJ6kurbf/~/changes/5/contributors-hiya/best-practices)**for more info)**: * Write a clear README * Maintain a roadmap * Label and scope your issues * Include onboarding and contribution docs * **Show that you're active**: Regularly open and close issues, merge PRs, and summarize progress monthly. > **Visibility is earned**, not automatic. We manually review activity and engagement across the platform on a rolling basis. ### What we look for We assess projects using a combination of visibility signals and contribution quality: * **Activity**: merged PRs, issue velocity, responsiveness to contributors * **Structure**: clear roadmap, well-described and tagged issues * **Community-building**: onboarding, mentoring, and inclusive practices * **Relevance**: alignment with real-world use cases and ecosystem maturity Consistent quality and contributor experience matter most. ### New vs. Existing Projects Being new is not a disadvantage. Mature projects may have more data and traction, but newer projects can rise quickly if they: * Ship consistently * Onboard contributors clearly and kindly * Present a compelling, structured vision Visibility and funding eligibility are reassessed monthly - if you're not hitting the marks, you can be dropped out. ### Not Eligible Yet? We still have your back If your project isn’t yet eligible for a grant, you may still benefit from a **Fellow Contributor (more info in the** [**OnlyDust Fellowship** ](https://app.gitbook.com/o/MQQDjhOXRySQPsao0aZ0/s/FetEvDuVEZkpYJ6kurbf/~/changes/5/contributors-hiya/onlydust-fellowship)**section)**. Fellows are selected developers, funded by OnlyDust, who contribute actively to projects we (and the sponsors) believe in. They bring: * High-quality engineering support * Increased project velocity * Mentorship for other contributors * A commitment to open source values Fellows are matched with projects based on skills, needs, and potential impact. We handle the logistics and the introduction - your job is simply to collaborate and integrate them into your team. ### FAQ **Do top projects get all the funding?**\ Funding is prioritized for top-ranked, high-quality projects, but it's not exclusive. Projects showing consistent growth, strong community engagement, and good structure can still be selected for grants in future cycles. **How is a “top-ranked” project defined?**\ Through a mix of quantitative signals and manual review, including: * Contribution history and recent trends * Roadmap and issue quality * Contributor onboarding success * Relevance and real-world utility **How can smaller or less visible projects attract contributors?**\ Focus on being contributor-friendly: * Write clear, scoped, and labeled issues * Respond promptly to PRs and questions * Offer documentation to onboard newcomers * BE ACTIVE. In general. Not just during the OSS Wave. Show that you care about your repo. **Still have questions? Go into our** [**Discord**](https://discord.gg/sVDvdKqPqN) **and ask there.**
# Contributors - hiya! # How to get started Easy peasy. All you need is to have your GitHub account and go through quick and easy steps to get yourself started. 1. First, sign up as a contributor.
2. Accept the code of conduct *(won't put a screenshot here as it's boring BUT important to read and accept of course...).* 3. Add in your contact information. We highly recommend to add in the ones that you're okay to be contacted on. 4. Select the languages that you are fluent in. This helps us to recommend repos according to your skills. Super important. If you don't see your language just search for it (we show the most popular ones).
5. Then, select the topics that you like. Whether that's AI, gaming, dev tools... 6. And then voilà! You'll see a personal dashboard with top picks for you, projects that welcome newcomers, or those that are trending in your interests. 1. You can use the section to explore different categories or use our "browse" tab if you want to go further.
And after all this, you’ll get cool emails from our CEO. So that will be your first touchpoint :sunglasses:. Your second touchpoint is joining our [community on Discord](https://discord.gg/sVDvdKqPqN). ### # Why GitHub authorizations ### In a few words We need the authorizations in order to allow you to have the BEST EXPERIENCE ever on OnlyDust. Or else it’s really limited and actually, not worth it 😟. Contributors log in via the **OnlyDust OAuth App**. This is required only when applying to an issue. Here's how permissions work: #### Permissions requested **`read:user`** Used to: * Fetch contributor profile and public GitHub activity * Feed our recommendation engine and contributor scoring * Display profile data in the app We call the GitHub API using the contributor’s token. This avoids rate-limiting issues (5000 req/h per token) that we’d hit using a single platform token. No GitHub connection = no real login. Contributor gets read-only access. * First time: contributor is asked to grant this permission during the application modal * Later applications: no prompt unless the permission was revoked * If permission is revoked: we’ll ask again This permission lets us comment on GitHub issues **as the contributor**. [GitHub OAuth scopes reference](https://docs.github.com/en/apps/oauth-apps/building-oauth-apps/scopes-for-oauth-apps) over here. # Find your first issue ### Manage your applications & start contributing! Every month we do a 10-day long sprint where a number of selected projects open up issues for contributors to tackle. This is known as the [OSS Wave](https://app.gitbook.com/o/MQQDjhOXRySQPsao0aZ0/s/FetEvDuVEZkpYJ6kurbf/~/changes/5/contributors-hiya/oss-wave) :ocean:. But if you fancy starting contributing before the event, you can start looking at repos that have open issues ready. You'll see that with the little bubble which announces how many open issues there are:
If you're interested in this repo for example, click on it and you'll see more descriptions of what it's about.
If an issue that is open catches your attention, simply click on it and click on the "I want to work on this issue" button on the left hand side of your screen. If it's your first time, you'll be directed to ask for authorizations via GitHub ([read here](https://app.gitbook.com/o/MQQDjhOXRySQPsao0aZ0/s/FetEvDuVEZkpYJ6kurbf/~/changes/5/contributors-hiya/why-github-authorizations) as to what is asked). This is to allow us to be able to synchronize your work on GitHub onto the platform.
A window will pop up asking you to apply. Make sure you give details on why you would be a good fit for this issue to up your chances. When you submit your application, the comment will automatically appear on the issue in question in GitHub.
Then wait! If the maintainer thinks you're a good fit, they'll assign you and you'll receive a notification. And then...up to you to work your magic! ### Managing your applications If you want to know the status of your applications and where things are at, we have a very handy dashboard for you. Head over to your bubble head (the icon on the top right of your screen) and click on "**My Applications**".
Over here, you'll be able to view your applications and status. You can see issues that you've been assigned to, those that expecting PRs, in review, closed or completed! Perfect to know where things are at and to jump back into issues that you need to work on. The more you contribute, the more you can be eligible for our [OnlyDust Fellowship](https://app.gitbook.com/o/MQQDjhOXRySQPsao0aZ0/s/FetEvDuVEZkpYJ6kurbf/~/changes/5/contributors-hiya/onlydust-fellowship) program and perks. # OSS Wave ### What's it about It's THE event of the month that lasts around 10 days. The Wave is a moment in time when maintainers from a variety of repos create or open a number of issues for contributors to tackle. We partner with strong repos that are looking to onboard motivated devs to help them fix their issues quickly. Over 5500 devs & 500 repos (probably more, can’t keep up!) have joined the Wave. ### Why participate? It's the perfect time to explore projects across the space, get onboarded, build your skills and be in direct contact with the maintainer. This is when everyone is active and when you can get instant feedback on your work. Many contributors have found amazing projects to contribute to in the long-term, leading them to furthur opportunities. Basically, great for your resumé :wink:. **Bonus:** Participating increases your chances to earn perks like fellowship grants and limited-edition merch. ([More info in the OnlyDust Fellowship](/contributors-hiya/onlydust-fellowship)). {% embed url="" %} ### How it works *(Have a look at the using the* [*Find your first issue*](/contributors-hiya/find-your-first-issue) *on step by step details).* In order to participate, you will need to register to "Join the Wave". Before it starts, you'll be seeing a page similar to this:
And boom, when it's live, a whole new page takes action! As a contributor, you'll be able to browse through open issues and repos looking for contributions. * You can use the filters that are provided to have a better look at issues that match your skills or repos that interest you. * Once you find an issue that you'd like to tackle, go through the steps in the [*Find your first issue*](/contributors-hiya/find-your-first-issue) section. Other info: * The OSS Wave lasts \~10 days. * We strongly recommend contributors and maintainers stay active and communicative throughout the week. * To keep things smooth, make sure you always let maintainers where things are at. * Contributors can submit PRs anytime during the week, but we **highly** recommend they submit all final work (even drafts) by Day 10 to show progress. * Maintainers then have two extra days to review and merge. All info are sent through our mails (so keep an eye out on that) and on our [Discord](https://discord.gg/sVDvdKqPqN). # Best Practices - must read If you're contributing to open source through OnlyDust, here's how to do it right -for maintainers, for the community, and for your own learning. #### 1. Pick a project that you care about Choose a project that interests you technically or helps you grow. You'll stick with it longer, do better work, and get better feedback. #### 2. Start with the Docs and Issues Before touching any code: * Read the **README**, **contribution guidelines**, and setup instructions * This may sound like a no brainer, but READ THE ISSUE before saying that you can work on it. Pick issues that fit your skills or else you're wasting everyone's time. * Ask questions if something’s unclear. Maintainers appreciate it when you check before diving in #### 3. Communicate, communicate, communicate Super important. It's collaborative work. Always keep maintainers and the community up to date with where things are at: * Comment on the issue you’re picking up * Open a draft PR early if possible - helps maintainers follow your thinking * If you get blocked or need more time, say so * If you stop working on something, let others know #### 4. Use AI Responsibly AI can definitely boost your productivity - but you’re still responsible for what you submit. Don't abuse it. **Good uses of AI (to help out):** * Exploring unfamiliar frameworks or tools * Generating boilerplate, test scaffolding, or starter code * Summarizing large files or docstrings * Reviewing PRs for structure and clarity **Not acceptable:** * Copy-pasting AI output without reviewing or testing * Submitting work you don’t fully understand * Generating meaningless or bloated PRs for visibility Maintainers and other devs will notice when work is AI-generated and low-quality. It's tiresome and just overall reflects badly upon you. #### 5. Quality > Quantity * One well-crafted PR beats five rushed ones * Stick to the repo’s conventions * Add tests when it makes sense * Write good commit messages * Keep your changes scoped and purposeful Remember that you’re contributing to something others rely on! #### 6. Link your PR to an issue (why it's important) When you’re working on an issue, always link your pull request to it. This helps maintainers track progress, understand context, and close things cleanly once your work is merged. In your PR description, include: ``` Fixes #123 ``` or ``` Closes #123 ``` Where `123` is the issue number. You can also use: * `Resolves #...` * `Related to #...` (if it’s not directly solving the issue) Once your PR is merged, GitHub will automatically close the linked issue **Bonus tip:** Add a short description of what the PR does and *why* it matters. Maintainers appreciate the context. [More info here on GitHub](https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue). #### 7. Be a Good Teammate * Respect that many maintainers are volunteers * Stay open to feedback * Help onboard others when you can * Be clear, direct, and kind in all communication #### 8. Track Your Work During OSS Waves If you’re contributing during an OSS Wave, you have 10 days to push your work. Even if it’s not done, submit a draft PR by Day 10 so the maintainer can see what you’ve been working on. They'll have two extra days to review. # OnlyDust Fellowship Contributing to open source on OnlyDust can open a lot of doors - if you show up, contribute meaningfully, and stay consistent. The more active and reliable you are, the more visibility you get on the platform, and the more chances you have to earn perks, mentorship, and even funding. ### What is awaiting you **Exclusive Merch**\ We send out limited-edition merch to contributors who are active and engaged. You’ll get something cool once you start contributing (and merging top PRs) - and if you keep going, you’ll unlock higher-tier drops that reflect your impact in the space. **Access to Mentors**\ Some contributors gain access to experienced open source developers who can offer technical guidance, review your work, or connect you to opportunities. This can happen online or in person, and in some cases, we’ll even cover your travel and conference ticket if there’s an event worth attending. **Fellowship Program**\ The Fellowship is our way of supporting top contributors who want to go all-in. It’s a 3-month funding program where selected contributors may receive between $300 and $5,000 per month to keep building in open source. You need to show consistent, high-quality contributions in open source. Contributing to a project backed by one of our sponsors can increase your chances, but any public repo listed on the platform is fair game. ### How the Fellowship works Fellows are selected from the pool of the most active and impactful contributors on the platform. There’s no strict formula - but here’s what we look for: * You’ve been contributing consistently over time * Your pull requests are well-thought out, scoped, and relevant * You don’t just write code - you communicate well, collaborate, and improve the project for others * You’re active on issues, ask the right questions, and respond to feedback It’s not about having the most PRs. It’s about having quality work done, helping move things forward, and building trust with maintainers and other contributors.
* We run manual reviews to select Fellows. We look at your full contribution history, including past OSS Waves, and we consider context - not just numbers. If eligible, we'll invite you to a quick call to learn more about your goals and where you want to grow. * Once selected, you’ll receive funding for up to three months and we’ll help connect you with a project, ecosystem, or organization where you can have impact. **This is reviewed on a monthly basis.** At the end of the fellowship, you’re free to continue contributing, switch focus, or even launch something of your own. We’ll still support you however we can. For all [admin related subjects go over here](/admin-stuff). *** ### FAQs **Do I need to be ranked to get selected for the Fellowship?**\ While we’re working on a quality-based scoring system that can be visible to all, selection is mostly manual and based on the consistency, depth, and relevance of your contributions. **Will merged PRs matter more?**\ Merged PRs definitely help, but it’s not about just getting merged. What we care about:\ – Is your contribution of high quality?\ – Were maintainers happy with you?\ – Are you helping the project move forward? **I’m new - do I have a shot?**\ Absolutely. Some of our most promising contributors were new just weeks before they were selected. If your work is strong, consistent, and well-communicated, you can rise quickly. **Is there a fixed number of Fellows selected each month?**\ We aim to fund as many contributors as possible based on available sponsor support. We review monthly and rotate fellows every 3 months, so there’s always a new cycle and new opportunities. **Will my past contributions count?**\ Yes. Your previous PRs, activity during OSS Waves, and overall participation on the platform are part of your contributor history. They help us understand your journey and impact. # Admin stuff # KYC/KYB - ID verification For those that are eligible to OnlyDust Fellowship or the Grant program we will ask to verify your identity. We don't want to be funding weird things... ## In detail - what it is and what you should know Before we can reward anything, you need to verify your identity through our compliance partner **Sumsub**. This is a standard KYC (for individuals) or KYB (for companies) process. It keeps everything clean on both ends - including yours - and helps us comply with international regulations. We’ve kept it simple, and it usually takes less than 5 minutes if you have the right docs ready. ### If You’re an Individual (KYC) You’ll be asked to provide: * A valid ID (passport, national ID card, driver’s license, or residence permit) * A proof of address dated within the last 3 months * A selfie * A short questionnaire asking if you're a US Person (citizen or resident) **ID Requirements:** * Must be a live photo of the original document (not a scan or screenshot) * If your ID has two sides, you must upload both * Image must be in color, fully visible, and unedited **Proof of Address Requirements:** * Must clearly show your full name and address * Dated within the last 3 months * Accepted formats: utility bills, bank/credit card statements, or official government documents * Must be a photo or scan, under 50Mb * If double-sided, upload both sides **Important****:** * Screenshots, mobile phone bills, medical bills, receipts, or insurance statements will be rejected. * If you’re a student living at your parents' home - we accept the following document as POA (Proof of Address): * A certificate of accommodation dated less than 3 months and signed by one of the parent *(model below)*. * A copy of the CNI (ID Proof) of the signatory (parent) * A POA at the name of the signatory (parent) with their name and address on it dated less than 3 months. It can either be a bank statement or a bill. Model as an example: *I, \[Name Surname], born on \[date of birth] at \[place of birth], residing at \[your full address] hereby certify on my honor to host at my home, free of charge \[Madam, Mr] \[First Name Last Name], born on \[date of birth] at \[place of birth] of nationality \[country of birth].* *Done at \[place of declaration] on \[date]* *Signature* ***Also super important to note:*** * *Minimum age to pass KYC is 16* * *We do not accept applicants from: Cuba, Syria, Iran, North Korea* ### If You’re a Company (KYB) If you’d rather use a company to receive your payments (which we recommend if you do have one), here’s what you’ll need: * A Certificate of Incorporation (dated less than 12 months) * A Shareholder registry or official document that lists your directors and UBOs (anyone owning more than 25% of the company) * This can be a recent cap table signed by an authorized person of the company (don’t forget to date it also) or signed official doc * You may also need to submit additional documents based on your country Country-specific notes: * US: Your EIN is required * Australia: You’ll need your ACN/ARBN, business address and legal address * Germany, Ireland, Malta, etc.: Expect to provide details about directors, business activity, and legal rep #### Final, final tip We know it’s not the most fun part of the journey, but doing this properly means: * You get paid safely * You avoid issues with your local tax office * And you don’t have to come back later to fix stuff # OnlyDust Fellowship - admin ### What to Expect Yes, we know - admin stuff isn't what you came here for. But we’ve kept it simple, clean, and (almost) painless. You'll be receiving each step by email. Here’s how it works: #### Step 1: Fill out the onboarding form By email, we’ll ask for: * Your personal or company info (so we can invoice properly). *If you’ve got a company, use your company details. It’ll make invoicing smoother - and let’s be honest, your local tax office will give you way less trouble later on.* * The wallet where you want to receive your rewards (make sure to follow the rules that we send you by email along with your Tally form to complete). #### Step 2: Verify your identity (KYC/KYB) Once step 1 is completed, you'll receive a link to do a quick identity check with our partner Sumsub. It takes 3–5 minutes and helps us stay compliant on both sides. * If you’re an individual → upload your ID, a selfie, and proof of address * If you’ve got a company → add your business registration + UBO info Please refer to our [section KYC / KYB](https://app.gitbook.com/o/MQQDjhOXRySQPsao0aZ0/s/FetEvDuVEZkpYJ6kurbf/~/changes/7/admin-stuff/kyc-kyb-id-verification) for more info. #### Step 3: Sign your Fellowship contract Identity verified, you’ll get a Pandadoc to sign via email. This makes it official. No contract = no rewards. Period. #### Step 4: We issue the invoice for you No need to create your own - we generate the invoice or receipt on your behalf. *You’ll get a copy by email for your records.* #### Step 5: Payment time Once the invoice is ready and your contributions are approved, we process your payment to the wallet you gave us. It may take up to 7 business days to land. You’ll get a final email with the transaction hash once it’s done. If you ever get stuck or don’t receive something, just email us at [**admin@onlydust.xyz**](mailto:admin@onlydust.xyz) . # Wallets This part is for contributors and maintainers that are eligible to grants. ### How to set up your wallet properly (and not lose :moneybag:) You’re about to receive a Fellowship grant or a project reward through OnlyDust. That means you’ll get either crypto payments (USDC or native tokens) if you're contributing to a blockchain ecosystem, or fiat payments (USD/EUR) via PayPal if you're contributing to traditional open source projects (non-blockchain). Each ecosystem comes with its own network, rules, and currency. So please — read this carefully. Mistakes here can get expensive. #### Step 1 – Check your ecosystem + currency Your payment method is determined by OnlyDust based on the ecosystem you’re contributing to - you don’t need to make that decision. In the onboarding form (Tally), you’ll be asked to provide either a crypto wallet address or a PayPal email, depending on your assigned payment method. We’ll clearly indicate whether you’ll be paid in crypto or fiat (USD/EUR) — no need to guess, but you won’t be able to choose. Here’s the breakdown by ecosystem: **If you're contributing to a traditional OSS project (non-blockchain):** * You’ll get paid via PayPal * By default, payments will be made in USD * If you’re a resident of the European Union, you can choose to be paid in EUR * Your PayPal account must be valid and verified * Make sure the email address or the phone you give us is linked to your account If your PayPal account is in a different currency than the one you're paid in (USD or EUR), PayPal will convert the funds, and you may incur FX fees on your side. **If you're in the Starknet ecosystem:** * Payments are made in USDC * Network: Starknet * Wallets we recommend you to use: Braavos or Ready (former ArgentX) * Your wallet must: * Be non-custodial (no exchanges because it might result in loss of funds- it happens a lot with exchange when it comes to USDC) * Be activated (you must have received at least 1 STRK once) **If you're in the Stellar ecosystem:** * Payments are made in USDC * Network: Stellar * Wallets we recommend you to use: LOBSTR or any non-custodial Stellar wallet * Your wallet must: * Be activated (i.e. received at least 1 XLM in the past) * Have the USDC asset added manually (refer to your wallet’s FAQ) * Not be an exchange wallet — those often have internal routing and will reject or lose USDC **If you're in the Flare ecosystem:** * Payments are made in native FLR tokens * Network: Flare * Wallets we recommend you to use: Use a EVM compatible wallet such as metamask or Rabby on the Flare Network. Please refer to FLR recommandations here * Same rules apply: no exchange wallets, and make sure the wallet is ready to receive FLR #### Step 2 – Provide your wallet or PayPal address (correctly) In the onboarding form, you’ll be asked to share either your wallet address or your PayPal email, depending on your ecosystem (we choose for you, don’t worry). You have two options: 1. Crypto contributors: use WalletConnect (if supported) or paste your wallet address 2. Traditional OSS contributors: provide your PayPal email or telephone *Important: double-check what you submit. If you enter a wrong wallet or email and the funds go missing, we can’t recover them.* If you made a mistake, email us ASAP at before payment is triggered. #### Final tips * Crypto to exchange wallets = risky → they often reject ecosystem-native USDC * Use a wallet you control and check regularly * You can update your info (wallet or PayPal email) at any time before the next payment wave by emailing us That's it. Proper setup = smooth payments, no headaches. # The impossible Bench Here are the articles in this section: * [What is it](https://docs.onlydust.com/~/revisions/hDyFLjt7yK9TBrWfEAXo/the-impossible-bench/what-is-it) * [What's in it for you](https://docs.onlydust.com/~/revisions/hDyFLjt7yK9TBrWfEAXo/the-impossible-bench/whats-in-it-for-you) * [Who should apply](https://docs.onlydust.com/~/revisions/hDyFLjt7yK9TBrWfEAXo/the-impossible-bench/who-should-apply) * [Selection Process](https://docs.onlydust.com/~/revisions/hDyFLjt7yK9TBrWfEAXo/the-impossible-bench/selection-process) * [Admin stuff](https://docs.onlydust.com/~/revisions/hDyFLjt7yK9TBrWfEAXo/the-impossible-bench/admin-stuff) * [FAQ](https://docs.onlydust.com/~/revisions/3DpCaZPxwpxhfZH7z0cV/the-impossible-bench/faq) # What is it Some claim that fully autonomous SWE is around the corner, that devs will be useless in a few months. **“We just killed software engineering.”** Their sales pitch? Saturated benchmarks.\ But these evaluations don’t represent the work we do every day as great engineers on a complex codebase. Coding is not just vibecoding. It’s a great narrative to push when you are a coding agent raising money, but it’s simply not true. **The best engineers in the world can perform tasks that are very far beyond the actual capabilities of LLMs.** And to prove it, we need to set up a fair game.\ Code that has never been seen by LLMs.\ Well-scoped and feasible tasks. We will grant 100 incredible engineers working on 100 closed-source hardcore projects.\ From this work, we will create the ultimate benchmark. A coding benchmark, with a 0% success rate from LLMs. # What's in it for you Here’s what you get if selected for the Impossible Benchmark Program: * **Your work becomes the new frontier**: your contribution has a direct impact on improving the models & agents of the world's top AI labs (think, for example, OpenAI, Anthropic, DeepMind, Mistral, ...). * **Invitation to San Francisco** (for top contributors): Meet researchers from top AI labs, share your workflow, and shape how AI learns to code like elite engineers, not just autocomplete. * **$30,000/year grant** (paid quarterly, $7,500 per installment), renewable for up to 2 years, no equity taken, no strings attached beyond the program terms. It’s a grant, pure and simple, to empower you to keep building on YOUR project. * **Full ownership of your code**: You retain all rights. We only ask for a time-bound, exclusive license to use your closed-source project to build AI benchmarks. * **Zero pressure to “productize”**: This isn’t about building a business. It’s about advancing hard, real-world engineering. If your project solves a meaningful problem and confuses AI, that’s enough. * **A community of peers:** Join 100 of the world’s most technically rigorous builders, people who code in Rust, C++, Go, embedded systems, compilers, and other domains where correctness, context, and complexity matter more than syntax. # Who should apply This program isn’t for everyone, and that’s by design. \ \ Below are some key traits of ideal candidates: * **You already have a project started or a clear idea you want to launch;** this isn't about finding you a project; it's about funding the one you're already passionate about. * **AI agents struggle with your codebase**: when you try to use LLMs to assist, they hallucinate, produce broken logic, or require 10+ iterations to get anything usable. (If your features get built in “one-shot” with autocomplete, your project is likely too simple for this program.) * **You code primarily by hand**, using AI only for minor autocompletion, not as a co-pilot for core logic or architecture. The goal is human-original reasoning, not synthetic data. * **You’re committed to 10–15 hours per week** over the next 6–12 months to advance your project. Not as a freelancer-for-hire but as a passionate builder solving a problem you deeply care about. * **You retain full ownership of your code,** but are willing to grant a license so we can turn your work into rigorous, private benchmarks for top AI labs * **Your project is closed source (for now),** you can open source it later but it needs to stay private during the grant period * **You’re not in it just for the money**: the €30k/year grant (paid quarterly) is meant to *enable* your vision, not replace a salary. We fund builders, not contractors. {% hint style="info" %} If this sounds like you, or if you’re unsure but your code regularly makes AI “give up”, apply anyway. Many of our strongest candidates initially thought, *“My project isn’t hard enough.”* \ Spoiler: it probably is. Don't self-reject. {% endhint %} # Selection Process 1. Kickoff, with JB, Head of DevRel\ Check motivation, 6+ month scope, and 10 to 15 h/week. Review the contract. \ If fit, book the tech interview. 2. Before the tech interview\ Have at least 10 to 15 hours of code started. Send a short project brief, roadmap, and key challenges 24 hours ahead. Share GitHub access. 3. Technical interview, with Antho or Olivier (both senior back end engineers)\ Evaluate complexity, potential, and code quality. \ Written feedback and a go or no-go within 24 hours. 4. Admin validation\ If accepted, you get a confirmation email and the contract. 5. One-month review after contract signature\ Committee checks progress and quality. \ Decision based on delivery, effort, and rule compliance. 6. Payment and legal\ On approval, finance pays the first quarterly €7,500. # Admin stuff #### Contract We will sign together a license contract with the following principles: * You license your repo(s) to OnlyDust for AI use only (benchmarking, training, eval, improving models). The license is exclusive, worldwide, transferable, sublicensable, and irrevocable. * If your code stays private, you can still build and sell products with it, just not for AI benchmark or training purposes. * You can open-source your code after 12 months #### Pay * Total amount: 30,000€ per year, renewable once (2 years in total) * Pay: 7,500€ every quarter, submitted to a committee review (make sure the code has advanced enough during the past 3 months + the quality is still up to expectations) * 1st pay timing: * If you have already started a project with an extensive code base, we can review : 7,500€ at contract signature * If you've not started and want to use this to fund an idea : 7,500€ 1 month after contract signature, submitted for review (quantity and quality of the work in this 1 month) # FAQ The questions you might have - this is regularly updated. Contact us if you can't find your answer here. ### :question: Not sure I understand the program
Ok cool program, but I don't have 10 to 15 hours per week * It's an **average**, not a strict requirement * Some weeks you'll do 3 hours, others you'll binge an entire weekend * If you're in France between Christmas and New Year, we're not tracking your time * We care about **monthly progress**, not weekly time logs **What we actually measure:** * Is the project moving forward? * Are you delivering what you said you would at quarterly reviews? * Is the code quality maintaining standards?
Ok cool program, but I don't have a project or ideas Then this program isn't for you right now, and that's okay. Here's why we require existing projects or clear ideas: What we fund: Builders who are already scratching their own itch, solving problems they're obsessed with, and would code this regardless of money. What we don't fund: Developers looking for project ideas or trying to come up with something "hard for AI" just to get funding. Why this matters: * Projects without intrinsic motivation rarely survive 6+ months * The best code comes from solving real problems you deeply understand * Labs can tell the difference between genuine complexity and artificial difficulty What you can do instead: 1. Build your confidence through open source — Contribute to existing projects, get comfortable with complex codebases (we even have a discovery platform for this) 2. Wait until you have an itch to scratch — The best projects come from frustration with existing solutions 3. Start small on your own — Code something for 20-30 hours first, see if it excites you, then apply
I would make more money freelancing, the pay is not high enough You're right. If this were a freelance contract, the rate would be low. \ But here's the key difference: **this is a grant to fund a project you'd build anyway, not payment for contract work. This is NOT A PAY, it's a grant.** \ \ Think of it this way: * If you're already spending evenings/weekends on a side project you're passionate about, this grant gives you €30k to keep doing exactly that * It's not about replacing your income, it's about funding your ambition * The real value compounds: you keep all IP rights for commercial use, get visibility with top AI labs (OpenAI, Anthropic, DeepMind), and potentially get flown to SF to meet researchers If your goal is to maximize hourly rate, freelancing is definitely better. But if you're building something you believe in and want funding without investor dilution or client management, this is designed for that.
I want a full-time job, not a grant This isn't employment - it's funding for independent builders. **What this is:** * A grant to fund YOUR project while you maintain autonomy * You work when you want, how you want, with quarterly check-ins * You keep all commercial rights to build a business if you want **What this isn't:** * A job interview in disguise * A probation period before full-time employment * A contractor relationship with daily management **If you want full-time employment:** * The SF trip for top performers might lead to intros with labs who ARE hiring * Your project could become a business you run full-time (many past grant recipients did this) * Working on this kind of initiative is a great signal for employers and definitely something you can flex about on your resume
Can I use AI extensively to code on my project? The problem with AI-heavy development for our use case: * If you iterate with Claude for 3.5 hours instead of coding for 5 hours, you're essentially having Claude write your code * That creates synthetic data, code written in AI patterns, by AI logic * When we create benchmarks from that code, we're testing AI on AI-generated patterns * The evaluation becomes circular and useless What we're actually looking for: * Code with YOUR mental models, YOUR architecture decisions, YOUR problem-solving patterns * Projects where AI agents currently fail because they haven't seen this thinking before * Genuine human expertise at the frontier, not AI-assisted approximations What IS allowed: * Autocompletion is fine (like GitHub Copilot's inline suggestions), you're still structuring the logic * Occasional use when you're truly stuck on something (ask us first if unsure) * 50/50 workflow: one day exploring with Claude, next day refactoring/rewriting by hand The self-assessment test: If you're thinking "without AI, I'd go 10x slower", your project isn't complex enough for current models. That's actually GOOD for normal development, but it's not what labs need for frontier benchmarks. Bottom line: We're paying you to write code that AI can't write yet. If AI is writing most of it, we're funding the wrong thing.
I work in a team / want to collaborate with others This is not an issue; many options are possible to make this work.\ Apply anyway, and we will discuss if you're selected.
### :scales: Legal questions
Can I do this alongside my full-time job? * **Generally, yes, you can** do that in addition to a full-time job as long as: * Your employment contract doesn't have a strict exclusivity clause preventing side projects * You're not working on something that directly competes with your employer * You're doing this on your own time (evenings/weekends) * **Many of our developers have full-time jobs;** this is specifically designed for people with day jobs who code on the side projects * Your employer typically can't prevent you from working on personal projects unless explicitly stated in your contract
Do I need to create a legal status for legal compliance and handle taxation? Usually, yes, but it depends on where you're currently living. We have experience with this kind of topic and can help.
The licensing terms bother me: indefinite exclusive license for AI use Let's break down what the license actually means, because we drafted it to be as developer-friendly as possible while meeting lab requirements: **What we CAN do (and labs can do):** * Use your code to create benchmarks and evaluations * Train models using your code (post-training, pre-training) * That's it. Literally just AI training and evaluation purposes. **What we CANNOT do:** * Launch a commercial product using your code * Compete with you if you productize your project * Sublicense it for non-AI purposes * Prevent you from using your own code **What YOU keep:** * Full commercial rights for non-AI use * You can build a SaaS, sell licenses, offer services, whatever you want * You own the code; we just have specific usage rights * If you want to start your own AI lab someday, we can discuss (that's the only restriction) **Why this structure?** * Labs need assurance that the benchmark won't be contaminated by open-sourcing too early * You need assurance that you're not signing away your business future * The contract is 1.5 pages in plain English, if a sentence confuses you, it's our fault, not legalese **Context matters:** This isn't a typical "company wants your IP" situation. We're not building products with your code. We're using it to measure where AI fails so it can improve. You get paid, keep your upside, and help advance the field.