Policy & blacklist status

Open pools, scan signals, explicit risk blocks

DogeFactory can show a token in discovery, analytics, wallet views, or pools without endorsing it. This page explains the policy and lets users send a lightweight scan signal to admin triage. The scan does not whitelist, endorse, or promise a route; public swaps stay open for non-blocked pools that pass liquidity and runtime checks.

Request token scan

Use this when a token looks risky, a route is missing, or a swap attempt needs operator context. The request is transmitted to Admin > Token Policy > Triage inbox with the intake scan result.

Admin triage

1. User signal

Contract, optional contact, and reason are recorded.

2. Intake scan

Known risk words and request history produce a triage status.

3. Admin decision

Operators can re-scan, approve context, or block specific risk.

A valid token contract is required before confirmation.

How to read this page

Trust is separate from routing

A token can exist on the network, and a pool can exist on DogeFactory, without carrying a DogeFactory trust mark.

Missing routes are not blocks

When the public swap path cannot execute yet, the token can still be observed without being treated as clean or endorsed.

Risk signals explain blocks

Tokens stay open by default when the registry is readable; critical risks move to an explicit token block.

Liquidity still matters

Even a non-blocked token still needs a real pool and enough liquidity before execution can work.

Public trust states

Trusted

Trusted

An official or reviewed trust mark does not guarantee routing by itself. A live pool and runtime checks still decide execution.

Observed

Observed

The token or pool can be shown by the app without being endorsed or marked clean by DogeFactory.

Blocked

Blocked

Critical risk was detected or recorded. Public swaps and new liquidity stay unavailable until policy changes.

Why a token may be blocked automatically

  • Hidden or unstable transfer fees
  • Sell-block or honeypot-like behavior
  • Blacklist or freeze controls that can target normal users
  • Abusive minting or supply changes
  • Misleading metadata or impersonation risk
  • Repeated failed risk signals or missing basic verification data

Automatic blocking is meant to keep clearly unsuitable tokens away from public swaps and new liquidity while operational follow-up stays manageable.

Why a route may be unavailable without being blocked

  • No pool exists yet for the selected pair
  • A pool exists, but liquidity is too low for public swapping
  • The token is visible, but no usable pool was found yet
  • The first usable pool still needs to be created
  • The route is waiting for public app data to catch up

No route is not the same as blocked. It often means the token needs a first pool, more liquidity, or a fresh index update.

How the open pool policy works

Official DogeFactory launchers auto-register their tokens on-chain through approved registrars.

External tokens can still appear in discovery, pools, or wallet views if DogeFactory finds them on-chain or through the DogeOS list.

Pool creation is open for tokens that are not explicitly blocked. A pool can be visible without meaning DogeFactory endorses the token.

Public swaps use live pools when blacklist, liquidity, hook, module, and runtime checks pass. Critical-risk tokens can be blocked from swaps and new liquidity.

Existing LP positions can still inspect pools and remove liquidity even if a token later moves into blocked status.

Where to double-check

Use the token page, pool page, and wallet exposure panel together. Discovery answers "can I see it here?", while status badges answer "what does DogeFactory currently know about risk?".

Live public policy status

Registry readability

Unreadable

Blacklist enforcement

Unknown while registry is unreadable

Pool creation policy

Open unless blocked

Visible pools are not automatically endorsed by DogeFactory.

Risk handling

Automatic signals + manual follow-up

Clear, unclear, and critical-risk signals take different paths.

Deployment manifest

--

Updated --

Public UI toggles

Explorer-listed discovery: hidden by default

Explorer-listed limit-order discovery: quiet defaults

Limit orders V1: hidden

Signed limit orders: hidden

Manual fee-tier panel: hidden

What this page does not mean

A status, trust label, or submitted scan request is not the same thing as an audit, endorsement, whitelist, or promise of future liquidity.

A visible token or pool is not automatically trusted. A visible route can still be a bad trade.

DogeFactory does its best to reduce obvious risks and protect users, but no automated or manual policy can filter everything.

The policy model helps keep routing legible and safer. Users should still do their own research before deciding what they are getting into.