SatelliteLaunchPad Docs

SatelliteLaunchPad is a non-custodial token launchpad. You connect your own wallet, describe your token, and sign a single transaction that deploys a fixed-supply ERC‑20 contract on the network you chose. We never hold keys or funds, we do not take a fee, and the contract has no owner that could change it later.

1. Connect a wallet. Browser wallets such as MetaMask, Rabby or Coinbase Wallet are detected automatically. Mobile wallets work through WalletConnect when it is enabled on the site.
2. Fill in the form. Name, symbol and total supply are required. The website and description are optional and are stored on-chain inside the contract. Social handles are kept off-chain.
3. Pick a network. Tick “Show testnets” to rehearse on Sepolia or Base Sepolia with free test ETH before spending real gas.
4. Press Launch Token. Your wallet switches network if needed and shows one transaction. Review the gas estimate and confirm. The countdown starts as soon as it is broadcast.
5. Orbit. When the transaction is mined you see the contract address, explorer links and the add-to-wallet button. If anything fails, nothing is deployed and the form is restored.

Every launch deploys the same audited building blocks from OpenZeppelin Contracts v5: ERC20, ERC20Burnable and ERC20Permit. The constructor mints the whole supply (18 decimals) to the deployer and stores the website and description. There is no owner, no mint, no pause, no blacklist and no fee switch, so what you launch is what holders get, forever.

Compiler

solc 0.8.37+commit.f401782d

EVM version

cancun

Optimizer

enabled, 200 runs

Constructor

string name_, string symbol_, uint256 supply_, string website_, string description_

// SPDX-License-Identifier: MIT
pragma solidity ^0.8.20;

import {ERC20} from "@openzeppelin/contracts/token/ERC20/ERC20.sol";
import {ERC20Burnable} from "@openzeppelin/contracts/token/ERC20/extensions/ERC20Burnable.sol";
import {ERC20Permit} from "@openzeppelin/contracts/token/ERC20/extensions/ERC20Permit.sol";

/**
 * @title SatelliteToken
 * @notice Fixed-supply ERC-20 deployed by SatelliteLaunchPad directly from the
 *         creator's wallet. Built only from audited OpenZeppelin v5 components.
 *
 *  - The entire supply is minted once, to the deployer, in the constructor.
 *  - There is no owner, no mint function, no pause, no blacklist, no fee switch.
 *  - Holders can burn their own tokens (ERC20Burnable).
 *  - Gasless approvals are supported via EIP-2612 permit (ERC20Permit).
 *  - Project metadata (website / description) is stored on-chain, immutable.
 */
contract SatelliteToken is ERC20, ERC20Burnable, ERC20Permit {
    /// @notice Project website supplied at launch (may be empty).
    string public website;
    /// @notice Short project description supplied at launch (may be empty).
    string public description;
    /// @notice The platform that produced this deployment.
    string public constant LAUNCHPAD = "SatelliteLaunchPad";

    /**
     * @param name_        Token name, e.g. "SatelliteLaunchPad"
     * @param symbol_      Token symbol, e.g. "STPAD"
     * @param supply_      Whole-token supply (18 decimals are added here)
     * @param website_     Optional website URL
     * @param description_ Optional description
     */
    constructor(
        string memory name_,
        string memory symbol_,
        uint256 supply_,
        string memory website_,
        string memory description_
    ) ERC20(name_, symbol_) ERC20Permit(name_) {
        require(bytes(name_).length > 0, "SatelliteToken: empty name");
        require(bytes(symbol_).length > 0, "SatelliteToken: empty symbol");
        require(supply_ > 0, "SatelliteToken: zero supply");
        website = website_;
        description = description_;
        _mint(msg.sender, supply_ * 10 ** decimals());
    }
}

Explorers show a green check once the bytecode on-chain matches public source code. Launches are not verified automatically yet, so do it once per token:

1. Open your token’s address on the explorer and choose “Verify & Publish”.
2. Select Solidity (Standard JSON input), license MIT, and upload the standard JSON input file from the section above.
3. Contract name contracts/SatelliteToken.sol:SatelliteToken, compiler v0.8.37+commit.f401782d. Constructor arguments are usually detected from the deployment transaction; if asked, paste the ABI-encoded arguments shown by the explorer’s decoder.

SatelliteLaunchPad charges nothing. The only cost is the network gas for the deployment transaction, paid in the chain’s native coin from your wallet. Gas varies with network congestion; L2s such as Base and Arbitrum are usually a small fraction of Ethereum mainnet. Your wallet shows the exact estimate before you confirm, and a rejected or failed transaction never creates a token.

$STPAD is the planned native token of the SatelliteLaunchPad ecosystem (launch access, participation across the orbital network, and community). It has not been deployed yet. When it launches, the official contract address will be published on this page and on the official channels only. Any token using the name before that is an impostor. Tokenomics remain TBA until finalized.

Can I change the supply later?

No. The supply is fixed at deployment; there is no mint function. Holders can burn their own tokens.

Who owns the contract?

Nobody. The contract has no owner role and no privileged functions.

Can I use a different number of decimals?

Not currently. All launches use 18 decimals, the ERC-20 standard default.

Where is my launch history stored?

In your browser’s localStorage only. Clearing site data removes the list, not the token.

I rejected the transaction, is anything deployed?

No. A rejected or failed transaction deploys nothing and costs nothing beyond any gas a failed on-chain transaction consumed.