Build what happens after the swap.
A focused buildathon for builders creating useful products with DFlow on Solana. The goal is not another swap screen—it is the game, agent, consumer app, payment flow, or product experience that becomes possible after the swap.
Apply now · View the live site
| Build window | Aug 21–31, 2026 |
| Submission deadline | Aug 31, 2026 · 23:59 ICT |
| Demo Day | Sep 3, 2026 · Bangkok |
| Prize pool | 1,000 USDC |
| Team size | 1–4 builders |
Use DFlow to create a useful product experience that begins where the swap ends.
We are looking for:
- A clear user problem and a product people could genuinely use.
- A meaningful DFlow integration—not a reskinned swap interface.
- Creative thinking, clarity, usefulness, and evidence that you shipped.
- A working demo, product write-up, and public demo link or code repository.
Projects already released to users are not eligible. New products and new ideas are the point.
DFlow is a DEX aggregator API that routes swaps across Solana venues and re-optimizes routes at execution through JIT Routing.
For the buildathon:
- Start with What is DFlow?.
- Use
devquote.api.DFlow.net. - The development endpoint is free, limited to 1 TPS, and requires no API key.
- Builders can add
platformFeeBpsand retain 100% of the platform fee. - Gas fees can be sponsored to create a smoother product experience.
Core integration flow:
- Call the
orderendpoint with the input mint, output mint, amount, and user public key. - Receive a ready-to-sign transaction.
- Ask the user to sign.
- Submit the signed transaction through a Solana RPC.
Understand DFlow, JIT Routing, the quote-to-swap flow, monetization, and gas-sponsored UX.
- Workshop page
- The recap is available inside Build Hub → Workshops on the site.
Learn how a mobile game economy can turn in-game currency into SOL and become a starting point for your own product.
The full Rules, Q&A, Workshops, recap, and Docs are available on the /rules/ page.
Requirements: Node.js 20 or newer and npm.
npm ci
npm run devOpen http://localhost:3000.
Create a production build with:
npm run buildThe site is exported as static files into out/.
- Push this folder to the root of a GitHub repository.
- Import the repository into Vercel.
- Keep Framework Preset set to Next.js.
- Leave the build and output settings on their defaults.
- Deploy.
No Vinext, Vite, Cloudflare, Wrangler, database, or custom install configuration is required.
- Push the project to the
mainbranch. - Open Settings → Pages in the GitHub repository.
- Set Source to GitHub Actions.
- Wait for the included Deploy to GitHub Pages workflow to complete.
The workflow handles repository base paths automatically and deploys both / and /rules/.
| File | Controls |
|---|---|
app/page.tsx |
Landing-page text, dates, prize, buttons, brands, and social links |
app/rules/RulesClient.tsx |
Rules, Q&A, workshops, recap, Docs tab, and Build Hub footer |
app/Countdown.tsx |
Submission deadline and countdown copy |
app/globals.css |
Colors, typography, motion, footer sizing, layout, and responsive styles |
app/layout.tsx |
Browser title, description, favicon, and social-sharing metadata |
public/ |
DFlow logo, Superteam Thailand logo, favicon, and social preview image |
app/
├── Countdown.tsx
├── globals.css
├── layout.tsx
├── page.tsx
├── site-path.ts
└── rules/
├── page.tsx
└── RulesClient.tsx
public/
├── dflow-mark.png
├── superteam-thailand.png
├── favicon.svg
└── og.png
.github/workflows/deploy-pages.yml
next.config.ts
package.json
- Next.js
- React
- TypeScript
- CSS animations and responsive layouts
- Static export for Vercel and GitHub Pages
Built by Superteam Thailand with DFlow for builders who are ready to ship.