RAYDIUM LAUNCHLAB · TOKEN-2022

A clearer path
from launch
to settlement.

Your creator. Your workflow. One explicit platform profile — with unsigned preparation and a transparent path for fee accounting.

Explore the demo Read the partner brief ↗

An integration review, not a production launch service.

THE INTEGRATION PATHOFFLINE PREVIEW

Creator inputsUnsigned draftClient review

MAINNET SNAPSHOTPlatform configuration

Recorded on-chain evidence; not a live status check.

OFFLINE TESTEDUnsigned preparation

Existing canonical builder and API adapter.

PLANNEDPublic partner API

No deployed endpoint or approved live launch.

01 / THE PLATFORM

A defined profile.
Clear responsibilities.

Built around an existing LaunchLab configuration. Partner integrations can evaluate Fjf2or as an explicit launch profile.

For creators

Review public token inputs and know which platform receives the fees. Payer and mint keys stay with your client.

UNSIGNED FLOW · OFFLINE

For integrators

Keep your interface and feed. Evaluate a fixed Fjf2or preset or an unsigned builder connector without a new launch contract.

PARTNER CONNECTOR · PLANNED

For bot operators

Use structured public inputs, creator-bound authentication and idempotent draft requests. Trigger execution stays outside this demo.

API ADAPTER · OFFLINE

Understand the fees and current limitations

Platform fees are received in the quote asset. Token-2022 transfer fees accumulate in the launched token and require authorized withdrawal. Collected tokens are not quote revenue until actually sold. Only attributed, verified quote receipts can support settlement.

The recorded configuration assigns post-migration CPMM / LP fee rights to Ashmih; an off-chain agreement does not transfer those rights automatically. MSTRx has issuer-controlled extensions. Price, liquidity, migration, creator income and holder rewards are not guaranteed. This demonstration does not reproduce StonkFun's holder-reward promises.

The current sale automation supports migrated CPMM pools; a pre-migration fee-token sale is not an available automated feature. No integration with J7, Uxento or LaunchBlitz has been confirmed.

02 / INTERACTIVE WALKTHROUGH

Inspect the flow.
Keep control of the keys.

Validate a public request locally, then inspect an archived unsigned example. Edited inputs never generate a transaction in this page.

1Public inputs
2Request validation
3Archived draft review
4Live gates — blocked

Public launch request

LOCAL ONLY

Example addresses are fixtures, not approved launch participants. Enter public keys only.

Ready for local validation. Nothing will be submitted.

Request & draft review

NOT SENDABLE

A local request preview. No endpoint is called.

Validate the public request to see its JSON shape.

✓ Fixed Fjf2or configuration

✓ Archived draft: two zero signatures

✓ No wallet provider or RPC connection

○ Fresh preflight and production approval required

Inspect full archived unsigned fixture ↓

Placeholder blockhash; historical cost; expired test clock. Editing inputs does not change this fixture.

Review ends here. A future live flow needs published metadata, verified creator consent, fresh mainnet costs and simulation, custody review and an approved economic / execution plan. This page cannot sign or broadcast.

03 / RECEIPT-BASED ACCOUNTING

Track receipts.
Understand the liability.

Fee collection, monetization and creator payout are separate steps. The panel below is a presentation of synthetic records, not a live ledger.

DEMO · SYNTHETIC DATA

Settlement overview

Show receipts

Illustrative 50/50 accounting rule from the existing offline implementation. Not a commercial offer or guaranteed payout.

Attributed quote receipts1.20 MSTRx

Creator allocation0.60 MSTRx

Operator allocation0.60 MSTRx

Creator balance due0.40 MSTRx

Synthetic receipt records — every row is a DEMO
Reference	Source	Quote received	Evidence status

Demo creator paid: 0.20 MSTRx. Totals remain cumulative when filtering.

NO PAYOUT ACTION

Collect or claim

Authorized fee collection to the configured platform receiver.

Verify quote receipts

Attribute finalized claim or sale proceeds to the correct mint and creator.

Accrue & reconcile

Immutable terms, persistent reservations and receipt deduplication in the existing ledger.

04 / INTEGRATION CONTRACT

A small interface.
An explicit boundary.

These paths describe the existing in-process API prototype. No HTTP base URL is deployed. Authentication and execution are not simulated as real user consent.

GET/v1/platform

Inspect the fixed profile and demo terms.

POST/v1/auth/challenge

Request a nonce-bound creator authentication message.

POST/v1/auth/verify

Verify a client-supplied Ed25519 message proof.

POST/v1/launch/build

Prepare a canonical unsigned draft. Creator-bound session and idempotency required.

IN-PROCESS REQUEST SHAPEDOCUMENTATION ONLY

await handle({
  method: "POST",
  path: "/v1/launch/build",
  bearer: "<creator-bound session>",
  idempotencyKey: "partner_review_001",
  body: {
    creator: "<public payer key>",
    mint: "<public mint key>",
    name: "Example token",
    symbol: "EXAMPLE",
    uri: "https://ipfs.io/ipfs/<CID>"
  }
});

Documentation example, not an executable browser request.

API documentation ↗Explore OpenAPI ↗One-page partner brief ↗

05 / EVIDENCE, NOT PROMISES

Ready for a technical conversation.

The next milestone is one independent integrator reviewing the unsigned flow. Production use follows separate approval and fresh evidence.

RECORDED Mainnet platform and fee authority configuration
OFFLINE TESTED Builder, API boundaries and settlement protections
PLANNED Public API, durable sessions and partner connectors
BLOCKED Live end-to-end launch, fee monetization and payout

06 / LET’S BUILD A CLEARER FLOW

Become a Partner.

Tell us about your integration or creator workflow. We start with an offline technical review, not a production rollout.

OFFLINE PARTNER REVIEW

Contact us

partners@fjf2or.com

Creators, integrators and bot operators are welcome to discuss a fixed platform preset, unsigned builder connector or a first-user flow review.

Share your integration goals and requirements. Commercial terms follow technical review; no fixed revenue share or earnings are promised.

Read the one-page partner brief ↗

Open an email draft

This form opens your email application. It does not send a message or submit data to a backend. Review and send the draft yourself. A configured email app is required.

Nothing is submitted or stored by this page.

Open email app or use partners@fjf2or.com ↗

A clearer pathfrom launchto settlement.

A defined profile.Clear responsibilities.