FAQ
Clear, technical answers about WWW, the AutoBalancing Market Maker, and the burn constraint. All parameters should be verified on-chain.
What is World White Whale (WWW)?
WWW is a Pump.fun-native Solana token built as an execution system: an AutoBalancing Market Maker funded by Pump.fun creator rewards, designed to maintain structured activity from pre-bonding through post-bonding with strict concentration limits and on-chain transparency.
What is the core vision of WWW?
The vision is to convert creator rewards into a disciplined execution budget that can operate continuously. Instead of relying on one-time liquidity or short-lived attention, WWW is designed as a lifecycle-aware engine that supports structure, measurable activity, and transparent rule-based operations over time.
How does the Market Maker operate at a high level?
The Market Maker runs band-based rebalancing and inventory control. In weakness it prioritizes balance restoration within budget; in neutral conditions it minimizes intervention; in strength it reduces inventory risk to keep exposure bounded. Actions are evaluated on a cadence with cooldowns to avoid churn.
What does AutoBalance mean in WWW?
AutoBalance is the rule set that keeps the Market Maker operational without becoming a passive mega-holder. It manages inventory targets, preserves reserves, and executes within a defined budget so the system can sustain longer-term operations rather than overextending in a single phase.
What is the 3% rule and why does it exist?
The 3% rule is a hard cap on Market Maker wallet concentration. If the MM wallet holds more than 3% of total supply, the excess portion is designated for burn. This constraint prevents silent accumulation, strengthens credibility, and keeps the MM wallet as an operational tool rather than the narrative.
What exactly gets burned?
Only the excess inventory above the 3% cap in the Market Maker wallet is intended to be burned. The goal is to keep the wallet functional for operations while enforcing a strict upper bound on its long-term token concentration.
How are Pump.fun creator rewards used?
Creator rewards are treated as renewable execution fuel. They can be allocated to rebalancing and lifecycle support while preserving reserves. Over time, this creates a feedback loop where reward inflows fund systematic operations rather than depending purely on external injections.
Does WWW work pre-bonding and post-bonding?
Yes. WWW is designed to be lifecycle-aware: it targets controlled participation during pre-bonding and continues systematic operations post-bonding when typical meme flow weakens. The objective is resilient behavior across changing liquidity conditions, not only the launch window.
Is the Creator / Rewards wallet the same as the Market Maker wallet?
No. The Creator / Rewards wallet is intended for reward receipts and treasury accounting. The Market Maker wallet is the operational execution wallet with strict concentration constraints. Separating these roles improves transparency and limits operational risk.
What are the key transparency metrics WWW aims to publish?
Key metrics include: Market Maker holdings as a percentage of supply, burn TXIDs and burned amounts, creator reward inflow traces, and time-stamped summaries of rebalancing activity. These outputs make the system auditable and reduce reliance on trust.
How can I verify burns and wallet behavior on-chain?
Use Solana explorers to inspect the Market Maker wallet, burn transactions (TXIDs), and token supply changes. The project’s Links page should provide verified URLs to the mint (CA), official wallets, and relevant explorers or dashboards.
What makes WWW different from typical meme tokens?
WWW is positioned as a rule-based execution engine rather than a one-phase meme cycle. It focuses on measurable mechanics: reward-funded operations, band-based rebalancing, strict wallet concentration caps, and transparent burn reporting.
Is this financial advice?
No. This website is documentation only and does not provide investment advice. Always verify information on-chain and perform your own research.
Quick note on the 3% constraint
Whenever referencing the cap in documentation, prefer explicit phrasing like “MM holdings must remain at or below 3%” or use JSX-safe formatting such as { > } when needed in code to avoid build issues.