DaoPad documentation
Token launches, community rewards and treasury governance on Solana.
Quick start
- Add a token name, ticker, description and image.
- Choose a supported pair and an optional first buy.
- Select Community Member Rewards or Community-Owned Governance.
- Set the creator share. For governance, also set the voting period and quorum.
- Review the costs and approve the launch transaction in your wallet.
Your creator dashboard shows the token’s launch status, funding and transaction history.
Launch models
Community-Owned Governance
Holders vote on how the launch’s community budget is used. Proposals can cover marketing, development, contributor payments or project direction. Each launch has its own voting configuration and treasury accounting.
Community Member Rewards
The existing holder-reward system tracks recognized buys and retained positions. Eligible holders below their verified entry can share the launch’s funded reward budget. The reward rules remain unchanged under the new name.
Pump.fun integration
DaoPad uses Pump.fun for token creation and trading. The form lists supported quote pairs. An optional first purchase is included in the creation transaction, with tokens delivered to the creator wallet.
Current tracking covers bonding-curve activity. New reward epochs pause at graduation until the migrated market is supported.
Launch setup
The review shows your token details, pair, creator wallet, fee destination, allocation, optional first buy and estimated network costs. The model and allocation are fixed at launch.
After confirmation, DaoPad registers the mint and market. Token creation and tracker registration have separate statuses, so a registration retry uses the existing token.
Fee allocation
The creator share can be set from 0% to 20% of received funding. The selected community model receives 70% to 90%, and the protocol share is 10%.
For Community Member Rewards, the community allocation funds holder distributions. For Community-Owned Governance, it funds the launch’s community budget.
| Destination | Share | Units |
|---|---|---|
| Community model | 80% | 80 |
| Creator | 10% | 10 |
| Protocol | 10% | 10 |
This is an allocation of received creator fees, not an extra trading tax. Pump.fun sets its own trading-fee schedule. A custom trading-fee control is separate from the creator-share slider.
Funding
The worker checks Pump.fun’s per-mint fee-sharing configuration and finalized distribution receipts. It credits each receipt to one launch. Creator deposits use a separate verified funding flow.
The dashboard shows available funding, reserved amounts, pending transactions and confirmed payments. A launch’s budget stays separate from every other token’s budget.
Community Member Rewards
Recognized market buys establish weighted entry. Incoming transfers add no purchase cost basis. Sells or outgoing transfers exclude the wallet for the applicable reward epoch.
At each finalized snapshot, the engine checks the retained position, market price and available funding. Eligible wallets share the funded budget using the existing loss-weighted calculation and caps.
Search a wallet on the token page to see its entry, eligible units, status and previous distributions.
Proposals and voting
The creator opens a proposal with a title, description and decision type. Voting uses balances at a fixed finalized snapshot. Moving tokens after that snapshot does not create additional voting power for the same proposal.
Marketing budget
Request a defined amount for a campaign.
Contributor payment
Specify the recipient wallet, asset and amount.
Project direction
Vote on a development or community priority.
Each eligible wallet casts one token-weighted yes, no or abstain vote. The launch’s quorum and voting period determine the result. Vote totals and proposal status appear on the token page.
Treasury spending
A spending proposal fixes the recipient, asset and amount before voting. After passage, the current flow requires creator authorization and a treasury-wallet signature. Completed payments link to their transactions.
Governance directs the community budget, not the token’s mint authority. Automatic recurring treasury actions are not enabled in this release.
Transaction history
Each token’s history includes funding receipts, reward snapshots, allocations, payouts and treasury payments. Open a transaction link to view its network confirmation.
The homepage proposal is an illustrative preview. Real proposals and payments appear on their token pages.
Transaction recovery
After a refresh or timeout, the site checks the saved transaction reference and resumes the existing launch. Partial payouts continue from their remaining batches after the worker verifies earlier transactions.
Wallet roles
- Creator
- Approves token creation and receives the configured creator share.
- Operator
- Runs indexing, fee collection and the configured reward pipeline with launch-scoped accounting.
- Treasury signer
- Approves treasury transactions for the relevant launch.
Launch availability appears in the form. Current operational status and transaction details remain separate from this guide.