Sources and documentation scope
The product description follows the creator's brief. Base is the live production network. Stellar contract behavior follows the sibling source repositories. Comparable launchpad documentation informed the organization, not claims about Launchpad's implementation.
Implementation sources
| Source in the project workspace | Used for |
|---|---|
evm-contract/src/Factory.sol | Base factory settings, pair token, vault deployment, and deposit behavior |
evm-contract/src/BondingCurve.sol | Base curve vault |
evm-contract/script/Deploy.s.sol | Base and Base Sepolia deploy path, including native Circle USDC |
stellar-contract / launchpad-contract packages and contracts | Stellar factory, vault, reputation, and historical Testnet evidence |
interface and lumenrise-interface | User flows, visual identity, authentication, and prototype limitations |
These are workspace-relative source references, not public service URLs. Local implementation and network deployment are described separately throughout the docs.
Comparable launchpad documentation
- Legion Help Center separates account setup, reputation, sales, and user support.
- Legion's score guide explains its own reputation model and how contribution affects access. Launchpad's scores and policies are independently specified here.
- Fjord's sale-format guide distinguishes sale mechanisms before creator setup.
- Fjord's fixed-price creation guide is a reference for a task-based creator journey.
- PinkSale's presale vesting guide treats contributor vesting and claims as explicit topics.
Launchpad does not inherit those platforms' chains, pricing mechanisms, score scales, verification policies, or settlement behavior.
Chain and integration references
- Base: the live LumenRise network.
- Circle USDC on Base:
0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913. - Stellar Asset Contract: how the same Stellar asset is used by accounts and contracts.
- Stellar RPC API reference: simulation, transaction results, and event-query methods.
Editorial conventions
Base is described as live. Stellar is described as the expansion, with factory and reputation source documented so integrators can start. “Implemented in source” means a matching path exists in the reviewed Stellar code. It does not mean that network already matches every Base feature.
Examples are illustrative unless explicitly identified as historical transaction evidence. Proposed API and CLI interfaces are not advertised as callable endpoints or installed tools. Open auction and presale decisions on Stellar are stated rather than filled in with invented mechanics.