The path to launch.

A floor for viability. Clear limits.

The soft cap is the minimum gross winning payments after clearing, before the platform fee. Deposits from losing bids and refundable cover do not count. If that threshold is missed, cancel before acquisition, return deposits in full and charge no platform fee.

An optional hard cap limits aggregate accepted deposits. A deposit that would cross it is rejected in full; reaching it never shortens the 24-hour window. This is a funding admission limit, not a token price or net-proceeds cap. It can favor earlier bidders and constrain price discovery. The initial raise has no selected soft-cap amount or hard-cap policy yet; these must be committed before opening.

The 2% platform fee is deducted from successful gross winning payments, rounded down once in lamports. It is not a surcharge on bidders, and refunds are excluded. For example, 100 SOL in winning payments leaves 98 SOL before inventory acquisition, network costs and any recovery reserve. Fee release requires verified delivery.

All collected platform fees are intended for future CIPHER buybacks and burns. That execution is not active. A reviewed fee vault, authorized spending policy, slippage limits and public purchase and burn receipts are required first. This policy promises neither a token price nor a return.

Your launch. Your keys.

The public launch intake lets creators choose an asset, destination, allocation, reserve, caps and delivery policy, then review and save a validated brief. The initial preset is a 24-hour SOL-funded token launch through Pump.fun. Other destinations remain planning options.

No private key, seed phrase, email or social login is requested. Saved briefs belong to the current browser session and expire after 24 hours; download the JSON to keep your own copy. Saving a brief does not publish an auction, authorize a transaction or establish ownership of an entered public wallet. Future execution must use explicit wallet signatures and reviewed escrow permissions.

Wallets and privacy

Solana wallet-standard discovery and injected EVM discovery are connection diagnostics. The Solana ownership proof signs an expiring, origin-bound message and verifies its Ed25519 signature server-side. It does not authorize a deposit, grant token approval or prove that a wallet can complete the auction.

Authenticated MPC settlement and private funding remain separate engineering work. Arcium bid-encryption helpers do not establish operator-blind privacy on their own. The initial raise is denominated in native SOL. No private payment or cross-chain route is currently enabled for this raise.

Five gates before opening

01 / Commit the terms

Finalize reserve, minimum raise, fees, inventory ceiling, delivery deadline and failure policy. Publish immutable metadata using the fingerprint logo at an unauthenticated public URI.

02 / Secure the funds

The native SOL prototype enforces funded admission, wallet caps and timeout refunds in compiled local-VM tests. Its settlement path is disabled. Authenticated private clearing, on-chain acquisition and independent review remain required.

03 / Automate the launch

The devnet coordinator validates signed instructions and auction context, journals before sending and reconciles identical retries. Connect an authentic settlement verifier, creator-controlled signer and reviewed funding path. There is no active launch scheduler or mainnet execution switch.

04 / Prove delivery

Verify custody, distribute exactly the winning amounts, preserve refunds and prove conservation under retries, partial failure and downtime. Define a funded recovery policy for a failure after acquisition.

05 / Rehearse and release

Run the complete funded devnet lifecycle, physical Phantom/Solflare mobile signing, adversarial contract tests and independent security review. Verify monitoring, incident response and recovery before mainnet activation.

The artwork and launch brief are ready for review. They do not establish that a live launch is production-ready.