Security & safety
Wallet safeguards, public uploads, sign-in sessions, and the risks that remain outside hugpad’s control.
7 sections / hugpad handbook
On this page
Your wallet keys stay in your wallet
hugpad asks your wallet to sign; it does not ask for your seed phrase or private key. The payer must match the wallet used for preparation, the signed message must remain unchanged, and required signatures must be present before submission.
Inspect every request in your wallet. Reject anything unexpected. A wallet signature is real authorization to use mainnet funds, not a harmless preview.
Transaction boundaries
The launch flow permits a single pump.fun create_v2 operation and allowed compute-budget instructions. An initial buy is not included, and the RPC checks reject transactions outside the allowed structure. Simulation must succeed before signing, but conditions can change between simulation and execution.
Duplicate-launch precautions
The known signature, mint, and model ID are saved in the current browser session before broadcast where session storage is available. This enables the form to recheck a potentially submitted transaction rather than blindly creating another one.
This is a recovery precaution, not an absolute guarantee against duplicates. Storage can be cleared or unavailable. Save the transaction link, resolve pending status first, and do not open another session to retry an uncertain launch.
Hugging Face sign-in sessions
Sign-in uses Hugging Face’s own OAuth page with PKCE. The browser stores the resulting session locally; signing out removes that stored session. Expired or unreadable sessions are treated as signed out.
Use a trusted device and browser. Do not share access tokens or paste them into screenshots, public descriptions, or third-party forms. The server rechecks identity and organization roles for launch operations.
Uploaded media is public
Token pictures and metadata must be publicly readable so token viewers can display them. Do not upload secrets or sensitive personal information. Preparation can upload media before you approve the transaction, and cancelling does not automatically delete those uploads.
Financial and model-use risks
No investment or safety guarantee
When to stop
- The wallet requests something different from the reviewed launch.
- The repository, payer, mint, image, or links are not what you intended.
- The service cannot verify mainnet, public metadata, identity, or transaction simulation.
- A previous transaction is signed but its confirmation is still unknown.
- You are being asked to share a seed phrase or pay an unexplained charge.
