DegenCast
$CAST TokenLaunch App
  • Multichain Launch
    • Background: $CAST
    • High-Level Overview
    • Key Components
      • 1. Foundation Token $CAST
      • 2. Launched Tokens $T
      • 3. Liquidity Pools
      • 4. Cross-Chain Bridging
    • Workflow
      • 1. Token Launch Process
      • 2. Price Convergence & Arbitrage
      • 3. Inventory-Based Arbitrage
    • Implementation Details
      • 1. Contracts on Base
      • 2. Contracts on Solana
      • 3. Bridging Mechanism
      • 4. Security & Audits
    • Launchpad User Guide
      • 1. Project Owners
      • 2. Investors
      • 3. Arbitrageurs & Market Makers
  • Multiplatform Launch
    • Introduction
    • Key Components
      • 1. Mother Token
      • 2. Child Tokens
      • 3. Bridge / Swap Mechanism
    • System Architecture
      • 1. Token Contracts
      • 2. Vault / Escrow
      • 3. Launchpad-Specific Deployments
    • Launch Flow & Process
      • 1. Preparation
      • 2. Deploying Mother Token & Vault
      • 3. Deploying Child Tokens
      • 4. Bridging Setup
  • Disclaimer
Powered by GitBook
On this page

Was this helpful?

  1. Multiplatform Launch
  2. Key Components

2. Child Tokens

1. Definition: Token instances deployed on external chains or launchpads (Pump on Solana, Virtual on Base) that fulfill local requirements—most importantly, “100% circulation at launch.”

2. Launch Mechanics:

• Each Child Token contract mints a specified supply upfront (e.g., 5B tokens for Pump, 10B tokens for Virtual).

• Distributed via each launchpad’s IDO/ICO mechanism.

3. Limited Utility:

• Generally, the Child Token confers no direct governance or advanced features.

• Instead, Child Tokens act as “wrappers” or placeholders that can be burned in exchange for the Mother Token.

Previous1. Mother TokenNext3. Bridge / Swap Mechanism

Last updated 4 months ago

Was this helpful?