Launcher Access

Review the terms. Acknowledge the risk. Continue with clarity.

MSS Launcher access uses wallet-linked acknowledgements for builder and participant transactions. No identity verification, document upload, KYC or KYB is required for this flow.

Access Scope

Participant Launcher acknowledgements

Model

Acknowledgement only

Stage

Connect Wallet

Launcher acknowledgements

Choose the workflow you are using. Builder and participant transactions record separate acknowledgement requirements.

Wallet Address

Used only to record acknowledgements against the wallet taking the Launcher action and to apply any existing internal intervention block.

Launcher Acknowledgements

Participant terms and risk acknowledgement

No identity verification or KYC is required for this flow. Confirm the Launcher terms and risk disclosures before committing to a launch.

No identity check No legal name, ID document or date of birth is required.

Wallet recorded Acknowledgements are recorded against the wallet taking the action.

Risk acknowledged Transactions continue only after required terms are accepted.

I accept the MSS Launcher Terms for participating in this launch. I understand crypto launches carry significant risk and outcomes are not guaranteed. I accept the launch rules, allocation conditions and transaction conditions. I understand MSS provides information and infrastructure only, not investment advice.

Transaction access

Access remains open by default once the required acknowledgements are recorded. MSS does not require identity verification for this Launcher flow.

Selected Workflow

Participant

The role whose acknowledgement requirements are being recorded.

Current Outcome

Connect Wallet

Transaction access opens once the required terms are acknowledged unless an internal intervention block already exists.

What is required

The Launcher flow is based on transparent terms and wallet-linked acknowledgement rather than identity verification.

Connect or enter the wallet performing the Launcher action.

Select participant or builder mode for the correct terms.

Read and accept the relevant Launcher terms and risk acknowledgements.

Return to the launch or launch creator to continue the transaction.

Operational protection

Wallets can still be prevented from using transaction-sensitive Launcher actions where an internal intervention block has already been applied.

Builder Flow

Acknowledgement Only

Builders accept project accuracy and prohibited conduct terms before launch creation.

Participant Flow

Acknowledgement Only

Participants accept launch risk and transaction conditions before committing.

No ID verification required. A blocked wallet cannot complete Launcher transactions. Where a builder has already paid a Builder Bond before an internal block prevents launch creation, the Builder Bond refund result is surfaced through the launch creation transaction flow.