Start here
Foundations
Product map, glossary, protocol overview, and the minimum context needed before reading launch or trading sections.
Reading progress
Navigate this topic
Current section
Overview
Reading mode
Focused route with anchored sections
Quick section jump
Within this topic
Start here
Overview
What DogeFactory is, what this page documents, and how to interpret current public behavior.
DogeFactory groups several DeFi surfaces in one place: token launch, swap, liquidity, farming, staking, and a wallet-centric user view. That does not mean every page is equally complete or depends on the same services. Some screens can read live network state, while others still depend more on supporting services or current availability settings.
What DogeFactory is
DogeFactory is a DogeOS-native DeFi suite that groups token launches, DEX routing, liquidity provisioning, farming, staking, and a wallet-centric activity view into one app.
What this page tries to do
This documentation is meant to be a compact operational reference. It prioritizes plain definitions, real behavior, limits, risks, and user decisions over marketing language.
How to read the launch sections
The launch sections distinguish between the single active fixed-price market-sale path and the parallel bonding-curve path, because they do not create the same user expectations.
Start here
How to use the docs
How the docs hub and full reference differ, how chapters are organized, and how search should be used.
Use the Docs Hub as the fast entry point, then switch to the Full Reference when you need denser rules, exact terminology, or a stable section anchor for support and product review.
Docs Hub
Use the hub for overview, product map, quick paths, and short explanations before a wallet action or a deeper review.
Focused guides
Topic routes stay useful when you want a shorter chapter-specific read without scanning the full reference.
Full Reference
Use the full reference for dense product and protocol behavior, search by chapter, and deeper caveats.
Focused topic guides
Use the topic routes when you want a shorter, structured read instead of scanning the full reference page.
One-page reference
Use the full reference when you need search, a complete table of contents, and every section on one route.
Old links preserved
Old links such as /docs#bonding-curve are automatically redirected to the correct topic page, so existing references stay usable.
Chapter structure
Start here
Start with the product overview, then use the docs guide and glossary to understand how the rest of the reference is organized.
Launchpad
Compare launch paths, sale end states, refunds, sell-back, and the settings that most affect user outcomes.
Trading
See how swaps find a path, what slippage means, what minimum received protects, and why a transaction can fail.
Pools & Liquidity
Review how users add or remove liquidity, what LP exposure means, and why a pool can still block an action.
Earn
Understand rewards, claiming, withdrawals, and why APR can be missing or only approximate.
Wallet
Review portfolio context, wallet activity, launch participation, and why some tokens stay outside the main portfolio list by default.
Safety & Risk
Keep labels, approvals, token warnings, and admin routing decisions clear in plain language before any action.
Data & Indexing
See where token lists and market panels get their public data, how known deployments stay visible, what the app caches in the browser, and why updates can lag.
Protocol Reference
Stay at the public level: what the app does on-chain, which fees matter, and how paused or degraded states affect users.
FAQ
Quick answers to the most common user questions about launches, trading, wallet states, and basic safety signals.
Product map
Site surfaces
Definition, utility, main advantage, and main limit of each public page.
The table below is deliberately operational. It focuses on what each public surface is for, what it does well, and where its main limitation or risk sits.
| Surface | Definition | Utility | Main advantage | Main limit or risk |
|---|---|---|---|---|
| Launch | Initial token distribution through a fixed-price sale or, in some flows, a bonding curve. | Bootstrap supply distribution and seed the first DEX market. | Rules can be published and inspected before users commit funds. | A mathematically correct launch can still be economically unfair if the price or caps are badly set. |
| Swap | Token exchange through the live pool graph and the router. | Give holders a secondary market after launch and allow normal DEX trading. | Auto-best route can choose direct or multi-hop execution across live pools. | No route, shallow liquidity, or large size can still make a trade fail or become unattractive. |
| Pools | Liquidity provisioning into canonical live pools. | Create markets, deepen liquidity, and earn swap fees. | The app distinguishes clearly between opening a new pool and joining an existing one. | The first LP sets the initial price, so a bad ratio can create an objectively bad market from block one. |
| Farm | LP rewards through the current public reward path, with older reward modes only when explicitly enabled. | Incentivize selected liquidity pools and deepen market depth. | Reward cards separate current and older reward modes and show the action users are approving. | Displayed APR can deteriorate quickly and the page still depends on available reward and discovery data. |
| Staking | Single-token staking pools that distribute rewards over a configured duration. | Reward holders without LP exposure. | Withdrawals remain available after rewards stop, which is operationally simpler than locking principal past period end. | High displayed APR on low TVL can look attractive while remaining economically thin or unstable. |
| Analytics | Protocol and market discovery view for TVL, volume, top pools, trending tokens, launches, and dormant pools. | Help users scan where attention, liquidity, and recent activity are concentrated. | Custom liquidity floors reduce noise from dead or too-thin markets and degraded states make stale data easier to spot. | Discovery scores use the best available data; missing windows, missing buy/sell splits, or stale indexing can still make figures incomplete. |
| Wallet | Connected-wallet hub with Overview, Portfolio, Activity, Launches, LP, Farms, and Staking tabs for the connected address. | Centralize user-specific activity and actions in one place. | Reduces navigation friction by reusing the same data modules already exposed in other surfaces. | It does not bypass data dependencies; if farm or staking discovery is incomplete elsewhere, the wallet view inherits the same gaps. |
Glossary
Definitions
Short objective definitions for the terms used across the app and docs.
Fixed-price sale
A launch mode where the live sale keeps one published price per token, buy and sell stay open during the sale window, and settlement happens through an explicit final state rather than a moving quote.
Bonding curve
A launch mode where the price changes as more of the sale allocation is sold. In DogeFactory documentation, the curve path is a live market before migration, not just a presale counter.
Migration
The move from launch mode into a DEX pool. On the curve path, migration moves reserve and remaining token inventory into the pool and burns the launch LP.
Near migration
A Launches counter for curve launches that are close to migration. In the current UI, a curve is counted as near migration from 75% progress. It is a warning light, not proof that migration already happened.
Deployment
One installed version of the DogeFactory contracts on a network. A new deployment can create new tokens while existing known deployments can still have tokens or pools that users already hold.
Deployment registry
The app list that remembers which DogeFactory deployment created a token or pool. It helps the interface keep known launches visible after a reboot or redeploy.
Slippage
The worst extra movement a user accepts before the transaction fails. It is separate from price impact.
Price impact
The price move caused by the size of the trade relative to available liquidity. A low slippage setting does not remove price impact; it only caps tolerated execution drift.
Pool
The market connecting two assets on the DEX. Without a live pool or route, a token can still exist in search while remaining unswappable.
Wallet cap
A maximum accepted contribution per wallet during a sale. It reduces direct concentration but does not stop multi-wallet behavior on its own.
Verified
A review or data label inside the app. It is not an independent review, not a guarantee of legitimacy, and not a promise that liquidity is safe.
Data service
A supporting service used by fast pages such as Analytics, Wallet, Tokens, and Pools. If it lags, the network can be correct while the page is late.
Extra tokens
Wallet tokens kept out of the main Portfolio list by default to keep the view readable. This can include test tokens or tokens that need more DogeFactory context. They are still in the wallet; the toggle only changes what the table shows.
Needs context
A Wallet portfolio grouping for assets that need a little more explanation before they look like normal priced holdings. It can include locked sale tokens, demo/test tokens, or assets without reliable price or route context yet. It is not an accusation and it does not mean the asset is invalid or gone from the wallet.
Farm reward path
The current farming path for eligible liquidity positions. Older reward modes are separate and should appear only when explicitly enabled.
Signed order
A limit order signed in the wallet and later executed only if the visible terms still hold. Expiry, network, recipient, amount, and minimum output should match what the user approved.
On-chain basics
Protocol Overview
A high-level explanation of DogeFactory on-chain actions, wallet checks, and the boundary between public user guidance and private operational documentation.
DogeFactory uses on-chain execution for swaps, launches, liquidity, rewards, and selected protocol actions. This section gives users a high-level view of what happens on-chain without exposing internal operational details.
Within this section
Protocol basics
Get a high-level view of what users trigger on-chain when they use the app.
| Area | What users do | Wallet check | Public documentation scope |
|---|---|---|---|
| Swaps and liquidity | Users confirm token pair, amount, fee tier, slippage, recipient, and deadline before execution. | The wallet preview should match the page: network, token, amount, minimum received, recipient, and fee. | Public docs explain the user-facing flow and the checks to perform before signing. |
| Launchpad | Creators and participants confirm sale type, token, amount, fee, recipient, lifecycle state, and settlement preview. | The page and wallet should agree before a launch, buy, sell-back, claim, refund, or migration action. | Public docs describe launch behavior and participant checks, not internal operational procedures. |
| Limit orders | Users define trade terms up front and confirm expiry, recipient, input amount, minimum output, network, and cancellation behavior. | The wallet confirmation should be readable enough for users to compare it with the order form. | Public docs focus on safe signing, status visibility, and how to stop when the terms are unclear. |
| Rewards | Users deposit, withdraw, claim, or exit while checking deposit token, reward token, APR source, and withdrawal behavior. | Approvals and reward actions should be clearly tied to the visible farm or staking surface. | Public docs explain reward behavior, degraded states, and user exits at a high level. |
| Public vs private scope | Users rely on official DogeFactory surfaces and should not follow unofficial links or pasted destinations. | If the wallet preview, network, token, recipient, or amount looks inconsistent, users should not sign. | Internal operational material stays private. |
Emergency states and limits
Understand the public limits of the app when parts of the product are paused or degraded.