25 seats available
This cohort is limited to 25 participants so we can stay hands-on during the build weekend. If you are not accepted this round, you will still have the chance to apply for upcoming hackathons.
STON.fi Vibe Coding Hackathon
begins june 4th, 2026
No coding experience required. Develop the skills to use AI coding agents to build with STON.fi on TON. Set up your tools, build your app, ship it live, and submit your weekend build for rewards.
Qualification
We are selecting a focused group of builders who are ready to learn, commit real time, and submit a working TON product by the end of the hackathon.
This cohort is limited to 25 participants so we can stay hands-on during the build weekend. If you are not accepted this round, you will still have the chance to apply for upcoming hackathons.
We are looking for people who are genuinely ready to invest the time needed to build, finish, and submit a product, not just browse the materials.
Everyone who fills out the application is reviewed for acceptance. We use the application to understand your motivation and whether you are ready to participate fully.
You do not need to be a programmer to join. We are also open to new builders who want to learn vibe coding on TON and use AI tools to create their first product.
Rewards
Track rewards require a real integration, and every valid submission can still reach the participation pool.
To qualify, use Omniston crosschain SDK - our v1beta8 release in your submitted product.
To qualify, integrate & utilize Mira in your TON product.
Distributed equally to all participants who follow the submission criteria.
Projects must be new. Established products built before the hackathon are not eligible for rewards.
Agenda
The hackathon runs across five days with workshops, office hours, weekend support, and a Monday morning submission deadline. Workshops are recorded as well, so participants in different time zones can catch up.
The program begins on Thursday with the opening session and a dedicated STON.fi workshop to get everyone aligned on the stack.
Friday continues with the Mira AI workshop so participants can explore the second integration track.
Participants can book a call with an expert throughout the day on Friday to unblock setup, product ideas, and technical questions early.
Participants spend the weekend building online with continued support, so they can keep moving even after the live sessions end.
Everyone should arrive at the weekend prepared with tools, accounts, and setup complete, then submit their finished project by 9:00 AM CET on Monday.
Participants can present their project on Monday, but presenting is not mandatory. Winners are judged based on their submission, not on the demo day presentation itself.
Setup
Set up your environment, connect an AI agent, and bring in the TON tools you need for a working MVP.
FAQ
Answers to the most common questions about who the hackathon is for, how submissions work, and what to expect.
The STON.fi Vibe Coding Hackathon is a build-focused program for founders, developers, designers, and operators creating new products, tools, and experiences around the STON.fi ecosystem.
It is designed for ambitious individual builders and small teams who can turn a strong idea into a credible product. Technical depth matters, but clarity of execution matters just as much.
Yes, you can continue exploring a market or problem space you already know, but the submitted product itself should be new. The key requirement is that the project under consideration for prizes is new work.
Yes. One registered participant can act as the primary point of contact while collaborating with a small team on a single coordinated submission.
Projects will be judged based on the submission itself, not on demo day attendance. Demo day is not mandatory if the timing does not work for your schedule, and the winners will already be decided just before demo day begins.
Each submission should include:
No. All sessions will be recorded, so if you miss one, you can watch it later and stay up to speed.
The strongest projects solve a real user problem, show clear utility, and demonstrate thoughtful execution. Relevance to the STON.fi ecosystem and the quality of the product experience both matter.
Not necessarily. What matters most is meaningful progress, a clear concept, and enough working proof to communicate what you built and why it matters.