Launchpad

Associate the token with a company identity.

Casa is optional at token creation. A company connection is separate from curve completion or liquidity migration.

Reviewed September 16, 2026 · Casa v0.3.0 · Current Launchpad mainnet presets. Release notes

CAPX / COMPANY CONNECTIONTwo codes. Two separate journeys.
  1. TOKEN BINDING

    Launchpad → Casa

    Creator opens Connect Casa. Redeem that bind code with capx/bind.mjs inside the company project.

  2. REGISTRATION

    Casa → Terminal

    Request a short-lived code with capx/terminal-code.mjs. Redeem it at Terminal /register to publish or claim a company.

  3. RESULT

    Stable company identity

    A published company has a slug page. Optional mint binding adds a market without replacing its history.

Do not paste a Launchpad bind code into Terminal registration. Tokenless company registration is supported.

Bind a Launchpad mint

  • As the creator, open the token on Launchpad and choose Connect Casa.
  • Obtain the bind code from Launchpad.
  • In the correct company project, use the Casa integration with the intended brain and company signing key.
  • Inspect the resulting mint and company association; retain company-brain/capx-bind.json.
Redeem the Launchpad bind codesh
node capx/bind.mjs --code <launchpad-bind-code> --brain company-brain

Replace the angle-bracket placeholder with the code issued to you; it is not a literal shell argument. Run from the Casa checkout, or use absolute paths. Binding is the integration’s initial go-public consent. It enables the bound update path described in the publishing guide.

Registering a Terminal company is different

Issue a Terminal registration codesh
node capx/terminal-code.mjs --brain company-brain

This second code comes from the Casa service and is redeemed at Terminal /register. It is short-lived and used to publish or claim a company page. A Launchpad bind code must be redeemed in the Casa project, not pasted into Terminal registration. A company can register without launching a token.

Rebinding

The integration supports a restricted rebind path with explicit confirmation and a public continuity break. Do not treat rebinding as an ordinary profile edit or silently change the company attached to a mint.