LaunchifyDocumentation · v8Chain 4663 ↗
LAUNCHPAD INFRASTRUCTURE

Launch businesses,
not only tokens.

Launchify lets an operator deploy a branded launchpad with its own storefront, verified namespace, market rules, token explorer, owner analytics and automated fee route.

One storefrontA direct launchify.store subdomain for every active pad.
Multiple marketsStocks, collectibles, communities, memes, creators, gaming and AI.
Shared revenueEvery token uses the deterministic 70/20/10 fee route.
01 · MARKET MODES

Choose a market and its provider.

UI V9 keeps provider rails separate. Stock and community pads use Pons V2. Commodity and card-price-index pads call the verified Commodity Market Exchange V6 router directly; CME assets are never passed into the Pons factory.

ModeCreator choosesExecutionStocks

Any currently Pons-approved canonical Stock Token

Pons V2 pairTokenCommodities

Live CME reference pair

CME V6 · direct onchainCard price indexes

Live trading-card reference pair

CME V6 · direct onchainCollectibles

An owner-approved community category

Pons V2 · ETHCommunity / memes / creators

Token identity and story

Pons V2 · ETH
Important

Commodity and card-index coins are synthetic reference-price markets. They are not title to gold, oil, a card or another physical item. Redeemable collectibles remain disabled and marked custody partner required.

Pons catalog

Robinhood registry + Pons allowlist

CME catalog

Verified from the CME V6 onchain pair registry

Settlement

Robinhood Chain · provider controlled

02 · PAD TEMPLATES

Start with the right operating format.

Classic

Universal, clear launch flow for any community.

Market terminal

Data-led structure for stock and market-focused pads.

Gallery

Visual-first structure for collectibles and culture.

Community

Story and participation-led structure for creators and agents.

The v4 template selector previews each format, cycles through them with a typed headline, and carries the selected format directly into the launchpad builder.

03 · LAUNCH FLOW

Provider-aware execution.

  1. The creator chooses a market in the launchpad storefront.
  2. Pons pads connect the wallet, upload the image, deploy the 70/20/10 splitter and confirm through Pons V2.
  3. CME pads show the chosen reference market and continue to the official CME V6 launch app.
  4. The creator rechecks the live commodity contract, provider fee and pool before signing there.
  5. Launchify never labels a CME price-index token as physical ownership or redemption.
04 · FEES

Fees follow the selected provider.

Pons V270% token creator20% launchpad owner10% Launchify protocol

Pons pads use the protected Launchify splitter. CME pads use the provider fee configured and displayed by Commodity Market Exchange V6. Launchify does not replace, intercept or describe CME fees as Launchify owner revenue.

05 · ANALYTICS

Live operating intelligence.

The owner dashboard includes total and unique creators, launches over 24 hours, 7 days and 30 days, average daily launches, market distribution, recent launches, onchain earned revenue, claimable revenue and active fee routes. Owners can also update their public description, artwork and the fee applied to future launches. The Launchify treasury signer has a consolidated command center plus read-only access to every storefront dashboard; revenue claims remain restricted to each launchpad owner.

Launch counts come from verified Launchify records. Revenue and claimable balances are read from the deployed splitters on Robinhood Chain.

06 · MONITORING

Production failures are recorded.

The API stores failed launch stages and unexpected server errors as operational events. Each owner can see recent pad incidents. A recurring treasury monitor checks the protocol wallet every five minutes and creates a critical event below the configured threshold.

SignalRecordedAlert levelLaunch failure

Stage, message, wallet and pad

WarningAPI error

Route, method and request ID

CriticalLow treasury

Balance and configured threshold

Critical

Events appear in the treasury command center and can be delivered directly to Discord with DISCORD_ALERT_WEBHOOK_URL or Telegram with TELEGRAM_BOT_TOKEN and TELEGRAM_CHAT_ID.

07 · SECURITY

Wallet-signed ownership.

Launchify never requests private keys. Authentication uses a one-time wallet signature. Pad registration and token launches are independently verified from Robinhood Chain receipts. Images are signature-checked, size-limited and rate-limited before storage.

An internal pre-audit and external-audit handoff are maintained in the repository. The contracts must not be described as independently audited until a separate auditor issues a signed report.

08 · API

Core endpoints.

GET /healthAPI and chain configuration healthGET /v1/padsActive pad directoryGET /v1/pads/:slugPad configuration and launchesPOST /v1/padsCreate a wallet-owned padPOST /v1/pads/:id/launchesVerify and index a Pons launchGET /v1/pads/:id/analyticsPrivate owner analytics and incidentsGET /v1/protocol/monitoringPrivate treasury-level monitoring
09 · CURRENT LIMITS

What Launchify does not claim.

  • Solana products can inspire workflows and templates, but no Solana contract, liquidity or asset is bridged into Launchify.
  • A stock-paired launch is a new Pons token quoted against a Robinhood Stock Token; it is not itself stock, equity, a dividend right or a claim on the underlying company.
  • Collectible references are categories, not custody or proof of ownership of a physical item.
  • UI V9 performs direct CME V6 execution using the published router and verifies the resulting LaunchCreated event before indexing. CME trading fees remain governed by CME; Launchify does not claim a share of them.
  • CME reference tokens do not provide delivery, storage rights or redemption. A verified custodian, authenticated inventory and an audited NFT/RWA adapter are required before those claims can be enabled.