Official wallet-native order explainer
NOVA lets a supported signing wallet create SOL-pair trigger orders from a token page. The app binds the order to an exact owner, pair, amount, target, expiry, route program, and finite delegated allowance—then separates submission, finality, registration, fill, and cleanup.
Owner-reviewed lifecycle
NOVA refreshes balances, available allowance capacity, token policies, current price evidence, and order history. It builds an exact record with owner, nonce, revision, pair, amount, target, expiry, router, and private salt commitment.
The wallet prepares required token accounts and a finite aggregate allowance, simulates the transactions, and asks the owner to sign. A watched wallet cannot place or mutate an order.
NOVA distinguishes submitted, confirmed, finalized, registering, and registered. Success presentation is permitted only after finalized Solana proof and canonical API registration agree.
Current order matrix
| Capability | Current behavior | Boundary |
|---|---|---|
| Limit entry | Buy a supported Solana token with SOL at a target USD price or derived market-cap target. | SOL must be the input; current source does not support arbitrary token-to-token pairs. |
| Take profit | Sell a chosen portion of a held supported token to SOL above the current target. | Requires a current supported balance and price evidence. |
| Stop loss | Sell a chosen portion of a held supported token to SOL below the current target. | A fast move, thin liquidity, route failure, or keeper delay can miss the intended price. |
| TP/SL pair | Two legs can share one OCO-style order reservation. | It is not an exchange guarantee; partially filled and recovery states remain possible. |
| Edit | Target edits preserve owner, token pair, identity, and advance the revision. | Only a completely unfilled active order can be edited. |
| Cancel | Owner-reviewed cancellation removes the active order and releases its reservation after finality. | A fill or expiry can win the race; NOVA reconciles the canonical and chain state. |
| Expiry | Default seven-day expiry; expired records can expose a cleanup action. | Expiry is advisory until an on-chain expire transaction lands. |
| Filled cleanup | After a verified complete fill, the owner can recover remaining rent and close no-longer-needed order accounts. | Cleanup is separate from fill and preserves canonical filled history. |
Funds and authority
The current NOVA path keeps the source token account under the user's ownership and uses Solana's delegate mechanism instead of depositing all orders into a provider-managed vault.
The signed delegated amount equals the allowance group's reserved input across active orders. NOVA rejects unrelated existing delegates and validates that the finalized allowance is finite and matches the aggregate reservation.
The order commits to NOVA's deployed executor program, a defined keeper authority or supported Pyth feed, and the Jupiter router. These controls reduce scope; they do not eliminate smart-contract, keeper, router, token, or oracle risk.
The token-account owner can still change the account state outside NOVA. Spending or revoking funds needed by an active order can make it fail. Treat every delegated allowance as real spending authority.
Fees and eligibility
| Rule | Current source value | What it means |
|---|---|---|
| Pair | SOL must be one side | Limit entry is SOL to token; take-profit and stop-loss are token to SOL. |
| Minimum input | $3 | NOVA rejects smaller orders before the owner signs. |
| Protocol fee | 50 basis points (0.5%) | Applied by the committed order execution path. |
| Route slippage | 100 basis points (1%) | Fresh execution liquidity still determines whether the route can fill. |
| Native SOL reserve | Up to 0.01 SOL initially | Kept available for account setup and network costs; reusable order accounts reduce the calculated reserve. |
| Default expiry | Seven days | The permissionless expiry path still needs an on-chain transaction. |
| Token policy | Classic SPL Token and narrowly supported Token-2022 shapes | Unsupported authorities, extensions, programs, mints, or account shapes fail closed. |
Interrupted workflows
If preparation, signature, submission, finality, or registration is interrupted, NOVA records enough non-secret mutation state to reconcile rather than inviting a blind duplicate action.
The order page can expose “Resume Order,” “Retry Order Recovery,” or cleanup actions depending on whether a signed transaction exists and whether temporary setup accounts remain.
Changing pages, duplicated records, mismatched revisions, partial histories, unexpected delegates, non-finalized transactions, or canonical/on-chain disagreement do not become authoritative success.
Evidence and corrections
The types, route constraints, fee constants, order binding, simulations, finite allowance checks, canonical registration, recovery journal, expiry, partial-fill, cancellation, and cleanup states come from current NOVA iOS source. This is a source-level product contract, not an independent smart-contract audit or a production order test.
This page applies only to NOVA - Solana Wallet, App Store ID 6753857720, published by 404 ENTERPRISES, LLC. It does not prove a funded order, protected API acceptance, deployed-program audit, keeper uptime, fill, realized price, cancellation race, signature, broadcast, or finality.
Send factual corrections to hi@nshield.org. Never include a recovery phrase, private key, signed transaction, order authentication token, or signing payload.