Skip to main content

Launchpad

Senticore Launchpad is a permissionless, fee-gated intake path for token launches that become TOKEN/USDC spot markets on Senticore. There is no human review: a non-refundable launch fee is the economic gate, the token contract is a fixed Senticore template (the deployer cannot supply custom code), and listed markets are clearly labeled as unaudited.

The current implementation covers application intake, PDF hashing and storage, wallet authorization with a signed risk-terms acceptance, the non-refundable launch fee, an automated chain orchestration worker, and post-distribution TOKEN/USDC listing.

Current Rules​

ItemCurrent rule
Frontend route/launchpad
GateNon-refundable launch fee (economic anti-spam gate, no human review)
Submit fee10,000 USDC (launchpadFeeUsdcMicro, deploy-config driven)
RefundsNone, except when Senticore cannot start minting (pre-mint failure)
TokenFixed-supply OpenZeppelin ERC-20 + Permit, deployed from the SenticoreERC20-v1 template only
Risk termsAccepted version is bound into the wallet signature (tosVersion)
LabelingListed Launchpad assets are flagged unaudited with no Senticore endorsement
Bridge targetOfficial Arbitrum bridge
Distribution target99.5% deployer wallet, 0.5% market-maker wallet (instant ledger credit)
Market targetTOKEN/USDC spot pair after distribution
Reserved tickersMajor assets and Senticore tickers are blocked

Application Flow​

  1. Applicant submits ticker, symbol, project description, market-maker wallet, total supply, whitepaper PDF, and tokenomics PDF, and accepts the risk terms.
  2. Browser computes SHA-256 content IDs for the PDFs.
  3. Applicant wallet signs the Launchpad submit authorization, which includes the fee, the SHA-256 content IDs, and the accepted risk-terms version.
  4. API validates origin, signature, nonce, fields, file type, file size, reserved/duplicate tickers, and the accepted risk-terms version.
  5. Sequencer moves the non-refundable launch fee from the applicant to the Launchpad fee account, and the application advances to fee_paid.
  6. When chain automation is enabled, the orchestrator picks up fee_paid applications and runs mint → bridge → distribute → list automatically.
  7. Distribution credits 99.5% to the deployer and 0.5% to the market-maker wallet, then opens the TOKEN/USDC spot market (listed).
  8. If a stage fails before minting, the fee is refunded; after minting (tokens exist on-chain) the application is marked failed and reconciled manually, with no automatic refund.

Why a fee instead of review​

A fee-gated, template-locked model follows the same economic-gate principle as Hyperliquid's HIP-1 (the deployment cost is the anti-spam mechanism, not a human gatekeeper). Because every token is the fixed SenticoreERC20-v1 template, contract-level rugpulls (hidden mint, honeypot, pause, blacklist) are impossible by construction; the remaining exposure is ordinary market risk, which the unaudited labeling and post-listing PauseAsset control address.

Release Gate​

LAUNCHPAD_CHAIN_ENABLED is disabled by default. With the default configuration, starting orchestration returns 503, so applications cannot enter mint, bridge, distribution, or listing automation by accident — they simply hold in fee_paid.

Production chain automation must stay disabled until:

  • production secrets and RPCs are configured,
  • the official Arbitrum gateway router is selected,
  • the MultiCollateralVault address and asset activation path are verified,
  • gas monitoring and manual recovery are ready,
  • StateCommitment and sequencer roots match the intended release snapshot,
  • release approval explicitly enables LAUNCHPAD_CHAIN_ENABLED and starts the orchestrator.

This keeps Launchpad intake separate from irreversible L1/L2 token operations until the release boundary is clear.