Start shared.Keep the escape route.
Create projects, assets, stable assets, SPACE, liquidity and privacy profiles on MIRCO Main — then move into Studio only when your product truly needs independent network control.
Project
A project created on MIRCO Main with the surrounding ecosystem available by design.
Describe what you are creating.
Not the infrastructure you are renting.
Launcher is project-facing. It should generate the shared MIRCO Main creation intent and canonical configuration needed by the ecosystem — not become a validator or VPS control panel.
Project on MIRCO Main
Start on the shared flagship network and inherit the ecosystem around it. No validator topology or deployment burden is introduced at the product-creation layer.
LaunchIntent {
kind: PROJECT
network: MIRCO_MAIN
sovereignty: SHARED
wallet: ENABLED
explorer: ENABLED
}
A launch should not create an island.
The reason to start inside MIRCO is the ecosystem that can remain around the project as it grows.
User-facing money, receive routes and signing stay in the Wallet product.
Liquidity, RFQ and settlement can be connected where the active product requires them.
State and assurance become visible without building a separate truth surface.
Native identity can connect the project to deeper MIRCO experiences.
Privacy capabilities are selected explicitly and fail closed when required but unavailable.
Create the product.
Studio shapes the network.
Keeping this boundary clean prevents the creation experience from becoming a giant infrastructure dashboard.
Project-facing creation
The creation surface belongs to shared MIRCO Main product configuration.
Network/operator configuration
Studio owns execution profiles, validators, security, privacy infrastructure, issuer settings, HSM and deployment manifests.
Escalate only when independence becomes a requirement.
These are network requirements — not Launcher settings.
If the project genuinely needs independent validator governance or infrastructure boundaries, Launcher should hand off the project context instead of trying to absorb Studio and Deploy.
Creation can be simple.
The consequences must still be explicit.
Launcher targets shared MIRCO Main unless the user deliberately escalates out.
Network + canonical asset identity remains the rule.
Requested privacy cannot silently downgrade.
Fee and sponsorship choices are explicit policy, not hidden defaults.
Launcher never manufactures validator, issuer or signing authority.
Create the product.
Carry sovereignty only when you need it.
Start on MIRCO Main, inherit the ecosystem, and keep the path open to a sovereign network without turning day one into an infrastructure project.