Fe Builders
Challenge.

The contest is open worldwide, to beginners and experienced developers alike. Members of the Argot Collective and contest judges are not eligible to participate.

Both are welcome. There is no team-size limit, and your team can change after registration. Each project needs one contact person reachable by email. Team membership, responsibilities, and any prize split are for the team to agree on internally.

Yes. You can submit multiple distinct projects and participate in multiple teams. Register each project separately. Do not submit multiple variants of the same work as separate entries.

No. Your initial idea is not binding and can change as you explore Fe. Register by November 17 at 23:59 UTC with a contact email we can reach. You can start building before registering, but registration is required to submit.

We use the contact details from your registration and submission only to run the contest: to confirm your entry, ask questions about your project, and arrange prize payment. We don’t use them for anything else.

All times are UTC. The build window opens on November 3, 2026 at 00:00. Registration closes on November 17 at 23:59, and final submissions close on November 24 at 23:59. Registration and preparatory experiments are welcome before the build window opens. The registration deadline is firm; exceptions apply only if a problem on our side prevents registration.

No. Fe supports both the EVM and native code, and purely native projects are welcome. Developer tools are one exciting direction; your project does not need a smart contract or any blockchain connection. The core technical contribution must be in Fe.

Yes, with a meaningful Fe contribution central to the project. Standard-library submissions do not need to be merged upstream before the deadline. Pure compiler contributions are outside this contest’s scope.

Yes. AI assistance is welcome and is not scored negatively. Disclose how you used it, test the result, and be prepared to explain your code. Every project needs one responsible human contact.

Yes, but only substantial work completed during November 3–24 is judged. Identify the starting point and explain what changed. New feature work after the final deadline is not eligible.

Report the bug in the Fe issue tracker, ideally with a minimal example, and email hello@fe-lang.org if it blocks your entry. We’ll work with you to find a solution.

Ask in the office-hours channel on Fe Zulip for help, ideas, and progress updates. If something blocks your entry, email hello@fe-lang.org.

Yes. A working prototype is enough if you can demonstrate the core contribution and clearly document what works, what is unfinished, and any limitations. Completeness is part of technical quality, but your project does not need to be production-ready.

No. Provide reproducible instructions so judges can build and try your project. An optional video or demo can help communicate your work and support your score in the Documentation & demo category.

No. Mainnet deployment provides no scoring advantage. A testnet deployment is sufficient where deployment helps demonstrate the project. Native projects do not need a blockchain deployment at all.

Yes. Use your personal submission link to submit again before November 24 at 23:59 UTC. The latest valid submission counts. Include the exact commit SHA you want judged.

A successful registration is confirmed by email with your project ID and private submission link. For submissions, an email confirms whether the automated checks passed or explains what needs correcting. The form’s receipt alone is not confirmation of acceptance. Technical eligibility is reviewed separately. If you don’t receive confirmation, check your spam folder or ask us on Zulip.

Judges review the submitted commit. We may contact you to clarify missing information or build instructions; please reply within 48 hours. Clarifications after the deadline are allowed only at our request and must not introduce new code changes. Without a reply, we assess the project using the information available.

A minor setup issue does not automatically disqualify your project; we may ask for clarification. Reproducibility and completeness affect technical quality, and the core contribution must be verifiable for the project to be eligible.

We aim to announce the winners on December 1, 2026 via the Fe blog and X, then notify the winners by email. If judging takes longer, we’ll announce the delay publicly. The jury’s decisions are final.

Yes. All three prizes will be awarded: $2,500 for first place, $1,500 for second, and $1,000 for third. The full $5,000 prize pool is funded by the Argot Collective.

Prizes are paid in USDC on Ethereum Mainnet. After the winners are announced, we’ll contact each winning project through its registered email to request and confirm one payout address. We aim to pay within one week once that address is confirmed. Teams are responsible for distributing the prize among their members. Winners are responsible for any taxes that apply to their prize.

Individual feedback is not guaranteed. We reserve the right to publicly showcase any submitted project, including entries that do not win a prize.