01 · Overview
What Z COLONY does
Z COLONY connects a Pump.fun launch to a recurring growth process: creator fees fund fresh anonymous wallets that buy the coin and lock every purchase. It keeps every token isolated and treats Solana as the source of truth for launches, balances, holders and transaction confirmation.
Launch
Create a Pump.fun token from Z COLONY and confirm the launch transaction with Phantom.
Route
A dedicated colony wallet receives the coin’s creator fees without mixing funds between launches.
Lock
Creator fees fund fresh anonymous wallets that continuously buy the coin — every purchase is locked forever.
02 · Quick start
Before you launch
Prepare the wallet and metadata first. Z COLONY validates the critical inputs before asking Phantom to sign.
Phantom
Install Phantom, unlock it and switch to the wallet that will create the token.
Enough SOL
Keep enough SOL for the launch, optional initial buy, network fees and fee-routing account rent.
Token artwork
Use a supported image under 5 MB and prepare concise public metadata.
Locked supply
Every colony purchase is locked forever — no configuration needed.
03 · Token launch
Complete the launch form
The launch screen prepares Pump.fun metadata and builds the transactions for the connected Phantom wallet.
The growth engine
After launch, Z COLONY routes the coin’s creator fees into its own colony. Fresh anonymous wallets continuously buy the coin through live Jupiter routes, and every purchase is locked forever. Nothing needs to be configured — the engine starts once fee routing is confirmed on-chain.
Fee routing is confirmed on-chain and the growth engine is buying and locking supply.
Waiting for the fee-routing configuration or its on-chain confirmation before the engine starts.
What Phantom signs
- 01Launch transaction
Creates the token through Pump.fun using the metadata and optional initial buy.
- 02Fee-routing transaction
Sets the Z COLONY platform wallet as the coin's creator fee recipient on-chain. The recipient is fixed by the platform and cannot be edited at launch; Z COLONY reads it back from the chain before activating the token.
04 · Growth engine
How the colony grows your coin
The engine checks active launches on a recurring cycle. It never acts on quoted amounts: only tokens actually received after a confirmed swap can become colony buys.
Read the dedicated colony wallet’s live SOL balance and reserve enough SOL for operating fees.
Fix one Solana slot, read the coin’s holders at that slot and exclude technical or configured accounts.
Request a current SOL route for the colony’s buy and enforce configured slippage and price-impact limits.
Sign with the isolated colony wallet, save the signature before broadcast and wait for chain confirmation.
Compare the token account balance and use only the amount that actually arrived.
Calculate each colony purchase from the fixed snapshot, using integer token amounts.
Execute the colony buys on-chain, lock the purchased tokens and confirm each transaction.
Slot-pinned
One holder state for the entire round.
Idempotent
A holder payout cannot be duplicated within a round.
Retry-safe
Failed transfers retry without repeating confirmed ones.
05 · Status reference
Read the current state
Statuses describe confirmed progress, not optimistic UI. A launch becomes active only after its required on-chain configuration matches the expected route.
Token statuses
Launch and fee routing are confirmed.
Waiting for fee configuration or confirmation.
A required launch stage did not complete.
Round statuses
- snapshotting
- Holder balances are being read at one fixed Solana slot.
- swapping
- A live Jupiter route is being checked and the fee swap is being prepared.
- verifying_receipt
- The swap is confirmed; Z COLONY is checking the actual token amount received.
- distributing
- Colony purchases are being executed and locked on-chain.
- completed
- All available purchases are resolved; any exhausted failures remain visible.
- swap_failed
- The swap could not be safely completed. No colony buy is created from an unconfirmed swap.
- token_receipt_failed
- The expected tokens were not observed after the swap.
Payout statuses
pending waits to be sent; processing has a recorded transaction; retrying will be attempted again; confirmed is final for Z COLONY; and failed exhausted automatic retries.
06 · Tracking
Dashboard and token pages
Connect the same Phantom address to view your launches. Public token pages expose the chain-backed colony route and activity for each mint.
For creators
- Tokens launched by the connected wallet
- Dedicated colony wallet balance
- Colony activity and token status
- Completed growth rounds and transactions
For holders
- Growth rounds executed for your coin
- Colony buys locked on-chain
- Confirmed, retrying or failed state
- Transaction link for independent verification
07 · Security model
Designed around verifiable state
Z COLONY separates signing responsibilities, isolates colony funds per launch and checks chain results before progressing to the next state.
Chain-confirmed activation
Database records do not make a token active. The expected fee-routing state must be readable on Solana.
Phantom launch authority
The creator approves user-owned launch actions in Phantom. Z COLONY never asks for a wallet seed phrase or private key.
Isolated colony wallets
Every token has a separate server-managed colony wallet. Public pages expose only its address and balances.
Confirmed-data reporting
Balances, holders, swaps and buys come from chain reads and confirmed transaction records, never mock figures.
Blockchain transactions are irreversible. Always verify the connected wallet, token mint and Phantom transaction details before approving.
08 · Troubleshooting
Common launch and growth issues
Most blocked actions are deliberate safety checks. Resolve the underlying balance, route or confirmation issue before trying again.
Phantom is not connected
Unlock Phantom, select the intended wallet and connect it from the Z COLONY header.
Growth engine is not buying
The token must be active and fee routing confirmed on-chain; the colony wallet must also cover operating fees.
Launch transaction is not confirmed
Leave the page open while Solana confirms the signature. If Phantom shows a failed transaction, inspect its network error before retrying.
Fee configuration is blocked
The creator wallet may need more SOL for network fees and account rent. The token remains pending until the second Phantom approval is confirmed.
No growth round starts
The token must be active, the engine must be running, no previous round can be open and the colony wallet must cover the swap plus operating fees.
A round shows fewer buys than expected
The round may have hit a failed swap that retries automatically, or calculated amounts may round to zero.
09 · FAQ
Frequently asked questions
Short answers to the most important questions about eligibility, timing and transaction safety.
Do I need to do anything after launching?
No. Once the launch and fee routing are confirmed on-chain, the colony runs on its own — new anonymous wallets keep buying and locking your coin automatically.
What does the colony buy?
The colony’s wallets buy your launched coin itself, using collected creator fees. Every purchase is locked permanently on-chain.
When is a token shown as active?
Only after the launch and fee-routing configuration have both been confirmed on-chain.
Are balances or holder counts simulated?
No. Z COLONY reads chain state and records confirmed transactions. Empty activity is shown as zero rather than replaced with sample data.
Can funds from different tokens be mixed?
No. Every launch has a separate colony wallet, configuration, rounds and payout records.
What happens when a purchase fails?
It enters a retry state. Confirmed transfers are never sent twice, and exhausted failures remain visible for investigation.
Ready to start?
Launch a coin that grows itself.
Connect Phantom, approve the on-chain launch and let the colony take over.