Skip to content
LogoLogo

Mosh raises

A Mosh raise is a different way to launch: supporters fund the token before it starts trading. Mosh launches run on the Mosh protocol (generation 3) by Pons. Makina creates them through its own contract, the Makina Mosh pad, which receives the launch's team side and shares it with the builder and the launcher.

How a Mosh raise works

Loading diagram...
  1. Create. The creator sets the token details, a raise target and the timing, and signs one transaction through the Makina pad.
  2. Raise. Supporters deposit ETH while the raise is open.
  3. Fire. Once the target is met and the optional not-before time has passed, the creator fires the launch through the pad. This starts the token on Mosh.
  4. Live. The token trades on Mosh's curve and then its pools. After the curve graduates, the launch is finalized, which installs the planned liquidity ladder.
  5. Expire and refund. If the raise is still short of its target after its deadline, it can be expired, and every depositor can take their ETH back.

Raise settings

SettingAllowed range
Raise targetset by the live Mosh factory; on testnet 0.002–0.2 ETH
Raise duration30 minutes to 3 days
Launch window1 hour to 3 days
Not-before timeoptional; must be in the future and at least 1 hour before the launch window ends
Team share5% to 50%
Holder pool share0% to 99%, paid to Mosh's holder pool
Grant from token supply0, or 1% to 3%

The app reads the live factory limits before you sign. Presales, funding books, extra team payees and whitelist managers are not available through Makina.

Where the team side goes

The Makina pad is the single team recipient of every Mosh launch it creates. Mosh pays it the team side of the launch:

  • fees, in the pair asset, and
  • tokens: the team's part of the launch and the optional grant.

Anyone can trigger a harvest. The pad splits everything it harvests between platform, builder and launcher in the ratio 45 : 25 : 10, and each recipient withdraws their own share. The builder share waits as pending until a builder is set for that launch, through exactly the same 3-day verifier process as normal launches.

The pad has no owner, no upgrade and no arbitrary call. It refuses any launch setting that would send the team side somewhere else: extra team payees, a curator other than the Makina platform, or a whitelist manager.

Contracts

NameAddressRole
Makina Mosh pad
MakinaMoshPad
0x771ad895e381EeC74a9Dc01F890F7932E005C7e4Creates Mosh launches for Makina and splits the team side.
Mosh native factory
Pons gen 3 factory
0x6a8E245036333C7795abe8Be7CBe1b26facCC0A1ETH-paired Mosh launches.
Mosh registry
Pons registry
0x09D57937196418B9c1b3a773cA7F212C598d4478Mosh launch registry.
Holder pool
Pons holder pool
0x40c1992d23f29d0a31A407512175C12c8C4b4f68Receives the holder share of Mosh launches.