Minting sends SPL tokens from a tokenized share class’s on-chain mint to a stakeholder’s Solana wallet. Each token represents one share unit. After minting, the transaction is recorded with a hash you can verify on the Solana explorer — giving the stakeholder cryptographic proof that their tokens have been delivered on-chain.Documentation Index
Fetch the complete documentation index at: https://docs.launchboard.xyz/llms.txt
Use this file to discover all available pages before exploring further.
How Launchboard resolves a stakeholder’s wallet
Launchboard determines the destination wallet for each stakeholder in this order:- Saved Solana wallet address — the address entered directly on the stakeholder’s profile.
- OASIS avatar — if the stakeholder has an OASIS account linked, Launchboard looks up the Solana wallet associated with that avatar.
Three ways to mint
| Path | How to access | Approval required? | Vesting-aware? |
|---|---|---|---|
| Securities table → Mint | Cap Table → Securities → click Mint on a row | Yes — security must have a linked approval with status Approved or Locked | Yes — mints the cliff/currently-vested amount only |
| Issue Shares / Issue Options | Transactions → Issue Shares or Issue Options | No | No — mints full quantity immediately |
| Tokenize from Document | Dataroom → open a signed, merged document → click Tokenize | No | No — mints full quantity immediately |
Minting via the Securities table
This is the most common path for securities that already exist in your cap table.Confirm the share class is tokenized
The security’s share class must be tokenized before minting is possible. If it is not, tokenize the class first — see Tokenize a share class.
Confirm the security has a linked approval
Navigate to Cap Table → Securities and find the security row. It must have an approval linked with a status of Approved or Locked. If no approval is linked, or if the approval is still pending, minting will be blocked.
Confirm the stakeholder has a wallet address
Open the stakeholder’s profile and verify that a Solana wallet address is saved, or that they have an OASIS avatar linked.
Click Mint on the security row
In the Securities table, click Mint on the row for the security you want to tokenize. Launchboard sends the tokens to the stakeholder’s wallet and records the transaction hash on the security.
Verify the mint succeeded
A success notification will appear. The security record is updated with an on-chain transaction hash (visible in the security details). Copy that hash and paste it into the Solana explorer to confirm the tokens arrived.
Vesting and minting
When a security has a vesting schedule, Launchboard does not mint the full grant quantity upfront.- Initial mint — only the cliff amount or the currently-vested quantity is minted at the time you click Mint.
- Ongoing vesting — as additional shares vest, Launchboard mints the newly vested tokens automatically on a daily basis. You do not need to trigger these subsequent mints manually.
- Tracking — the security record keeps a running count of how many tokens have been minted so far. You can see this in the security details.
The Issue Shares and Issue Options paths, and Tokenize from Document, mint the full quantity immediately regardless of vesting terms. Vesting-aware minting applies only to the Securities table → Mint path.
Verifying an on-chain mint
After a successful mint, Launchboard stores a transaction hash on the security record. To verify:- Open the security in Cap Table → Securities and copy the transaction hash.
- Go to explorer.solana.com (switch to the correct cluster — devnet or mainnet — depending on your organization’s setup).
- Paste the transaction hash into the search bar to see the on-chain record.