DOCS
Security and trust
What the current contracts enforce, what remains configurable, and what users must verify.
Security and trust
Contract-enforced boundaries
- fixed billion-unit initial supply and no later mint;
- factory-only registration and initialization of canonical pools;
- permanent launch-liquidity custody with no withdrawal or rescue path;
- immutable V1/V2 mode and immutable V2 tax, split, referral, and buyback allocations;
- official-router-only first referral binding, V2-buy-only candidates, and no self-referral;
- separate protocol, referral, creator, and buyback accounting;
- cached Chainlink native/USD presentation data with round, timestamp, and staleness checks; it cannot affect a contract money path;
- exact-input, full-consumption, output, price-limit, and deadline checks;
- executor-only, accrued-balance-only, slippage-bounded buyback and burn.
The owner may register or disable pair-asset profiles for future launches, transfer ownership in two steps, and replace the buyback executor. Those controls cannot rewrite an existing pool's pair asset, launch mode, fee rates, creator split, buyback allocation, liquidity, or referral binding.
External and offchain boundaries
Uniswap V4 core, the chain, pair assets, Chainlink, wallets, RPCs, and transaction ordering remain external dependencies. Fledgo's database, search, charts, holder list, media, and USD display may be stale or unavailable, but cannot transfer onchain principal or claims.
Stock Tokens add issuer, redemption, transfer-control, market-hours, legal, decimal, and liquidity risks. Permanent liquidity is irreversible and does not guarantee buyers, value, depth, price support, or recovery. Verify every deployed address and transaction before use.