User-defined execution boundary engine for PreStocks

You set the boundary.Sieve enforces it.

Set the execution constraint for a PreStocks trade. Sieve measures current Jupiter execution against the PreStocks reference, accounts for the token's onchain economics, and verifies how much of the requested order currently fits your boundary before transaction preparation.

Explore PreStocks

Illustrative exampleNot live market data

AssetOpenAI (OPENAI)

Reference price$500.00

Configured boundary+5.0% maximum premium ($525.00)

Requested order1,000 USDC

Within boundaryBoundary Capacity Verified

650 USDC of the requested 1,000 USDC is currently verified within your configured boundary.

Verified Amount: 650 USDC · Effective Price: $512.40

Executable route checkReady to prepare

The Core Question

How much of my requested order can execute right now without crossing the boundary I set?

Boundary Capacity shows how much of your requested order was actually verified within your configured boundary.

Instead of executing blindly or failing completely on price impact, Sieve probes executable route candidates up to your requested amount. When partial capacity is observed, you choose whether to prepare only the verified portion. Verification is bounded to observed route samples during the check; it is an empirical constraint check, not a theoretical market depth claim.

Two-Sided Enforcement

Configurable constraints for both Buy and Sell orders.

Whether acquiring or exiting PreStocks, you define the execution boundary and Sieve enforces it.

Buy PreStocksUSDC or SOL funding

User sets Maximum Premium

Sieve verifies effective Buy execution against the PreStocks reference. If current route execution exceeds your maximum premium (reference price + premium ceiling), the order is blocked before transaction preparation.

Constraint: Maximum execution price ceiling

Output: Target PreStock units delivered to wallet

Sell PreStocksUSDC output

User sets Maximum Discount

Sieve verifies effective Sell execution against the PreStocks reference. If current route execution falls below your minimum price (reference price − discount floor), the order is blocked before transaction preparation.

Constraint: Minimum execution price floor

Output: Canonical USDC proceeds delivered to wallet

Architecture & Roles

Clear separation of state, execution, and policy.

Sieve evaluates executable routes against the current PreStocks reference, accounts for onchain token economics, and enforces your execution policy.

PreStocks

Reference state

Asset registry and reference state. PreStocks maintains official reference valuations. Sieve evaluates executable routes against the current PreStocks reference.

Jupiter

Executable liquidity

Current executable route. Jupiter shows what can execute; Sieve checks whether that execution still fits the boundary you set.

Solana

Token-2022 economic state

Onchain token state. Sieve accounts for Token-2022 economic state such as scaled UI amounts and transfer fees before treating a route as valid.

You

Execution policy

You set the boundary (maximum premium or maximum discount) and choose the order size. Sieve enforces your policy instead of advising you.

Sieve (Verification + Enforcement): Boundary Capacity evaluation and final execution-boundary enforcement. Verifies route execution before transaction preparation and protects transaction constraints.

Execution Lifecycle

Actionable verification before wallet signature.

Sieve is an execution boundary engine, not a read-only analytics dashboard. Every boundary check leads to an actionable transaction preparation flow.

Check boundary

Set asset, side, amount, and your execution boundary (maximum premium for Buy or maximum discount for Sell).

Inspect Boundary Capacity

Sieve measures Jupiter route candidates against the PreStocks reference and returns the verified capacity.

Choose verified amount

When capacity is partial, choose to prepare the verified amount or adjust your boundary.

Prepare transaction

Sieve rechecks the reference, token state, and executable route and enforces the user's boundary in the final transaction constraints.

Review and sign

Review the exact order ticket details and explicitly sign with your connected Solana wallet.

Server-Authoritative Enforcement

Define the execution limit. Verify the route. Prepare only what still fits.

Before transaction preparation, Sieve rechecks the reference, token state, and executable route and enforces the user's boundary in the final transaction constraints.

Check a boundary