DocsIntegration rules

Limits & local patches

The locked method surface, reviewed patches, and deliberately unsupported behavior.

Application reads have a 12-second deadline. Callers must discard superseded results when the wallet, network, or request changes. The deadline bounds the UI wait; it does not promise cancellation of the underlying RPC request. Retained snapshots and local transaction journals are recovery aids, not financial truth.

Position discovery fallback

FxAeon checks canonical pool ownership counts before relying on SDK index results. If IDs are incomplete, app-owned read-only code scans at most 4,096 ownership IDs, in batches of 128 with two concurrent batches, under the shared deadline. Its 128-entry cache stores candidate IDs; ownership and accounting are rechecked on reuse. This fallback is not a sixteenth SDK method and introduces no write primitive.

Position brake reads

Position rows show how far the market can move before a position reaches its pool's rebalance point. While a row is shown, each position refresh makes one multicall of every position's getPositionDebtRatio and each pool oracle's getPrice; each pool's getRebalanceRatios, getLiquidateRatios, and priceOracle are read live and cached for 60 seconds. The SDK 1.0.5 bundle contains these pool views without exporting them, so FxAeon keeps a minimal ABI checked against the bundle. This app-owned code is read-only and signs nothing; it is not a sixteenth SDK method.

Unsupported does not mean implied

Internal SDK files, aggregator routes, contracts, and experiments are not automatically supported product features. Rebalance and liquidation distances come from each pool's live thresholds; global LTV thresholds must not be hardcoded as per-position prices. Reviews show estimated post-action rebalance and liquidation prices only when their required inputs are available, with assumptions behind the info control. The inspected scope exposes no per-position rebalancing opt-out. New transaction primitives require an explicit scope decision.

For the full implementation contract, use SDK scope (opens in a new tab) alongside the facade and plan types (opens in a new tab), canonical position reader (opens in a new tab), and verification guide (opens in a new tab).