Welcome

Home
How it works
Why Crowrise
The $CROW token
For Developers
LIVE Projects

For Creators

Create Project
My projects
Project Explorer
My allocations

The $CROW token

$CROW is Crowrise’s native token. When a listing goes live through Crowrise’s pump.fun-style launch with the $CROW leg enabled, part of the same deployable SOL buys $CROW and burns it. More launches → more buy pressure on $CROW → less circulating supply—without asking backers to do anything extra. Project token vesting for new listings runs in Streamflow; the 90/10 split here is about launch SOL, not how you claim project tokens afterward.

$CROW token 7VurkVCGyXUkcWiNLGhZHz8C5Cbby3swnRKMUKripump
Solscan DexScreener Streamflow lock

On-chain stats (launch burn program)

The tiles below summarize how much $CROW has been bought and burned through Crowrise launches, an approximate USD figure, and a live market snapshot (price, market cap, liquidity). Figures refresh automatically when data is available.

$CROW bought (all launches) — Waiting for data
$CROW burned (all launches) — Usually matches bought when burns are atomic
Implied value (USD) — Rough estimate from recorded prices
Price —
Market cap —
Liquidity —

How the launch bundle splits SOL

When the auto-launch countdown ends and funding rules pass, Crowrise runs go-live from the project funding wallet—a coordinated pump.fun-style launch (create + dev buy on the new curve, then the $CROW leg when enabled). The deployable SOL is divided between the new project’s curve and $CROW. Streamflow listings still use this launch bundle; afterward, project tokens vest via Streamflow instead of Crowrise’s disperser wallet.

  1. Funding wallet balance

    Let B be the SOL (lamports) Crowrise deploys at launch after any fee reserve. The whole raise still shows as verified contributions; this step is how that balance is spent on-chain.

  2. Coordinated go-live sequence

    Project and $CROW legs run in one tight sequence so backers experience a single go-live—not a separate manual step from the creator.

  3. After the bundle

    For Streamflow projects, allocations are vested on-chain in Streamflow. For legacy disperser listings, tokens route to the disperser for in-app claims. The $CROW leg is gone from circulation—bought with real launch volume, not a separate treasury gimmick.

In plain terms

  • You back a project by sending SOL to its published funding wallet (after Streamflow prepay is verified for new listings). Your share of the pool is your verified SOL ÷ total verified raise.
  • At launch, Crowrise doesn’t send 100% of deployable balance into only the new token. 90% buys the project; 10% buys $CROW and burns it when that leg runs.
  • Why that helps everyone: project launches stay the main event, but every launch also reinforces Crowrise’s own token with real SOL and a smaller float over time.

Formulas (lamports / SOL)

Exact basis can reserve fees first; the intended split of deployable launch SOL is 90% / 10%. Frontend helpers live in js/crow-mechanics-math.js for parity with the edge worker once wired.

  • Deployable balance B = lamports from the funding wallet used in the launch bundle (after any fixed reserves).
  • Project buy leg: P = floor(B × 9000 / 10000)
  • $CROW buy + burn leg: C = B − P (or explicit 10% floor; remainder to project—implementation should keep P + C = B).
  • Backer share of funded SOL (unchanged): si / S where si is your verified lamports and S is total verified lamports. Project tokens received scale with the 90% leg and curve math, not as if 100% of B bought only the project token.

Example: if B = 10 SOL, then P ≈ 9 SOL to the project token and C ≈ 1 SOL to buy and burn $CROW (subject to fees and rounding).

Where to read more

Mechanics tie into the same launch path described in How it works — After you publish and the bigger picture on Why Crowrise.