Platform / Launchpad
latch
EARLY ACCESS
TOKEN LAUNCH INFRASTRUCTURE

Launchpad

Discover launch configurations. Define your next opening.

Solana ecosystem
ANTI-SNIPER LAUNCH DESIGN / EARLY ACCESS

Put a ceiling
on launch snipers.

Designed to cap how much token supply one address can receive at launch. Shared order windows reduce the advantage of buying first.

Allocation studio available. On-chain deployment is not enabled.
DESIGNED TO LIMIT OVERSIZED OPENING ALLOCATIONS.
SHARED WINDOWSSUPPLY CAPSPROPORTIONAL ALLOCATION
LATCH / OFFICIAL TOKEN

Contract & community

SOLANA
Only use the contract address published in this box.
Follow on XPump.fun

The community token and the allocation simulator are separate. This page does not activate on-chain launch protection.

ALLOCATION DESIGN
Batch allocationPLANNED MECHANISM
ORDER WINDOW
60 secondsCONFIGURABLE WINDOW
SUPPLY CAP / ADDRESS
1.00%OF TOTAL TOKEN SUPPLY / MODEL
LAUNCH STUDIO
AvailableCONFIGURATION & SIMULATION
CURATED CONFIGURATIONS

Every opening has a blueprint.

Illustrative projects · No live markets
PROJECT WORKSPACE

Explore launches

EXAMPLE PROJECTS
PROJECTMECHANISMWINDOWSUPPLY CAPSTATUSSave project
04 PROJECTSILLUSTRATIVE PROJECT SPECIFICATIONS
ALLOCATION STUDIO

Define the opening

Configure a token supply cap and test an oversized order.

1.0%SUPPLY CAP
PER ADDRESS10,000 tokensof 1,000,000 modeled supply
Order window60 SEC
% SUPPLY
SIMULATION / NO TRANSACTION
THE PROBLEM / THE PLANNED CONTROLS

A big opening buy.
A defined allocation limit.

The proposed model targets oversized opening allocations and arrival-order priority. Explore exactly what it would limit.

01 / SUPPLY LIMIT

Cap the tokens received.

A percentage of total supply per address. A larger order cannot raise that address’s allocation ceiling in the model.

02 / SHARED WINDOW

Remove first-order priority.

Collect requests in the same opening window. Arrival order does not determine allocation within the modeled batch.

03 / PROPORTIONAL SETTLEMENT

Scale down excess demand.

If capped requests exceed the opening pool, reduce them proportionally. Never redistribute above the address cap.

Designed to reduce sniping. Not sniper-proof. Multiple wallets can bypass a per-address limit. The controls shown here are not yet deployed on-chain.

One operator can use many wallets.

A supply cap limits an address. It does not identify a person or stop someone splitting orders across many wallets. This is a known limitation of the planned model.

From concept to launch specification.

Define a project, set opening parameters, and save a local draft with the proposed allocation rules attached.

LAUNCH STUDIO / SPECIFICATION

Define your launch.

Prepare your launch specification with a supply cap and shared opening window. On-chain token deployment is not enabled.

Stored in this browser only. Do not enter private keys or seed phrases.
MECHANISM / DESIGN SPECIFICATION

Limit the opening allocation.

A proposed anti-sniping model. Live on-chain enforcement is in development.

01 / Fixed order window

Collect orders during the same window. In the simulation, an earlier arrival has no priority.

02 / Cap token supply per address

Cap each address’s token request as a percentage of total supply. If capped demand exceeds the opening pool, scale allocations proportionally. Leave unused supply unallocated rather than exceed a cap.

03 / Publish the allocation rules

Show the window and cap before participation. Production enforcement would require reviewed contracts and verifiable settlement.

Not sniper-proof. One operator can use many addresses. This model does not stop Sybil activity, manipulation after opening, malicious token permissions, or contract exploits.
ALLOCATION ENGINE / SIMULATOR

Allocation breakdown.

Model: 1,000,000 total tokens offered in the opening. One address requests 40% of supply; each other address requests 1%. Apply the address cap, then scale down if capped demand exceeds supply.

Large address request40.00% of supply
After model allocation1.00% received
Both bars use the same scale. Simulator only.
This is a mathematical model, not a live order book or investment outcome. An address is not a verified unique person.
PROJECT SPECIFICATION / NOT DEPLOYED

This entry has no deployed contract. Supply caps and batch allocation are planned controls, not active protections. Token permissions and security have not been checked.