The asset, metadata and authority configuration.
PRODUCT / TOKEN LAUNCHER
Launch Coin
Define a Solana token launch, bind a default intent policy and export one reviewable plan before any wallet is asked to sign.
LAUNCH WORKBENCH
One focused path: asset, market, policy, review.
A token launch has two different layers. The first creates the asset and its market: the name, symbol, metadata and launch venue. The second tells future trading interfaces what protection the issuer recommends when people trade that asset. Joltwork keeps those layers visible instead of hiding them behind one “launch” button.
The form below does not take custody of a creator’s wallet and it does not silently broadcast a transaction. It creates a deterministic JLM1 plan that can be reviewed, copied and downloaded. That plan becomes the input for a production launch adapter, where the wallet will see the exact Solana instructions before approving them.
SIGNING AUTHORITY
not connected
The creator wallet will be written into the compiled manifest.
COMPILED OUTPUT
Complete the launch manifest to derive its deterministic policy identity.
SIGNING BOUNDARY
Verify the public metadata JSON, compile the manifest, then use the separate mainnet action. Joltwork assembles Pump’s official create_v2 instruction, generates the new Mint signer in this browser and asks the connected wallet to review and pay for the transaction. Nothing is submitted without explicit approval. The default intent policy references the verified mainnet Jolt Guard Program ID 6HfEu…S3ENTY.
RPC AND PRIVACY
The default browser-compatible RPC is operated by PublicNode, not Joltwork or Solana. It receives ordinary RPC requests and the signed transaction when submitted. Production operators should replace it with their own trusted Solana RPC endpoint before launch.
WHAT GETS CREATED
One launch, three protocol artifacts.
An explicit Pump create_v2 route plan—no fictional Jolt-native exchange.
A discoverable baseline that wallets may strengthen per transaction.
The mint is the token itself. The market route is where the first liquidity and trading path are created. The default intent policy is not another tax or transfer restriction: it is a public baseline describing how supported wallets should protect a trade, such as requiring a maximum total cost or restricting execution to an approved route.
A trader is still free to choose stricter terms for an individual transaction. An issuer might publish a 2% maximum-cost baseline, while a trader can sign a 1% limit for one purchase. The user-level intent wins because it is the condition attached to that specific transaction.
LAUNCH PIPELINE
A reviewable path from metadata to market.
Each stage produces explicit data so a creator can review authorities, route configuration and policy before signing.
Imagine a creator launching a token through Pump with SOL as the quote asset. JLM1 records the token metadata, selected launch route and default policy as one inspectable document. The adapter then turns the asset and market portions into launch instructions, while Joltwork keeps the policy identity available for wallets and later trades. If any field changes, the compiled identity changes too, so an old review cannot be reused for a different launch.
Define metadata
Name, symbol and URI are normalized into the JLM1 launch manifest.
Select rules
Choose a baseline cost, route or fee constraint for supported interfaces.
Assemble
Prepare the selected Pump market route and the ordered accounts an adapter must assemble.
Review & sign
The connected creator approves the final transaction from their own wallet.
PRE-FLIGHT
Launch readiness checklist.
The checklist is deliberately split between facts the software can validate and decisions only the creator can make. A URI can be checked for format, but software cannot decide whether an authority should remain mutable or whether published social links are trustworthy. A commercial launch flow must make both categories explicit before asking for a signature.
Required inputs
- Metadata URI resolves to valid token metadata.
- Name and symbol fit the selected launch route limits.
- Creator wallet has sufficient SOL for rent and fees.
- Quote asset and initial market route are confirmed.
Creator decisions
- Whether mint and metadata authorities remain mutable.
- Which default policy wallets should display.
- Whether metadata and mint authorities remain or are revoked.
- Which treasury and social links are published.
VERIFIABLE DEPENDENCIES
The launch path is tied to Pump’s published interface.
Users can review the exact program, route and instruction name inside the compiled launch plan before approving a mainnet transaction.
Joltwork uses Pump’s published create_v2 interface and checks that the assembled instruction targets 6EF8r…F6P, the Pump program address used on mainnet and devnet. The new Token-2022 Mint keypair is generated only in the browser, partially signs the creation transaction, and is never transmitted as a reusable secret. The connected wallet remains the payer and final transaction signer.
The compiler exposes the instruction discriminator, ordered accounts, selected quote asset, metadata URI and target program before signing. This keeps the dependency review inside the product instead of sending creators to an external code-hosting account.
LAUNCH INSTRUCTIONcreate_v2 coin creation
account order / instruction dataTARGET PROGRAMPump program
6EF8r…F6PFAQ / LAUNCH
Before creating a coin.
Does a default policy prevent users from adding stricter limits?
No. The issuer policy is a baseline. A trader may bind tighter max-input, min-output, expiry or route constraints to an individual transaction.
Is the policy tied to one liquidity pool?
No. Joltwork’s intent policy is evaluated around the chosen transaction route, allowing it to move across supported launchpads, routers and markets.
Who signs the launch transaction?
The connected creator wallet. Joltwork compiles the plan and exposes the exact output; it does not take custody of the creator’s signing authority.
Need the execution model first?
Review Jolt Guard’s pre-hook, CPI route and postcondition phases.