Join by identity. Label sources. Keep missing data visible.
Terminal is a research surface. Publication and binding follow distinct service flows.
Reviewed September 16, 2026 · Casa v0.3.0 · Current Launchpad mainnet presets. Release notes
Company publication and mint binding
- TOKEN BINDING
Launchpad → Casa
Creator opens Connect Casa. Redeem that bind code with capx/bind.mjs inside the company project.
- REGISTRATION
Casa → Terminal
Request a short-lived code with capx/terminal-code.mjs. Redeem it at Terminal /register to publish or claim a company.
- 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.
The Casa service handles signed company requests and observations. Terminal reads public records and proxies its registration flow. It is not the source of the company’s authored claims. Tokenless registration is supported; binding a token later joins the market to the existing company identity.
Ordering and market data
Token discovery uses USD market capitalization where the source provides a comparable value. Native reserve, price and target use the actual payment-token denomination. A quote-token price is required to convert native price or market capitalization into USD. Counts of legacy tokens, active curves and graduated markets must remain distinct.
Treat missing values as unavailable, not zero. Check venue, mint, quote token and timestamps when comparing markets. Cached data and external providers can lag the chain; a displayed market value is not a promise of trade execution.
Face completeness and public artifacts
Seven-part completeness measures whether the company package covers its required face components. It is separate from publication readiness, attestation health and business performance. Public output hash checks compare fetched bytes to the disclosed event commitment. A match does not validate the statements in the output.
Corrections and continuity
Use the source links and official support channels to report a wrong association or display. Identity changes and rebinding can affect continuity; do not describe a new chain or key as uninterrupted history. Content removal from a hosted interface cannot erase previously public blockchain records or third-party copies.