Infrastructure,
recursively.
The definitive guide to launching the things that launch the things that launch tokens.
Launch³ is a real infrastructure protocol for building launchpad launcher launchers. Its design addresses an overlooked bottleneck: people were still able to explain what their product did in one sentence.
Start one layer ahead.
Open the deployment console, name your launcher and choose an abstraction depth. The default depth of 3 represents a launcher for launchpad launchers, one level above a conventional launchpad launcher.
- Choose a launch architecture.
- Keep roadmap inheritance enabled for optimal ambition continuity.
- Select Deploy Launcher and observe the simulated deployment stages.
- Copy the configuration, or launch another layer.
The following is illustrative SDK syntax, not an installable package:
const launcher = await launch3.createLauncher({
name: "The Next Paradigm",
recursionDepth: 3,
architecture: "recursive",
roadmapInheritance: true
});Every layer has a purpose.
Usually, that purpose is to introduce another layer.
- Depth 0 · Memecoin
- The conceptual end product. Launch³ never creates one.
- Depth 1 · Launchpad
- A platform that launches memecoins.
- Depth 2 · Launchpad launcher
- A platform that creates launchpads.
- Depth 3 · Launch³
- A launcher that creates launchpad launchers. This is our groundbreaking contribution.
Depths 4–6 extend the same rule: each level launches the level immediately below. Names become longer; conviction remains constant.
Complexity, relocated.
The Recursive Deployment Engine is the real coordinator. It reads a configuration, resolves the requested depth and allocates one Launch Abstraction Layer per level. Each layer references its immediate downstream layer rather than the end product.
Launch Abstraction Layer
A boundary that isolates one layer's promises from another layer's implementation. A higher layer may inherit a roadmap without inheriting its deadlines.
Downstream Hype Propagation
A real event bus distributing revolutionary announcements through the hierarchy. Announcements can propagate before their underlying features, reducing time to narrative.
Architecture options
Recursive uses a nested hierarchy. Modular describes independent layers sharing the same configuration. Circular closes the conceptual dependency loop.
Configure the recursion.
| Option | Accepted values |
|---|---|
| name | 1–60 characters |
| recursionDepth | Integer, 1–6; default 3 |
| architecture | recursive, modular, circular |
| roadmapInheritance | true or false |
The simulated pipeline resolves dependencies, allocates abstraction, prepares the roadmap, propagates hype and returns a real deployment identifier. Disabling roadmap inheritance produces a configuration with no inherited roadmap; ambition must then be supplied locally.
“Launch Another Layer” increases the selected depth by one and returns you to configuration. At depth 6, the maximum supported depth, the control stops offering more layers.
Consensus by declaration.
Proof of Launch is the real acknowledgement emitted when the simulation completes. It confirms that the browser has produced a configuration and a result panel. It does not prove a transaction, token issuance or blockchain state change.
{
"status": "conceptually_complete",
"consensus": "self_declared",
"utility": "inherited",
"onChain": false
}The protocol's unprecedented efficiency comes from not asking a network to agree with it.
A future-facing interface.
These are real API contracts for the satire. No live endpoint or downloadable SDK is provided.
launch3.createLauncher(config)
Conceptually accepts the configuration above and returns a launcher object with an identifier, selected depth and architecture. Invalid depths should be rejected rather than quietly abstracted away.
launcher.launchAnotherLayer()
Conceptually prepares a new configuration with recursionDepth increased by one, capped at 6. Roadmap preferences and architecture remain unchanged.
launcher.exportConfig()
Returns a JSON-shaped configuration. The playground's Copy Configuration button implements this locally, including a simulation flag so it cannot be mistaken for an on-chain receipt.
Resolve your abstractions.
Launcher launched a launchpad instead of a launchpad launcher.
Check your depth. Depth 1 represents a launchpad; depth 2 a launchpad launcher. Use depth 3 for the Launch³ default.
Maximum abstraction depth exceeded.
The playground supports 1–6 layers. Reduce depth to 6 or lower. Infinite recursion is reserved for strategy meetings.
Underlying utility unexpectedly detected.
This real warning suggests your architecture has become too easy to explain. Consider another layer. No real error is raised by the playground.
Circular roadmap dependency.
Your milestones depend on their own completion. Switch to Recursive architecture for a linear explanation of the same ambitions.
Copy button did not work.
Your browser may block clipboard access. Select the visible code or configuration and copy it manually. The interface reports a copy failure rather than claiming success.
Remaining questions.
Do I need a wallet?
No. The playground is entirely local and never asks you to connect one.
Is the token CA a deployment output?
No. The optional site-wide contract address is separate from the simulation. It displays “coming soon” until the site owner supplies one.
Is my configuration saved?
The launcher remembers your latest settings in this browser when local storage is available. Contact form entries are not saved or sent.
Where do I go from here?
Launch a Launcher Launcher launcher. Or close the tab and launch a memecoin. Both are technically possible.