Understand capability and availability labels

Understanding the platform · Reference · Source-reviewed capability boundaries, not a live authorization or a production acceptance report.

Separate implemented code, release admission, runtime readiness and verified outcomes.

Reviewed: 2026-10-18

Before you start

  • No account is needed to read. Use the current action screen for any private capability check.

What each label establishes

Implemented means there is a supported code path. Admitted means the release boundary permits new use. Enabled or available is a current, scoped capability report, still subject to account, asset and transaction checks. None of those labels is proof of a completed outcome.

Unavailable means the action cannot currently proceed in that scope; read its reason. Stale means the last known data cannot be treated as fresh. Deferred means new admission is not open. Legacy/recovery-only preserves existing obligations without opening new activity.

Verified outcome requires evidence for that exact event: for example the original confirmed transaction, public metadata verification or a finalized source receipt. One event does not prove a different event, such as strategy activation or external logo acceptance.

Configuration is not authority

Use this hierarchy: implemented source, permitted admission, fresh scoped runtime capability, then exact outcome evidence. A display-only Learn configuration table, deployment flag or old screenshot cannot sign, grant permission or prove a trade.

Source-specific gates matter. A top-level launch enabled flag does not summarize every launch source; likewise an admitted venue does not establish a funded account, signing policy or actual fill. Refresh failed/stale reads before acting, and retain the original request if a send may have started.

  1. Read the action’s current scope and blocker reason.
  2. Check wallet/account/asset readiness in that action screen.
  3. Review the fresh exact costs and authority before confirming.
  4. Afterward, verify the specific recorded outcome; do not infer completion from a capability badge.

Current admission boundaries

The reviewed release admits Solana Spot, native reward issuance and the Injective strategy category, each with independent runtime and signing gates. This is not a statement that every token trades, every account can launch or a strategy has executed.

New standard issuance is recovery-only. New Pump issuance, Pump/StonkFun adoption, X launch and new router configuration are deferred. Phoenix and additional strategy venues are outside the admitted execution boundary; no substitute venue is silently selected.

Card and Apple Pay funding are coming soon; existing funding reads/reconciliation do not reopen checkout. Index, routed dividend designs, hosted leverage/liquidity, PRO, airdrops and sponsorship explanations or shells must not be read as usable payout, purchase, claim or booking workflows.

Historical design is not current enforcement

The specification preserves design provenance and stable section references. Current capability boundaries and exact action reviews take precedence over a historical diagram or normative design paragraph.

Read existing-obligation and current-new-use guidance separately. A recovery route can remain necessary after new admission closes. Static article review dates are not live status timestamps; revisit the current screen whenever you act.