FAUCET DOCS

FAUCET is a community powered launchpad built on top of Pump.fun. Launches routed through FAUCET generate protocol fees. Those fees accumulate in the FAUCET treasury. Every 24 hours the community votes on which eligible FAUCET launch receives the next round allocation.

FAUCET is independent and is not the official Pump.fun team. Nothing in this protocol promises price appreciation, returns or profits.

Launches are created through the Pump.fun creation path behind the FAUCET launch adapter. The adapter is configured with an endpoint and credentials held server side. When no endpoint is configured the launch flow runs in demo mode and clearly states that no chain transaction occurred.

• Token must be created through the FAUCET launch flow on Pump.fun.
• Token must still be tradable and not migrated away from the FAUCET registry.
• Token must meet the minimum market cap threshold published for the round.
• Metadata must include a name, ticker, image and at least one verified link.
• Tokens flagged for impersonation or duplicated metadata are removed.

Each voting window runs for 24 hours and closes at the top of the window. Wallets may cast 1 vote per round. At close, the token with the highest aggregate voting power is selected for the next round.

Voting power is computed from the connected wallet's FAUCET balance. The active model is balance-sqrt, with a minimum balance of 1,000 FAUCET, a denominator of 10,000 FAUCET per unit of power and a hard cap of 250 power per wallet.

The formula lives in a single configuration module so it can be replaced without touching the interface. Snapshot rules and anti sybil measures: To be finalized

The treasury holds protocol fees and returned round fees. Balances, allocations and every transaction are published on the treasury page with explorer links.

Treasury wallet address: FAUCETNrTHwn8zbvRvmTz8uqBKpWvvrVQGEDJ1vqv3Dw

A round begins when a winner is selected and runs for 24 hours. The allocation for the round is disclosed before the round begins. Round parameters including repeat win rules: To be finalized

Exact fee percentages and the split between treasury and operations: To be finalized

Round allocations are deployed by an authorized server side execution service. No signing key, treasury credential or execution authority exists in this frontend.

Strategy parameters, venue list, size limits and pacing rules: To be finalized

Every treasury movement is published with a transaction signature. Round allocations, deployed amounts and fees returned are shown on the live faucet page while a round is running, and remain visible in the token page history afterwards.

Program identifiers, the FAUCET mint and audited deployment addresses: To be finalized

FAUCET never asks for seed phrases or private keys. Wallet connections are read only until you explicitly approve an action in your wallet.

Audit reports and disclosure process: To be finalized

Frequently asked questions are answered on the How It Works page, including what turning on the faucet means, how the winner is selected and where treasury transactions are published.