DOCUMENTATION / WHAT PHCREATOR IS
Meet PHCreator
PHCreator is a Solana launchpad that connects pump.fun tokens to PHub fee recipients. Launch a token, designate a personal PHub username, and choose how its creator fees are shared.
The recipient does not need to connect a wallet or register with PHCreator before launch. Their share accumulates in a program-controlled vault. When they claim, PHub login proves their identity and a Solana address receives the SOL.
Three destinations, one fixed split
| Destination | What it does |
|---|
| PHub creator | Receives the required share of creator fees. PHCreator currently requires at least 50%. |
| Buyback + burn | Optionally uses a share to buy that same token and destroy the purchased tokens. |
| Developer | Optionally sends your chosen share to the launch wallet. |
The shares total 100% of creator fees. They do not represent percentages of the token supply or the entire trading volume.
Choose the allocation before launch. Once the sharing configuration is frozen, the recipients and percentages cannot be edited through pump.fun's sharing configuration. Disabling buyback is a choice made before launch.
Start here
What makes a PHCreator launch
Every new token created through PHCreator must have a mint address ending in ph. The suffix is part of the address, not the token symbol.
A token appears as successfully launched only after the service verifies its frozen fee recipients on chain. A logo, ticker, PHub name, or matching address suffix alone does not prove a token is official.
Anyone can designate a PHub username. Being named as a recipient is not an endorsement by that PHub creator.
Current release
The vault and claim service are on Solana mainnet. This release includes the redesigned website, permanently frozen three-way splits, and verified mainnet program fixes. Automatic keeper execution still requires operator activation. The release-status page records deployment evidence and remaining launch steps.
The program remains upgradeable and has not had an independent security audit. A vault has no private key, but that does not remove the program and service trust dependencies.
DOCUMENTATION / HOW IT WORKS
How it works
PHCreator sits between pump.fun's creator-fee mechanism and a PHub identity. At launch, you set a fee-sharing configuration on the token's pump.fun account, pointing a percentage of future creator fees at a PHCreator-controlled vault program instead of a single wallet.
The vault
The vault is a program-derived address, not a wallet with a private key. Fees routed to it accumulate on chain, tagged internally to the PHub username named at launch. Nobody, including PHCreator operators, can move a recipient's balance except through the claim instruction that PHub login authorizes.
The keeper
A keeper process watches for accumulated fees and periodically triggers the buyback-and-burn and developer-payout legs of the split. Keeper runs are logged and the cadence is not guaranteed to be real time — see Release status for current keeper activation state.
The claim flow
When a recipient is ready to withdraw, they sign in to PHCreator with the PHub account matching the username set at launch, then provide a Solana address to receive the balance. No wallet connection or account creation is required before this point.
DOCUMENTATION / USING IT
Launch a token
- Enter the PHub username that should receive creator fees. You don't need their permission or a wallet address from them.
- Set the token name, ticker, image, and description.
- Set the developer share. The buyback + burn share fills the remainder of the non-recipient allocation automatically.
- Review the frozen split in the preview panel — this cannot be changed after launch.
- Connect a Solana wallet and confirm the transaction. PHCreator mints the token with an address ending in
ph and registers the fee-sharing configuration on pump.fun.
Optional dev buy executes in the same transaction as the launch, before public trading opens.
DOCUMENTATION / USING IT
Claim your fees
If you were named as a PHub creator on a PHCreator launch, fees accrue automatically — you don't need to do anything until you want to withdraw.
- Go to the Claim fees tab and sign in with the PHub account that matches the username used at launch.
- PHCreator looks up every token where that username is the frozen recipient and shows the accrued, unclaimed balance for each.
- Provide a Solana address to receive the payout.
- Confirm the claim. Funds leave the vault directly to the address you provided.
Claims can be made at any time and as often as you like; there's no minimum balance.
DOCUMENTATION / FEE SPLITS
Fee splits
Every PHCreator token has exactly one fee-sharing configuration, chosen at launch and frozen permanently. It always allocates 100% of the token's creator fees across up to three destinations.
| Destination | Range |
|---|
| PHub creator | 50%–100%, required |
| Buyback + burn | 0%–50%, optional |
| Developer | 0%–50%, optional |
These percentages apply only to the creator-fee stream pump.fun pays out on trades of that token. They say nothing about token supply, market cap, or overall trading volume — a common point of confusion when people compare a "70% split" to holding 70% of a token.
Platform protocol fees charged by pump.fun itself are separate and are not affected by a PHCreator sharing configuration.
DOCUMENTATION / BUYBACK + BURN
Buyback + burn
If a launch allocates a share to buyback + burn, that share of accrued creator fees is used by the keeper to market-buy the token on pump.fun, then send the purchased tokens to a burn address with no known private key.
Burns are not instant per-trade events. The keeper batches accumulated fees and executes on its own cadence, so there will typically be a delay between fees accruing and a corresponding buy-and-burn transaction appearing on chain.
Disabling buyback + burn at launch is permanent for that token — a later launch can choose differently, but an existing token's configuration cannot be switched on or off after launch.
DOCUMENTATION / REFERENCE
Program & operators
PHCreator consists of an on-chain Solana program (the vault and claim logic) and an off-chain service (PHub login, the keeper, and the website). The two are separable: the program can hold and release funds according to its own rules even if the off-chain service is unavailable, though claiming still requires the service to verify PHub identity.
Operators are the parties with authority to upgrade the program and run the keeper. Operator keys are held separately from any user or recipient funds; operators cannot withdraw a recipient's vault balance to themselves.
Program ID: PHC1acccPlaceholderProgramAddressXXXXXXXXXX (placeholder — replace with the deployed address before publishing).
DOCUMENTATION / REFERENCE
Release status
- Live Vault program deployed to Solana mainnet
- Live Claim service and PHub login
- Live Redesigned website and launch flow
- Live Frozen three-way split, permanent per token
- Pending Automatic keeper execution — currently requires manual operator activation per run
- Pending Independent third-party security audit
This page is updated as deployment steps complete. "Live" means deployed and reachable on mainnet, not audited or risk-free — see Security & trust.
DOCUMENTATION / REFERENCE
Security & trust
The vault holding recipient fees is a program-derived address with no private key, so no single party can sign a transaction to drain it directly. Funds can only move through the program's claim and keeper instructions.
This does not mean the vault is risk-free. The program itself is upgradeable by its operators, which means the rules governing the vault can change in future upgrades. The program has not undergone an independent security audit. The off-chain service that verifies PHub identity is a further trust dependency: if it is unavailable or compromised, claiming can be disrupted even though the underlying funds remain on chain.
Treat PHCreator the way you would any new, unaudited on-chain program: understand that upgrade authority and service uptime are trust assumptions, not guarantees.
DOCUMENTATION / SUPPORT
Questions & troubleshooting
My token isn't showing as verified
Verification only appears once the frozen fee recipients are confirmed on chain, which can lag a few minutes behind the launch transaction. A matching ph address suffix alone doesn't mean a token is verified.
I can't claim — PHub login doesn't match
The PHub account used to log in must match the exact username recorded at launch. If the recipient's username has changed since launch, claiming from the new username won't match the frozen record.
I don't see any accrued fees yet
Fees accrue as the token trades on pump.fun. A brand-new token with little trading volume will show a small or zero balance until it sees activity.
Can I change the split after launch?
No. The sharing configuration is frozen at launch and cannot be edited for that token going forward.