Limit Orders
AquaVaults Limit Orders allow users to define swap conditions ahead of time so participation can occur when target prices are reached instead of only during manual interaction.
Participation Beyond Immediate Swaps
Most swap activity is immediate. A user decides they want to swap, opens the interface, and executes the trade at the current price. That works well for users whose intent aligns with current market conditions, but it requires being present at the right moment — and not every user wants to participate that way.
Limit Orders extend that model. Instead of executing immediately, users define the conditions under which they want a swap to happen. The order persists until those conditions are met, at which point it can execute — without the user needing to be present or monitor the price manually.
This gives users a different relationship with their own participation. Rather than reacting to current conditions, they define future intent and let the system carry that intent forward until the moment it becomes relevant.
How Limit Orders Work
The process is straightforward. Users configure the order ahead of time, and the infrastructure monitors for the conditions the user defined until the order becomes eligible for execution.
Select a token pair
Choose the token to sell and the token to receive. This defines the direction of the intended swap.
Set a target price
Define the price condition at which the order should execute. The swap will not proceed until the price reaches or crosses the specified target.
The order waits
The order remains open and monitored. The user does not need to stay active on the platform. The condition persists until it is met, cancelled, or expires.
Execution when conditions align
When the target price is reached and routing conditions allow, the order executes. The swap completes according to the parameters the user set at the time of configuration.
Some Token-2022 assets may not behave reliably with Jupiter Limit Orders depending on the token's configuration and Jupiter Trigger support. If a selected token is identified as Token-2022, a confirmation prompt will appear before the order is placed.
Community Routing Is Not Currently Supported
This is an important distinction to understand before using Limit Orders as part of a community participation strategy.
Limit Orders currently do not route activity toward selected communities. Community fee routing — the mechanism that directs platform fees toward a community when a user swaps with that community selected — is not part of the Limit Orders flow at this time. This limitation applies regardless of which community a user has selected in other parts of the platform.
This is not a configuration issue and not something users can work around by adjusting settings. The limit-order infrastructure operates through a different execution pathway than the Solana Swapper and AutoSwap, and that pathway does not currently support the same community routing integration.
Users who want their swap activity to contribute toward community routing should use the Solana Swapper or AutoSwap for that purpose. Limit Orders remain a useful tool within the broader AquaVaults ecosystem — but their current role is user-directed timing flexibility rather than community-directed fee routing.
This distinction is stated clearly here because the rest of the ecosystem docs consistently reinforce community routing as a central feature. Limit Orders are the exception to that, and users deserve to know that before building plans around them.
Why Users Still Use Limit Orders
Even without community routing, Limit Orders serve a real purpose for users who prefer not to execute swaps at current prices or who do not want to manually monitor conditions.
Execution on Your Timeline
Users who have a view on where they want to participate can configure the order once and let it execute when conditions arrive — without needing to watch price action or act quickly in the moment.
Participation Ahead of Time
Intent can be locked in before market conditions reach the desired level. Users define where they want to participate; the order carries that intent forward until it becomes relevant.
Reduced Manual Overhead
For users who would otherwise need to repeatedly monitor prices waiting for specific conditions, Limit Orders reduce that manual overhead significantly. Configure the conditions ahead of time and allow the order to persist until they are met or cancelled.
How Funds Are Handled
Limit Orders on AquaVaults are processed through Jupiter's limit order infrastructure. The custody model for limit orders differs from that of an immediate swap — users should understand this before placing an order.
When a limit order is created and the user confirms the transaction, the sell-side tokens leave the user's wallet and are deposited into Jupiter's limit order program. Jupiter's infrastructure holds those tokens and monitors the price condition until the order executes or the user cancels. This is different from an immediate swap, where tokens only leave the wallet at the exact moment of execution.
AquaVaults does not hold or manage user funds in limit orders. AquaVaults provides the interface and participation layer — the infrastructure that processes and holds funds during an open order is Jupiter's. Users should review the order details presented in their wallet and refer to Jupiter's documentation for a full explanation of how limit order execution and fund handling works before signing.
Users can cancel an open order at any time through the platform. When cancelled, Jupiter's program returns the deposited tokens to the user's wallet. The ability to cancel is always available — but the tokens are held within Jupiter's infrastructure between order placement and execution or cancellation, not in the user's wallet.
Limit Orders Inside The Broader Ecosystem
Although Limit Orders do not support community routing, they still exist within the same AquaVaults ecosystem as every other tool. Users who rely on Limit Orders for price-conditioned swaps can use the rest of the platform for community-directed participation activity.
The two functions are complementary rather than competing. A user who sets a Limit Order for price-based execution and also runs AutoSwap sessions for community participation is using both tools for what each one does well. One serves execution timing. The other serves community-directed recurring activity.
Limit Orders, the Solana Swapper, AutoSwap, and the Co-op Mining Rig all operate within the same ecosystem. They do not compete with each other. Users who want both execution flexibility and community participation can run both — directing community routing activity through the Swapper or AutoSwap while using Limit Orders separately for price-conditioned trades.
More Than Manual Timing
The underlying value of Limit Orders is not about sophistication or execution precision. It is about something simpler: participation does not always have to happen in the moment.
A user who defines an order today is expressing where they want to participate ahead of time rather than reacting only in the moment. They do not need to constantly monitor the market or manually wait for conditions to align. The order structure allows that intent to persist until the configured conditions become relevant.
That is a different posture toward participation than immediate swaps require — and for the right users in the right situations, it is a more sustainable one. Not all participation has to happen in the moment. Limit Orders allow users to structure participation around future conditions while remaining inside the AquaVaults ecosystem they already use for everything else.
Continue Exploring