The problem

The standard launchpad has one bonding curve and one exit: fill the curve, graduate, move liquidity to a DEX, and the launchpad has nothing more to do with the token. Once it graduates, nothing holds the market together. Snipers take the cheap entry, graduation turns into a place to sell, and the launchpad has already moved on to the next token.

CurveX is about the mechanism, not the launchpad. You're not building a full launchpad product. You're designing and building the bonding curve mechanism a launchpad could run on: several market phases, where each phase changes how the token trades, and where the mechanism keeps working after the token reaches the DEX.

An example model (not required)

This is one way to do it, and it's only there to get you thinking. You can design your mechanism however you want: different phases, a different number of phases, different names, phases that loop or branch, or something that looks nothing like this. The only requirements are more than one market phase and a connection to a real DEX at some point.

Phase	Name	What it's for	Example parameters
1	Discovery	Cheap, fair entry	Low price, small liquidity, strict per-wallet buy caps, anti-sniper delay
2	Momentum	Grow the market	Steeper or re-shaped curve, higher trade limits, deeper reserves
3	Community	Reward holders who stay	Holders unlock mechanics: fee-share, staking, voting on parameters, buybacks, quests
4	Open Market	Full DEX trading	Liquidity moves to a Solana DEX pool, and the mechanism keeps a role

---

The rules, in phases

The rules follow the four phases of the example model.

Phase 1: Discovery (what to build)

Design and build a multi-phase bonding curve mechanism on Solana. You don't need to build a full launchpad around it. Your submission must include:

1. An onchain program (Anchor or native Rust) that handles buys and sells across your phases, each with its own rules. The rules could be a different curve shape, per-wallet limits, fees, liquidity depth or which actions are allowed.
2. Onchain phase transitions. Each phase has to be triggered by something the chain can see: market cap, reserve size, number of holders, time spent in the phase, volume, a holder vote, or a combination. Transitions can't depend on an admin pressing a button.
3. A life after graduation. Once the token reaches the DEX, your mechanism still has a job. It could route fees to holders, manage the LP position, run buybacks, unlock rewards or carry holder governance forward. Designs that stop at graduation don't qualify.
4. A simple frontend or CLI (it doesn't need to be a full launchpad) that shows the current phase, the progress toward the next one, and what changes when it arrives.

Design questions worth answering well:

• How does your first phase stay fair when bots can create hundreds of wallets?
• What stops a big sell-off at every phase change?
• What do long-term holders actually get that a trader who just bought in doesn't?
• Who controls the liquidity once the token reaches the DEX, and can anyone pull it out?

Phase 2: Momentum (building and eligibility)

• You have 5 days. Submissions close exactly 5 days after the hackathon opens, and late entries aren't accepted.
• Solo builders and teams of up to 4.
• Any AI agent, framework or language is fine. Building with Claude, Cursor or other agents is encouraged.
• Anything started before the hackathon opened must be clearly marked, along with a description of the new work.
• Deploy on devnet. Don't launch a real-money token as part of your submission.

Phase 3: Community (submission and judging)

Submit

• A public GitHub repo with a README that includes:
  • a phase table like the one above, giving each phase's curve formula, limits, fees and exact transition trigger;
  • an explanation of what the program does after graduation;
  • how to build, test and deploy it.
• A write-up on the design and impact of your curve (roughly 500–1,000 words, in the README or linked). It should cover:
  • Design: why you chose these phases, curve shapes and triggers, and the trade-offs you made;
  • Impact: what your mechanism changes for creators, early buyers and long-term holders compared with the standard curve → graduate → DEX model;
  • Failure modes: how your design handles snipers, bots, sell-offs at each phase change and low-activity tokens that stall in one phase;
  • After graduation: why your mechanism's ongoing role is good for the token and its holders.
• Tests or a simulation that show the curve behaves correctly: prices at each boundary, limits enforced, and no way to skip a phase.
• A demo video (YouTube, Loom, Vimeo or X) of 3 minutes or less that walks through the phases as they happen.
• No private keys, seed phrases or API keys in the repo. Use environment variables and include a .env.example file.
• One submission per person; you can update it until the 5-day deadline.

Vote

• Voting opens the moment submissions close and runs for 24 hours.
• Token holders vote, weighted by how much they hold at the snapshot (and still hold when they vote).
• The submission with the most vote weight wins. Ties go to the earlier submission.

Phase 4: Open Market (the prize)

The winner doesn't stop earning when voting closes.

• The winner receives the entire prize pool (sponsorship + 90% of creator fees earned so far).
• Every future fee claim is forwarded to the winner's payout address, forever.

---

Circuit breakers (disqualification)

Plagiarised work, non-functional demos or malicious code are removed from voting. So are:

• admin backdoors, such as hidden mint authority, withdrawable LP or upgrade keys that can drain funds without anyone being told;
• phase changes that need a person to trigger them;
• designs that end at graduation;
• any launch or promotion of a real-money token as part of the submission;
• any repo that exposes private keys, seed phrases or live API keys.

Resources

• Solana docs
• Core concepts
• RPC overview and cluster endpoints
• RPC HTTP methods
• RPC WebSocket methods
• Developer tools
• Anchor framework
• Devnet faucet
• For your AI agent: llms.txt · SKILL.md · Solana agent skills