Execution
Trading and pools
How tokens appear, how routes and limit orders work, where slippage applies, and what pool creation really means.
Reading progress
Navigate this topic
Current section
Token sourcing
Reading mode
Focused route with anchored sections
Quick section jump
Within this topic
Data sources
Token sourcing
Where visible tokens come from, how known deployments stay visible, why some data is delayed, and how search behaves.
The token picker combines a small deployment starter list with public data services. That keeps the app usable when live indexing is late, but it also means visibility is not the same thing as a live market.
Token sourcing
Learn where the visible token list comes from before a market is fully live.
Deployment base
DOGE is available from the deployed app configuration. The starter watchlist also adds USDT, USDC, USD1, WETH, WBTC, TDOGE, and TUSD so the list does not start empty when live data is not ready.
Public data
The frontend then requests public token data. If fresh data is unavailable, the interface can show delayed or partial results instead of inventing token states.
Launch tokens
Tokens created through the launcher are discovered from creation events and active-token lists. If they are migrated, they can get LIVE status. Otherwise they can stay visible as CURVE while not yet being swappable on the DEX.
Routing gate
Discovery is not the same thing as approval. Reviewed candidates can appear earlier in the public list, but live markets still rely on the current visible routing state before public liquidity actions.
Known deployments
Understand how DogeFactory keeps known tokens and pools visible across contract generations.
Version tracking in plain words
- A deployment is one installed version of DogeFactory contracts on one network.
- A new deployment can become the active version for new launches, while existing tokens and pools can remain available on the network.
- The deployment registry is the app list that remembers which deployment each launch or pool belongs to.
- This prevents a reboot or redeploy from making existing launches look lost just because the active contract version changed.
- Version labels are handled by the app. Users only need the visible status shown on the page.
| Label | Plain meaning | What it does not mean |
|---|---|---|
| Trusted | The token has an official or curated DogeFactory trust mark. | It is not a promise of profit, deep liquidity, or independent safety review. It only means DogeFactory has recorded a clearer context label. |
| Verified | The token is known through the current approved app path or a reviewed data source. | It is not a promise of profit, deep liquidity, or independent safety review. |
| Needs context | The app can see the token, but some price, route, sale, or trust details still need a clearer explanation. | It is not a ban and it does not mean the asset is invalid. It is a context label before users take action. |
| External | The token or pool is known outside the normal core launch path. | External context does not make it endorsed automatically. A token can exist on the network without being trusted by DogeFactory. |
| Watchlist | The token is visible for follow-up review. | Watchlist visibility is not endorsement and should not be treated as a trading recommendation. |
| Blocked | A critical risk was detected or recorded, so the public app should block swaps and new liquidity actions. | The token can still exist on the blockchain network, but the UI should not encourage users into it. |
| Live | The token has live DEX liquidity or an executable market path in the app. | It does not guarantee good depth, good price, or a safe exit. |
| Curve | The token is still in bonding-curve launch mode and may be visible before normal DEX trading. | It does not mean the token is already swappable through the public DEX route. |
Missing or delayed data
Know why a token may still be missing even when the app is working as designed.
Display order
- Core assets are kept near the top: DOGE, WDOGE, USDT, USDC, USD1, WETH, WBTC, TDOGE, and TUSD when they are configured for the current network.
- A connected wallet can move tokens with a positive balance higher while the selector is open.
- Known liquid markets and useful liquidity context rank higher than a token that is only visible because it was created or discovered.
- Recently selected tokens are remembered in this browser, but sold-out or old entries lose priority over time.
- DogeFactory-origin alone is not enough to dominate the list; action status, route context, and wallet relevance matter more.
- Blocked tokens and browser-only cached launch entries stay lower unless the user searches for them directly.
Why a token may be missing
- The token is not in the deployment watchlist and the public token service is not responding.
- The address is not a contract on the selected network.
- The contract exists, but the app cannot read basic token fields clearly.
- The token was created recently but public discovery has not picked it up yet.
- The frontend loads a bounded result set per refresh.
- A pool may exist without usable liquidity, or the route may be unavailable because of stale data or a blacklist rule.
- External metadata can be late or unavailable; the app may reuse the last known display snapshot when it has one.
- The token belongs to a known deployment that has not been attached to the deployment registry yet.
- Explorer enrichment may ignore very small entries and de-duplicate symbols by keeping the version with more holders.
Search and browser cache
See how search works with the starter list, aliases, and cached public data.
Search, aliases, and team labels
Token search filters the already loaded list in the browser by symbol, name, public identifier, alias, and team. In practice, an alias or team name only works if that metadata is already present in the public list.
Pasting a contract address is different: the app checks the selected network directly. If the address is a readable token contract, it can be selected as an unreviewed token; routing still depends on pool, liquidity, and support state.
For display metadata, DogeFactory can keep a last-known-good snapshot in the browser. That prevents a temporary external metadata outage from making a known token look empty, but it does not change route or risk status.
Public execution
Swap
How public swap routing works, what LIVE and CURVE mean, and why no route can happen.
The public DogeFactory swap defaults to Auto best. It searches available live paths and can pick the best executable quote at quote time.
Within this section
How routing chooses a path
Understand how the app chooses a public swap path without exposing hidden technical detail.
Token search
Users choose two tokens from the merged list. A token can be visible without being swappable if it is still in CURVE phase or simply lacks a live route.
Route
Auto best checks available live paths. Manual mode only exposes direct fee tiers that are live for the selected pair.
A token or pool can exist on the network without carrying a DogeFactory trust mark. If liquidity, index freshness, runtime checks, or token policy fail, the public swap stays unavailable.
In practical terms, routing is open for live non-blocked paths, while endorsement stays separate.
DOGE and WDOGE
When users swap with DOGE, the router wraps and unwraps through WDOGE in the background. The interface still uses the DOGE label to keep the UX simpler.
Quotes and minimum received
Review how quotes, minimum received, and price-impact warnings work together.
Important points
- The token search filters by symbol, name, public identifier, alias, and team, but only inside the list already loaded.
- The LIVE badge means the token is already backed by live DEX liquidity. The CURVE badge means the token exists but is not live in the public swap yet.
- A token or pool can exist on the network without being endorsed by DogeFactory.
- A token can exist on the network without carrying a DogeFactory trust mark.
- Public swaps use live non-blocked paths when liquidity, fee tier, index freshness, and runtime checks pass.
- Launch and token surfaces show user-action status, not a public ranking of contract generations.
- The VERIFIED badge reflects an indexed or curated source in the app. NEEDS CONTEXT means the app still needs a clearer price, route, sale, or trust explanation.
- Auto best can use direct or indirect routes when that improves the quote.
- The standard pool fee tier is 0.30%, with 0.01%, 0.05%, and 1.00% tiers also available for suitable pairs.
- If a token has non-standard transfer behavior, quotes and execution can still fail.
Why a swap can fail
See the most common public reasons a swap is blocked or reverts.
No route available
This message means no live executable path was found for the current trade. It should not be read as a verdict on the token itself. The most common causes are a token still in CURVE phase, a launch warmup delay, or simply no liquid path yet through the currently live pools.
Execution protection
Slippage
Why swap slippage and liquidity slippage are different and what they do not protect against.
The word slippage covers two different behaviors in DogeFactory. They do not serve the same role and they do not protect against the same risk.
Within this section
Slippage basics
See what slippage protects and what it does not protect.
Swap slippage
Swap calculates a minimum received amount from the visible quote and the selected tolerance. If final execution falls below that minimum, the transaction reverts instead of filling at a worse price.
Example: at 0.70% price impact, the quote is already about 0.70% worse than the marginal pool price for that size. Slippage is an extra execution tolerance on top of that quote, not the quote impact itself.
In the current interface, swap allows a broad manual setting up to 20% and asks for extra confirmation from 7.5%.
Liquidity slippage
Add Liquidity calculates amount minimums from entered amounts. On an existing pool, that protects users against a reserve ratio that changed before mining.
The transaction may therefore use less of one side than the user entered in order to stay aligned with the real pool ratio, without taking more than necessary.
Add Liquidity supports custom tolerance up to 20% for thin pools that keep reverting after fast swaps, with a warning from 7.5%.
Price impact
Understand the difference between slippage settings and real market impact.
Pools
Add Liquidity / Pools
Existing pools, new pools, wallet balances, initial price setting, and rejection reasons.
Within this section
Add or remove liquidity
Understand how the app handles existing pools and first-time pool creation.
When the pool already exists
The page resolves whether a live pool already exists before asking users to sign. Standard tiers stay available for creation, but the form also shows which fee tiers are already live so existing pools are not confused with defaults.
When users create a new pool
The page makes it clear that the first LP is setting the initial price, shows the direct and reverse prices computed from entered amounts, and asks for explicit confirmation before sending the transaction.
What the page actually does
- The page first checks whether the selected pair has a usable live market.
- Before wallet confirmation, the page checks whether the selected assets are explicitly blocked and whether the selected action can be explained clearly.
- An existing pool does not automatically become endorsed. The app still needs enough live liquidity and a non-blocked policy state before offering swaps as normal.
- The default pool fee tier is 0.30%. The standard alternatives are 0.01%, 0.05%, and 1.00%; custom fees are advanced settings.
- If a seeded pool already exists, the page shows the live pool state and a link to the active pool.
- If no seeded pool exists yet, the interface can guide the user through first liquidity in the same flow.
- On an existing pool, the transaction may use less of one side to match the current reserve ratio.
- On a new pool, the router uses exactly the amounts you entered to set the first ratio. Slippage does not correct a bad initial price.
- The Pools list can show degraded states when public market data is delayed.
LP risks
Review the user-facing risks of setting price, holding LP, or joining shallow pools.
Displayed wallet balances
- The Add Liquidity page shows an Available balance for each side.
- When you use DOGE, the shown balance is the wallet native balance. For other assets, the balance comes from the ERC-20 token.
- The Max button fills the input with the available balance for that token.
- If the entered amount is above the wallet balance, the page shows Amount exceeds wallet balance and keeps the action blocked.
Pool status and blocked actions
See why a pool can appear but still reject a public action.
Why an amount can be rejected
The simplest case is an amount above the displayed balance. The page also blocks the action if the same token is selected twice, if the wallet is on the wrong network, if swap execution is not available in the current build, if ERC-20 approval is missing, or if the initial price was not confirmed for a new pool.
Conditional trades
Limit orders
How conditional orders differ from immediate swaps, and why expiry, cancellation, and readable status matter.
Limit orders are conditional trades: users choose the terms first, and execution happens later only if those terms can still be met. DogeFactory separates escrowed orders from signed orders because the fund custody model is different.
Within this section
Limit order basics
Understand the difference between immediate swaps and conditional orders.
Escrowed orders
The input token is reserved when the order is placed. The safest public copy must make expiry, cancellation, and reclaim behavior obvious before users sign.
Signed orders
The wallet signs an order for later settlement. Creation remains unavailable until the user-facing settlement, cancellation, and status reporting are reliable.
Expiry and cancellation
See why expiry, cancellation, and clear status reporting matter before users sign.
What must stay clear
- The public Trade page has a Limit tab. Users may see active creation, read-only status, or an unavailable creation state depending on product readiness.
- Some orders reserve funds at creation. Users need explicit cancellation or expiry paths so funds do not stay stuck.
- Some orders are wallet-signed first and executed later only if the visible conditions still hold.
- Signed order terms should match the visible network, recipient, token pair, amount, minimum output, and expiry.
- Current public policy avoids never-expiring orders, and expired orders should not appear fillable.
- Signed-order creation should stay disabled until user-facing settlement, cancellation, and status reporting are ready together.
Discovery
Analytics discovery
Trending score, gainers and losers, volume movers, new launches, liquidity filters, and boost rules.
Analytics discovery helps users scan markets without confusing visibility with endorsement. The surface starts with a minimum-liquidity filter, then groups market views such as Overview, Trending, Movers, Launches, and Boosts around the clearest public signals currently available.
External data limits
Understand which market lists are only as fresh as their public data inputs.
| Surface | Core target | Live now | Next data needed |
|---|---|---|---|
| Trending Tokens | Score based on recent volume, liquidity, token age, holders, and visible review or routing/trust labels. | The current UI uses available volume, liquidity, holders, token age, visible routing/trust labels, degraded-data states, and a custom liquidity floor. | Improve freshness windows and review signals without presenting them as safety guarantees. |
| Gainers / Losers | Rank the strongest positive and negative price moves, but only after the token clears the minimum liquidity filter. | The panel shows pending or degraded states until reliable price-change data is available. | Improve rolling market snapshots so change percentages are not guessed by the frontend. |
| Volume Movers | Expose highest 24h volume, largest volume acceleration, and low-volume markets as Dormant pools rather than presenting them as opportunities. | Highest-volume tokens and dormant pools are computed from available public market data. | Add clearer review signals for unusual market activity. |
| New Launches Explorer | List latest tokens by creation or first-liquidity timestamp with age, pool, liquidity, volume, holders, and routing/trust status. | Uses token createdAt, holders, routing/trust labels, pool count, liquidity, and 24h volume when those fields are present. | Prefer first live pool timestamp over mutable token metadata whenever possible. |
| Boosts | Paid or team-driven visibility can exist, but it must be labeled, capped, and filtered through quality rules. | The UI documents boost rules and keeps the active boost list empty until a reviewed registry exists. | Build boost policy with expiry, payment proof, review status, exclusions, and a capped score multiplier. |
Liquidity filter policy
- The default minimum-liquidity floor is automatic: the frontend uses a fraction of the median live pool liquidity so one very large pool does not set an absurd threshold.
- Users can override the floor with simple DOGE presets or a custom value, because useful limits differ between tiny testnet markets and mature production markets.
- Liquidity filters apply before trending, gainers, losers, and new-launch rankings, so dead or dust pools do not dominate the discovery surface.
- A low-volume market is labeled as a Dormant pool instead of being hidden silently; that makes inactivity visible without presenting it as a bullish signal.
Live analytics status
Liquidity floor
Live nowAuto baseline, presets, custom input, search, and trust-status filtering.
Discovery v0
Live nowTrending score preview, volume leaders, dormant pools, latest launches, and boost policy placeholder.
Rolling market windows
Next data windowPersist 5m, 1h, 6h, 24h volume and price changes per pool and per token.
Flow quality
Next flow dataImprove visibility into market activity quality without exposing internal scoring details.
Boost quality policy
Next reviewApply review exclusions, cap boost weight, store expiry, and expose the Boosted label everywhere.