JUSTYPE
Profile
Start here

Getting started

Create and review a token specification while keeping Classic and programmable execution states explicit.

Documentation index

Before you begin

You need a token name and ticker. Classic V1 fixes supply at 1,000,000,000 tokens, decimals at 18, and the pair at ETH. Behavioral rules are optional, but any you add remain a visual profile: the Classic pool is hookless and does not enforce them.

A real launch requires a connected wallet on Robinhood Chain and an enabled production launch flag. Drafts remain in this browser; JUSTYPE has no account or server copy from which to restore them.

Describe → Token → Market → Review → Launch → Live market

  1. 01
    Describe

    Write supported market behavior in ordinary language, or leave the Classic token without a rule profile.

  2. 02
    Token

    Set name, ticker, description, website, and optional image URL. Supply and decimals are fixed by Instant Launch.

  3. 03
    Market

    Choose ETH for Classic V1 and optionally choose the canonical creator LP-revenue variant. USDG and stock pairs are design-only.

  4. 04
    Review

    Inspect token, market, liquidity custody, non-enforced rules, canonical launcher, strategy, and predicted token address.

  5. 05
    Launch

    When activated, approve one canonical LiquidityLauncher transaction. Before signing, JUSTYPE predicts, checks, estimates, and simulates it.

  6. 06
    Live market

    Only a verified receipt unlocks the address route. Real PoolManager swaps create the first chart candle and trade rows.

Write an instruction the parser can inspect

Prefer short declarative sentences with explicit numbers, sides, destinations, and time units. “Take 2% on sells. Send half of sell fees to stakers.” is easier to inspect than a paragraph full of pronouns.

Take 2% on sells.
Use half of sell fees to buy back MOG.
Send the rest to stakers.

Accepted examples describe known patterns; they are not an exhaustive grammar. Review every normalized rule even when the instruction was recognized.

Know what the review proves

Rule review proves that the frontend can represent the configuration and found none of its implemented blocking issues. Classic preflight separately proves that the current canonical transaction can be predicted and simulated for the connected wallet at that moment. Neither proves economic quality, future programmable deployability, or safety.

Use Normalization and validation to see the exact checks, then use Behavior Score to inspect the visual representation.