Skip to main content

​
What it is

A launch through the SDK or the CLI builds the same transaction as the site. You pick a preset, name your integrator authority, supply a mint key and send.

​
When to use it

Use it after the Quickstart, when you build launches into your own product.

​
Step by step

1

Pick a preset

The SDK exports them as PRESETS. The CLI takes the name with --preset.
2

Name your integrator

A launch can name the authority of a registered integrator.
With the SDK, pass integrator: new PublicKey(authority) to client.launch. The integrator is recorded on the token record and never changes for that token.
3

Supply the mint key

You generate the mint keypair. The CLI makes one in memory by default and never prints it. To keep the mint address stable (a vanity address, a retry after a failed send), pass a keypair file:
The mint signs the launch transaction together with the creator. Keep the file out of version control.
4

Add a dev buy, if you want one

--dev-buy <SOL> buys at launch, into a locked vault. The tokens stay locked until the unlock time.

​
Numbers and limits

These are starting values and may change before the mainnet launch. A Solana transaction is at most 1232 bytes. The launch carries the name, the ticker and the metadata URI inside it. Every uri the upload service returns is at most 60 characters, for example https://m.pariprotocol.xyz/m/<id>, so a launch with the service’s URI fits.

​
What can go wrong

It is not an error. The builder leaves it out, and the integrator share of that token goes to the treasury. Registration is by form and is reviewed. pari integrator request prints the form address and the fields, and --submit posts the request.
The transaction is over the limit. Shorten the name, the ticker or the URI, or drop the integrator. If you host your own metadata, keep the URL short.
It is over the preset’s cap.

​
Next

Uploads

Short URIs for your metadata.

Fees and payouts

What you receive for each launch.