Launching on pump.fun
What happens at each stage of a real creation-only launch, from preparation to Solana confirmation.
7 sections / hugpad handbook
On this page
Before preparation
The form needs a valid Hugging Face session, an eligible public repository, a connected Solana wallet, and complete token details. The launch page checks a mainnet connection and public media storage. Passing these checks does not guarantee a transaction will succeed.
The transaction lifecycle
- 1
Recheck repository access
The server verifies your Hugging Face identity and namespace permissions. Browser claims alone cannot authorize the launch. - 2
Upload public media
The image and metadata are stored in Lovable Cloud and checked for public reachability. The future mint address determines the fixed website URL. - 3
Build a creation-only transaction
The official pump.fun SDK constructs a create_v2 instruction. No initial buy is included. Mint signing happens locally, and your wallet remains responsible for the payer signature. - 4
Simulate and estimate
The transaction is simulated against Solana mainnet. Preparation stops if simulation fails or the debit cannot be verified. The preview shows the estimated SOL debit and mint address. - 5
Request wallet approval
You review and sign the transaction in your connected wallet. hugpad checks that the message has not changed and that required signatures are present. - 6
Record, broadcast, and confirm
The transaction signature is recorded before broadcast for recovery. hugpad submits the signed transaction, then checks its status. Only an error-free confirmed or finalized result is reported as success.
Understand the estimated SOL debit
The preview estimate is derived from the simulated payer-balance change and a verified fee. It includes account funding and the network fee; it is not just the cost of signing. There is no fixed SOL price promised in these docs.
Network state and fees can change. Ensure the payer wallet has enough SOL, verify the request in the wallet, and do not treat a simulation as a guarantee of final execution.
No initial buy
Create only, no dev buy
Read the launch state correctly
| State | Meaning and action |
|---|---|
| Prepared | The transaction was simulated. No token has been created; review, cancel, or approve. |
| Wallet approval | Signing is requested. Reject it if the details or payer are not what you expect. |
| Signed / confirmation pending | A signature is known, but confirmation is not yet established. Check the existing transaction. |
| Confirmed on Solana | The recorded transaction is confirmed or finalized without an execution error. |
| Failed | An error was reported. Inspect the reason and existing transaction before deciding what to do next. |
| Confirmation unknown | Do not start another launch. Use Check confirmation and Solscan to resolve the recorded transaction. |
After a confirmed launch
The form provides transaction and pump.fun links. The token’s metadata website is https://hugpad.co/<mint address>. After confirmation, the server verifies the official creation, mint, wallet, and metadata against the saved launch record, then publishes a coin page and directory listing.
If the transaction is confirmed but saving the listing fails, use Retry publishing rather than launching again. An unlisted or unconfirmed mint does not receive a coin page. Admin-linked coins do not imply repository ownership or creator endorsement. No trading prices, liquidity, or rankings are invented.
What launch checks cannot guarantee
Ownership checks, simulation, and wallet verification reduce specific risks; they do not prevent every network failure, assess an investment, or guarantee market activity. The flow is implemented, but a funded real-wallet launch has not yet been verified end to end. Review security and safety and recovery guidance before signing.