Shipping to mainnet is where most hackathon projects stall. Deploy costs, audits, RPC, store fees and the last mile of polish all land at once, right when the team is out of runway.

This bounty exists to remove that wall for very best Brazilian Seeker builders. We will subsidize the mainnet deployment of selected Seeker projects so they go live (even with a smaller scope) instead of staying on devnet during the final and post stages of the Solana Mobile and Colosseum hackathons.

We'll also put a Seeker in the hands of each winning team so they can keep building and testing on the real device. From hackathon projects to real apps running natively on Solana.

To be eligible you must be applying to both:

1. The Solana Mobile hackathon, and

2. The Brazilian sidetrack of Colosseum's World Fair

The build is the same - this is extra support for getting it to mainnet, not a separate competition.

Who can apply

- Brazilian teams and solo builders. Any team member composition, as long as the team is based in Brazil or made up of Brazilians.

- You must have an active submission in the Solana Mobile hackathon and in the Brazilian sidetrack of Colosseum's World Fair.

- The project must be a Seeker / Solana Mobile app — Seed Vault, Mobile Wallet Adapter, dApp Store, or Seeker-native features in use.

- Preference is given to The/Garage attendees, but any Brazilian team can apply and will be judged on the same criteria.

What to submit

- Project name + one-liner of what the app does and for whom.

- Team details: names, city, Telegram or X handles, and roles.

- Links to both hackathon submissions (Solana Mobile hackathon + World Fair Brasil sidetrack). You can also send over print screens of your still not submitted, but complete application to @kauenet on X.

- Public repository. Include build instructions that actually work from a clean clone.

- APK or dApp Store listing link so judges can install and run it on a Seeker or Android device.

- Demo video, up to 5 minutes, showing the app running on devnet in an Android device (preferably Seeker - reach out to our team for demo devices) - not slides, not a mockup walkthrough!

- Mainnet-readiness notes (max 500 words): what is deployed and where (program IDs, cluster), any audits or security-focused analysis, how accounts and CPIs are validated, what tests exist (unit, integration, LiteSVM/Mollusk, devnet runs), known gaps, and what remains before mainnet.

- What the subsidy will cover: a short breakdown - program deploy and rent, size in KBs of deployment and expected SOL cost.

- Whether you attended The/Garage, and which sessions or dates.

How winners are selected

• Mainnet-readiness — security of the program and client, account and signer validation, error handling, UI polish, test coverage, no obvious footguns | 30%

• Overall project quality — does it work end to end, is the code legible, is the repo real | 25%

• Impact on Seeker and Solana users — does this give Seeker owners a reason to use the device, and does it bring real users onchain | 25%

• Innovation and potential — is this a genuinely new use of mobile + Solana, and can it keep growing after the hackathon | 20%

Tiebreakers: The/Garage attendance, and whether the app uses Seeker-specific capabilities rather than being a web app in a shell.

Hard requirements — submissions that miss these are not reviewed:

- The app runs. A build that doesn't install or crashes on launch is out.

- The repo is public and buildable. It's fine to open-source only part of your stack.

- Both hackathon submissions are live and verifiable.

- No init_if_needed, no unchecked arithmetic, no missing owner/signer checks in the program code. If you have a program, it gets read.

Prize

Of all four selected, each winning team receives:

- 400 USD to subsidize mainnet deployment

- 1 Seeker device

Payouts are made after the mainnet deployment is verified, or in two parts (half on selection, half on verified mainnet deploy) at the sponsor's discretion. Devices are delivered in person, at the Solana Mansion. We'll analyze shipping within Brazil in a per case basis. Availability can be delayed, but we expect to have all devices over the next couple of months.

Notes

- Deploy to devnet first, then mainnet. We want to see the devnet run in your submission.

- anchor build --verifiable before your mainnet deploy, and keep the program ID and verification output in your repo.

- One submission per team. Each person may be on one team only.