Does High Trading Volume Mean SAGE Has Deep sell-side Liquidity?

High trading volume does not establish deep sell-side liquidity. Volume totals completed trades over a stated interval, while depth concerns the trading capacity available at relevant prices. Repeated trades can generate substantial volume in a shallow market. The executable quote for the intended sale amount provides a more direct view of its pricing.

Can a Chia Offer Complete With Only Part of Its Requested Payment?

A standard Chia offer completes only when all its payment conditions are satisfied. A compatible aggregator can combine offers to supply the required assets through a combined settlement. Each included offer retains its signed payment requirements. Contributing part of a requested payment alone does not complete the original exchange.

Will Minting a Token in Sage Wallet Create Market Liquidity?

Minting a token in Sage Wallet does not automatically create market liquidity. Issuance creates the asset without creating funded purchase offers or depositing paired assets into a trading pool. A liquid market still requires counterparties or pool capital willing to exchange it. A wallet can therefore hold a token without an executable selling quote.

Is a Failed SageSight Swap Always Caused by Insufficient Liquidity?

A failed SageSight swap does not by itself identify a liquidity shortfall. A swap can also fail because of incompatible assets, token contract restrictions, insufficient fee funds, or execution outside the route's limits. Where a route enforces minimum output, failure can mean execution would have returned less than the required amount. Increasing tolerance cannot repair missing compatibility or replenish a fee balance.

What Does an NFT collection's Listed Floor Price Say About Liquidity in Sage?

A listed floor price identifies the lowest asking price in an NFT collection. It does not establish a funded offer to buy a particular NFT. Item-specific demand and available purchase offers can produce different selling terms. In a Chia offer, the requested NFT identity and payment conditions determine the exchange.

Sage

Sage liquidity depends on swap depth and funded Chia offers.

Sage liquidity affects the price available for a trade and the amount the market can absorb. Sage Wallet handles Chia offers with specified exchange terms, while SageSight quotes swaps through external trading venues. Those mechanisms draw on different trading capacity. Pool depth influences routed swap prices; valid, funded offers determine which exchanges the wallet can complete. The quoted output must match the selected assets, trade size, and fees to describe an executable sale.

Updated on Wed, Oct 7, 2026

The short version: For an exact-input swap, an enforced minimum output limits acceptable execution while available depth shapes the quote.

Chia Offers and SageSight Swap Routes

The asset's network determines which Sage trading mechanism applies, because Sage Wallet and SageSight belong to separate crypto systems with different execution methods.

Fixed Terms in Sage Wallet

Sage Wallet remains in beta and supports peer-to-peer exchange through Chia offer files, except in the App Store build introduced in version 0.13.0. A maker specifies the assets offered and the payments required in return. A taker supplies the matching payments to complete the exchange. The offer fixes those terms, while available counterparties determine whether anyone will accept them. Publishing an offer makes a proposed exchange discoverable; it does not create demand for the asset.

Routed Pricing in SageSight

SageSight quotes swaps using aggregated decentralized exchange liquidity on EVM networks. EVM means Ethereum Virtual Machine, the execution environment those networks support. Its Solana swap instructions call for a specified trading venue. A decentralized exchange (DEX) supplies the underlying trading mechanism; the assistant prepares the requested trade and presents its route, fees, and expected output before confirmation. Network support does not establish liquidity for every token on it.

Asset Compatibility and Spendable Funds

Asset compatibility requires the token identity and network to match the trading mechanism, even when a wallet displays a familiar name or balance. A Chia Asset Token (CAT) has an asset identifier distinguishing it from other tokens. For contract-based assets, the contract address and network identify the intended token. A matching ticker does not establish that identity. SageSight's research tools expose contract and on-chain liquidity information, helping distinguish assets before quoting a trade.

Spendable funds are the holdings available for the proposed operation. Local wallet reservations for pending Chia offers cover whole coin inputs, so reserved value can exceed the amount being exchanged. A reservation does not establish a completed sale. A required network fee needs usable funds in its payment asset. That asset may differ from the quoted trade output.

Trade Size and Executable Depth

Executable depth describes available trading capacity at particular prices for an asset combination. Trade size determines how much of that capacity an exchange uses.

Pool Reserves and Active Ranges

An automated market maker (AMM) calculates exchange amounts from pool assets and a pricing rule. Price impact is the price change a trade causes in its trading pool. A larger sale relative to available depth generally moves the average execution price further from the initial pool price. The relevant depth belongs to the route and assets under consideration. Liquidity elsewhere only helps if the trading mechanism can reach it.

Concentrated-liquidity pools assign capital to chosen price intervals. Positions whose ranges exclude the current market price do not supply active liquidity there. A pool's total value can therefore overstate the capital available near the quoted price. These range conditions apply specifically to concentrated-liquidity designs.

Visual summary: Pool Reserves and Active Ranges (Sage liquidity) — Pool Reserves and Active Ranges

View image file

Offer Amounts and Quoted Rates

An individual Chia offer specifies an exchange amount alongside its requested payment. Its rate applies to those terms. An attractive small offer does not prove a larger sale can achieve the same rate. Additional compatible offers may have different prices or quantities. A displayed listing can become unavailable once someone spends its underlying coins. The achievable trade therefore depends on valid offers matching the intended assets and amount.

Quote Movement and Execution Limits

Pool state can change between quoting a trade and executing it, so expected proceeds reflect conditions at the time of the quote. Slippage is the difference between an expected execution price and the price actually achieved.

An exact-input quote starts with a specified amount to sell. Where its route enforces a minimum output, execution must deliver at least that amount or fail. An exact-output route fixes the desired receipt and can instead enforce a maximum spend. Those protections depend on the integration. A quoted estimate alone does not establish an enforceable boundary.

SageSight's agent fee tier depends on the SAGE balance in the user's SageSight wallet at trade time. Pool fees and network costs remain separate cost inputs. A service discount does not itself add reserves to the trading route.

Transaction deadlines, where implemented, restrict how long submitted swap terms remain valid. A fresh quote can change both expected output and the proposed route. Widening a supported slippage tolerance permits greater deviation from the quote; it does not replenish liquidity. Keeping a tighter boundary can mean the trade fails when available execution falls outside it.

Sage liquidity: Quote Movement and Execution Limits - illustration

View image file

Liquidity Provision and Token Allocations

Liquidity provision commits capital to a trading mechanism, creating a different exposure from holding tokens outright or accepting an existing exchange offer.

Supply Assigned to Liquidity

SAGE tokenomics includes an allocation for liquidity provision. That allocation describes a purpose for token supply; it does not measure a pool's live reserves. Selling tokens through a pool requires available reserves of the asset being received. The allocation percentage alone cannot establish that reserve balance, its price distribution, or the proceeds available for a particular sale.

Fee Income and Changing Inventory

Pool providers may receive a share of swap fees under the pool's rules. Trades change the mix of assets in their positions as market prices move. Impermanent loss describes the value shortfall relative to holding the original assets separately. Fee income may offset that difference. In concentrated-liquidity designs, positions stop earning swap fees while the market price sits outside their intervals. A provider's exposure depends on the pool position, its fee rules, and the assets exchanged.

A Routed Sale With an Output Floor

A routed sale needs compatible assets and available trading capacity before a quoted output has practical meaning. Consider selling a held asset through a route offering an enforceable minimum output. The quoted proceeds change with market depth; the approved minimum defines the sale's acceptable output boundary.

Match the input and output identifiers to the selected network before assessing the quoted trading capacity.
Require a route for the intended sale amount; an unavailable combination means leaving that sale unsubmitted.
Check expected output, separately charged fees, and the enforced minimum before confirming the proposed transaction.
Treat submission as pending execution; a transaction identifier alone does not establish delivered sale proceeds.
Reconcile the confirmed asset movements and fee payments with the approved terms before counting the proceeds as available.

Fees paid in a different asset need separate accounting; subtracting them directly from the received token count mixes units.

Confirmed Trades and Changing Exit Capacity

Trade completion establishes delivered assets, while quoted and pending amounts describe earlier transaction states. Chia offers settle atomically, meaning all required asset exchanges complete together or none does. A submitted offer exchange still needs confirmation before its pending receipt represents a completed payment. Its signed conditions constrain settlement even when a public listing shows an outdated status.

View image file

On-chain cancellation spends the coins backing a Chia offer, invalidating that offer. Sage Wallet supports this cancellation mechanism. Removing a listing or deleting a local file does not spend those coins. A distributed copy can remain executable while its input coins remain unspent and its other conditions hold. Confirmed on-chain cancellation prevents another taker from completing the old offer.

Exit liquidity belongs to the market at the time of the next sale. Pool withdrawals, changing active price ranges, and consumed offers can reduce that capacity after a successful purchase. A previous fill does not reserve a future buyer or preserve the same exchange rate. A holding may remain transferable while the desired sale lacks an acceptable executable price.

Frequently asked questions about Sage liquidity

Does High Trading Volume Mean SAGE Has Deep sell-side Liquidity?: High trading volume does not establish deep sell-side liquidity. Volume totals completed trades over a stated interval, while depth concerns the trading capacity available at relevant prices. Repeated trades can generate substantial volume in a shallow market. The executable quote for the intended sale amount provides a more direct view of its pricing.
Can a Chia Offer Complete With Only Part of Its Requested Payment?: A standard Chia offer completes only when all its payment conditions are satisfied. A compatible aggregator can combine offers to supply the required assets through a combined settlement. Each included offer retains its signed payment requirements. Contributing part of a requested payment alone does not complete the original exchange.
Will Minting a Token in Sage Wallet Create Market Liquidity?: Minting a token in Sage Wallet does not automatically create market liquidity. Issuance creates the asset without creating funded purchase offers or depositing paired assets into a trading pool. A liquid market still requires counterparties or pool capital willing to exchange it. A wallet can therefore hold a token without an executable selling quote.
Is a Failed SageSight Swap Always Caused by Insufficient Liquidity?: A failed SageSight swap does not by itself identify a liquidity shortfall. A swap can also fail because of incompatible assets, token contract restrictions, insufficient fee funds, or execution outside the route's limits. Where a route enforces minimum output, failure can mean execution would have returned less than the required amount. Increasing tolerance cannot repair missing compatibility or replenish a fee balance.
What Does an NFT collection's Listed Floor Price Say About Liquidity in Sage?: A listed floor price identifies the lowest asking price in an NFT collection. It does not establish a funded offer to buy a particular NFT. Item-specific demand and available purchase offers can produce different selling terms. In a Chia offer, the requested NFT identity and payment conditions determine the exchange.