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.

STAGINGPublic partner API

Staging endpoint at api.fjf2or.com builds unsigned launch transactions with a fresh blockhash and a simulation. The server never signs or sends. Production not approved.

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 · STAGING TESTED

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 · STAGING

Understand the fees and current limitations

Recorded configuration: the 1% platform fee. On the operator test pool the pool-level platform fee counter stayed 0. LaunchLab accrues platform fees in a per-platform vault in the quote token instead (1% of the quote traded on the test pool: 0.08532359 MSTRx), and that vault was claimed once on-chain by the platform fee wallet. The 3% Token-2022 transfer fee accumulates separately in the launched token; its withdrawal has not been done. These fees came from bot-like third-party trading, not from independent buyers. Claims depend on the quote token issuer, who keeps freeze and permanent-delegate rights.

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.

OPERATOR TEST · VERIFIED ON-CHAIN

One launch.
Checked on the chain.

On 12 October 2026 the operator ran one test launch from a new test wallet through the staging flow. Everything below can be checked on a public explorer. It is a technical test, not customer activity.

What this shows, and what it does not

Shows: the unsigned-transaction flow produced a transaction that the test wallet and a fresh mint key signed locally and that ran on mainnet. It created a LaunchLab pool under the Fjf2or PlatformConfig, with the test wallet recorded as creator. The token has no mint or freeze authority. The server prepared and simulated the transaction; it did not sign or send it.

Third-party trading is not independent demand. Within about 80 seconds of creation, ten other wallets made 17 swaps on the pool, the first one in the slot right after creation, and seven of them bought and sold within about 40 seconds. We treat this as bot-like trading. It is not evidence of independent buyers or demand and is not counted as such.

Platform fee, claimed once. 1% of the MSTRx traded on this pool accrued in the platform fee vault: 0.08532359 MSTRx, accrued from the trading on this pool, which was bot-like. The platform fee wallet claimed it once on-chain (transaction above). This shows the fee mechanism works. It is not demand and not revenue to rely on; no value is assigned to the amount.

Not shown: the 3% Token-2022 transfer fee has accumulated withheld tokens on the mint; they have not been withdrawn. No independent creator or buyer has used this flow. The metadata content (image and description) is not independently verified here. No creator payout, settlement or revenue share exists; the settlement panel further down uses synthetic data. MSTRx is controlled by its issuer, who keeps freeze and permanent-delegate rights.

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. The walkthrough below is offline; the staging API is separate.

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.

Staging base URL: https://api.fjf2or.com (synthetic consent, mainnet NO-GO, closed beta). The same routes exist as an in-process prototype. Wallet-signature authentication is real; the terms consent is a demo and not a real agreement. Beta limits: 3 launches per day and 20 in total per wallet, a protected-name list against impersonation, and a closed list of allowed wallets. Metadata content is not fetched or verified by the server (host check only).

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/onboarding

Record the demo consent for a session (required before a launch request).

POST/v1/launch/build

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

POST/v1/launch/prepare

Unsigned transaction with a fresh RPC blockhash and a simulateTransaction result; never sent by the server.

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 creator launching through the staging flow, and one integrator reviewing it. Production use follows separate approval and fresh evidence.

RECORDED Mainnet platform and fee authority configuration
VERIFIED ON-CHAIN One operator test launch and one platform-fee claim (12 Oct 2026); not customer activity
OFFLINE TESTED Builder, API boundaries and settlement protections
STAGING Public unsigned-transaction API with preflight, closed beta
PLANNED Partner connectors
BLOCKED Independent creator launches, fee monetization and creator 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

[email protected]

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 [email protected] ↗

A clearer path
from launch
to settlement.

A defined profile.
Clear responsibilities.

For creators

For integrators

For bot operators

Fjf2or / MSTRx

One launch.
Checked on the chain.

Operator Test (OPTEST)

Inspect the flow.
Keep control of the keys.

Public launch request

Request & draft review

Track receipts.
Understand the liability.

Settlement overview

Collect or claim

Verify quote receipts

Accrue & reconcile

A small interface.
An explicit boundary.

Ready for a technical conversation.

Become a Partner.

Contact us

Open an email draft

A clearer pathfrom launchto settlement.

A defined profile.Clear responsibilities.

For creators

For integrators

For bot operators

Fjf2or / MSTRx

One launch.Checked on the chain.

Operator Test (OPTEST)

Inspect the flow.Keep control of the keys.

Public launch request

Request & draft review

Track receipts.Understand the liability.

Settlement overview

Collect or claim

Verify quote receipts

Accrue & reconcile

A small interface.An explicit boundary.

Ready for a technical conversation.

Become a Partner.

Contact us

Open an email draft

A clearer path
from launch
to settlement.

A defined profile.
Clear responsibilities.

One launch.
Checked on the chain.

Inspect the flow.
Keep control of the keys.

Track receipts.
Understand the liability.

A small interface.
An explicit boundary.