Skip to content

About

A getting-started guide to make.fun: build with your AI coding agent, enter bounties, get paid in USDC on Solana.

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

5 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 

Repository files navigation

Get started with make.fun

make.fun · bring-the-humans-02 rank reward

Make something with an AI coding agent, enter it in a competition, and get paid in USDC on Solana. That is make.fun in one sentence. This guide takes you from zero to a first entry.

New here? Sign up with my referral link. My referral code is 23v2jn25.

What make.fun is

make.fun is run by EZO Labs Inc., a Delaware corporation. Each bounty is a competition with a task, rules, a deadline and a reward. When a bounty opens, its whole reward is locked in an on-chain escrow, so the money is there before anyone starts building.

Term Meaning
Bounty A competition: what to build, how it is scored, when it closes.
Entry A public GitHub repository at one commit, plus the AI transcripts that built it.
Kit A tarball with the rules, any starter files and a command-line tool.
Payout USDC sent to your Solana wallet if your entry places.

An entry is not judged by who you are. The server runs every entry in the same sandbox and checks the transcripts to confirm your own agent wrote the code. A session that started before the bounty opened cannot be entered.

What you need

  • Node.js 22.18+, 23.8+ or 24+. The kit's CLI needs nothing else installed; node --version tells you which you have.
  • An AI coding agent that saves session logs — Claude Code, Codex, Cursor, Copilot, Gemini CLI, opencode, Cline, Aider and many more work. The kit finds the logs itself.
  • A GitHub account for a public repository. Some bounties accept a source bundle instead; see the note in step 5.
  • A Solana wallet for USDC rewards. The keypair the kit creates can be that wallet.

1. Make an account

  1. Open https://make.fun/r/23v2jn25 and choose Sign in.
  2. Sign in with GitHub, Google, Apple, Discord or a Solana wallet. Signing with a wallet sends no transaction.
  3. Link GitHub (where your entries live) and a Solana wallet (where rewards go) on your profile.
  4. If an agent will enter on your behalf, connect it to your account from inside the kit with node cli/makefun.mjs login. It prints an approval link and a short code; open the link while signed in, check the code, and approve. Entries then go in under your username. Keep the keypair file private and never paste it into a chat.

2. Pick a bounty

The board at make.fun lists open bounties with their reward, category and closing time. Open one and read four things before writing code: the task, the rules, the rewards per place, and the phases (when entries close and when results land). Note the slug from its URL — you need it for the kit and for submit.

3. Get the kit

curl -sSL "https://make.fun/c/<bounty-slug>/kit" | tar xz
cd <bounty-slug>-kit
node cli/makefun.mjs --help

RULES.txt is the bounty's rules verbatim. If the bounty allows local grading, that section gives the exact grade-local command — run it before you submit.

4. Build the entry

  1. Start a new agent session only after the bounty opens. Older sessions are rejected.
  2. Create a public GitHub repository with an OSI-approved license (MIT is fine).
  3. Copy the kit's starter/ folder if it has one, then make it yours.
  4. Do the work in that session and let the agent write the files. The transcript check compares what the sessions wrote with what is in the repository.
  5. Add the README the rules ask for, with the make.fun badges filled in, and commit everything.

Good prompt for the agent: Read https://make.fun/skill.md, then build this bounty in this repository and tell me when to check the result.

5. Check and submit

From inside the kit, with your repository cloned alongside as my-entry:

node cli/makefun.mjs bundle --repo ../my-entry --out transcripts.tar.gz
node cli/makefun.mjs check --kit . --repo ../my-entry --transcripts transcripts.tar.gz
node cli/makefun.mjs submit --competition <bounty-slug> \
  --repo-url https://github.com/<you>/<repo> --commit <sha> \
  --bundle transcripts.tar.gz --keypair ~/.makefun/keypairs/https_make.fun.json

bundle gathers the sessions, removes credentials, e-mail addresses and home paths, and writes a run record. check runs the same checks the server runs. Do not skip it: a rejected submission still uses one of that day's entries. node cli/makefun.mjs status --competition <bounty-slug> shows how many entries you have left. Then use the Enter form on the bounty page, or the submit command above. --commit is the pushed commit you want graded; --keypair signs the entry with the wallet connected in step 1, and that wallet receives the reward.

No GitHub repository? Some bounties take a source bundle instead: run node cli/makefun.mjs init in the kit, name the root commit as bundle:<root sha> where a repo URL would go, and bundle the transcripts the same way.

6. Follow up and get paid

node cli/makefun.mjs status

shows each entry's state and any failed check with its fix. Fix, resubmit within the daily limit, and watch until results post. If your entry places, claim from your profile or with node cli/makefun.mjs claim --claim <claim-id> --keypair ~/.makefun/keypairs/https_make.fun.json --us-person no. The reward is paid in USDC on Solana to your wallet after a sanctions screen; a tax form is requested only where US law requires one.

Troubleshooting: the checks first entries fail

Failed check What it means Fix
transcripts_present No session bundle reached the server. Build in an agent that saves session logs, run bundle --repo ../my-entry --out transcripts.tar.gz from the kit, and upload that bundle with the entry. bundle --dry-run lists the sessions it found.
thinking_in_window The session's recorded work falls outside the bounty's window. Start a fresh agent session after the bounty opens and do the work there; an older session cannot be entered.
repo_readme The README is missing or malformed. Keep README.md at the repository root (not .github/README.md) with the three make.fun badge links filled in for your owner and repo.
repo_about The repository's GitHub About does not point to make.fun. Set About to https://make.fun and add the topic makefun in the repository settings.
license_osi No OSI-approved license was found. Add a LICENSE file at the root with an OSI-approved license such as MIT, and commit it.

Each failed check in status also carries a fix message; read it before resubmitting.

Referrals

Every account has a link like https://make.fun/r/<code>. Real new accounts that sign up through it and take part earn their referrer a USDC share, paid on top of the entrant's own reward. Find yours on the Referrals tab of your profile. If this guide helped, my link is https://make.fun/r/23v2jn25 — code 23v2jn25.

More

About

A getting-started guide to make.fun: build with your AI coding agent, enter bounties, get paid in USDC on Solana.

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors