Beethoven x
Beethoven x swap quotes help you check the tokens received after a trade
Last updated -
Beethoven x, now called Beets, provides swap quotes that estimate how many output tokens a trade will return. For an exact-input swap, compare the final quoted output with the minimum accepted amount, then reconcile the completed transaction with the recipient’s token balance. Keep network gas separate: a token-output comparison does not measure the full transaction cost.
The useful comparison starts with the same input amount and the same token contracts on the same network. A saved estimate gives the trade a baseline; the transaction record establishes what actually happened when the swap executed.
Pool changes alter the quoted output
Beets uses Balancer technology, with pool mathematics determining exchange amounts and a router providing access to swaps. A quote reflects the selected amount and the liquidity available along its route. Your trade changes pool balances, which can make its average execution rate differ from the marginal rate before trading. That difference is price impact. Other trades or liquidity changes before execution can also change the output, even when your input stays fixed.
Price impact and slippage describe different comparisons. Price impact concerns the effect of the trade itself; slippage concerns movement between the quote and execution. An unfavorable rate already present in a quote does not become favorable through a wider slippage tolerance.
Which details make a swap quote comparable?
A comparable quote uses identical token contracts, network, input amount and trade direction, with a recorded output estimate. The recipient account matters when checking delivery. Token names alone cannot establish that two records concern the same asset. Also retain the minimum accepted output and any displayed route details, so a refreshed quote does not silently replace the terms that you intended to review.
Record the output-token balance before submission if you plan to compare balances afterward. Keep the final reviewed quote, rather than an earlier estimate from before you changed the amount. A screenshot can preserve those displayed terms, although it does not prove which parameters the transaction ultimately used.
Execution also requires a supported route, sufficient input funds, the necessary spending authorization and enough native currency for gas. Review the requested spender and allowance before granting permission. An approval permits spending; its success alone does not establish that the swap happened.
Match a completed swap to its quote
The completed transaction supplies the received amount to compare with the final quote. For ordinary token transfers, the recipient’s balance increase provides a second check when no other activity changes that balance. Use the same token units throughout.
A quoted trade with a minimum-output boundary
All amounts and outcomes in this example are hypothetical. Assume an available Beets route between the selected tokens, ordinary token transfers and no unrelated balance changes. An exact-input swap must satisfy its encoded minimum output. The reviewed quote exchanges 73.5 input tokens for an estimated 42.875 output tokens, with a minimum of 42.61. The recipient already holds 8.125 output tokens. Network gas remains a separate cost that depends on processing the transaction.
The received amount stays above the minimum
After checking the token contracts, spending permission and gas balance, you submit the reviewed swap. The transaction succeeds and records 42.73 output tokens delivered to the recipient. The new output balance is 50.855 tokens: subtracting the starting 8.125 confirms receipt of 42.73. This is 0.145 below the quote and 0.12 above the minimum. The output satisfies the chosen boundary despite differing from the estimate.
The available output falls below the minimum
If execution would return only 42.58 output tokens, the same minimum-output check causes the swap to revert. That failed transaction produces no completed exchange, though it can still consume gas. Confirm the failed status before considering another submission. A new attempt needs a fresh quote and renewed review of its terms; raising tolerance merely lowers the amount that the transaction will accept.
Does minimum received promise the quoted amount?
Minimum received sets an acceptance floor for an exact-input swap; it does not promise the estimated output or successful execution. The router’s exact-input swap includes a minimum output amount that constrains execution. The estimate and the floor therefore answer different questions. One describes the calculated output at quotation time, while the other expresses how much adverse movement the submitted transaction permits.
A tighter floor leaves less room for unfavorable movement and can increase failures when conditions change. A wider allowance permits a worse execution price. Neither setting repairs the wrong token selection or protects against every contract vulnerability. Keep the minimum attached to the transaction that you signed: a later quote cannot explain its limit.
Separate the token result from gas costs
Beets swap fees vary by pool according to the underlying assets and AMM logic. Pool fees affect the calculated swap output, so subtracting them again from a quoted net output would double-count that cost. Network gas pays for transaction processing and belongs in a separate record. Include any separate approval transaction when assessing the total operation cost. If the native gas asset is also the input or output asset and the account being checked pays gas, its balance difference mixes trading and gas movements. Use the transaction’s transfer details and actual gas charge to separate them.
When is a fresh quote more useful than the saved quote?
A fresh quote is more useful for deciding whether to make a new trade, while the saved quote explains the terms reviewed before an existing transaction. Refreshing cannot reconstruct an earlier pool state. It can produce a different estimate because liquidity, fees or market conditions have changed. Changing the trade size also creates a different comparison, even when the selected tokens remain identical.
For reconciliation, retain the transaction identifier alongside the saved estimate and its minimum output. Check the recipient and token contract before interpreting an apparent shortfall. Unrelated transfers can make a later wallet balance misleading, and display rounding can hide small differences.
Helpful answers about Beethoven x
Can I obtain a Beets swap quote before approving a token?
A read-only swap query can calculate an estimate without a token spending approval. Quoting simulates the operation without transferring your funds. Execution has separate balance and authorization requirements, so receiving an estimate does not establish that your account can complete the transaction. Granting permission also does not reserve the quoted rate while you prepare the swap.
Why can my wallet’s currency valuation differ from the swap estimate?
A wallet’s currency valuation uses price data that can differ from the rate available through the swap route. The valuation can also change after execution while your token quantity stays unchanged. Compare the actual output-token quantity first. A difference between displayed currency values alone does not establish that the swap delivered fewer tokens than its transaction record shows.
How do token decimals affect the received-amount comparison?
Token decimals determine how raw integer amounts translate into the quantities that a wallet displays. Divide a raw token amount by ten raised to that token’s decimal count before comparing it with a human-readable quote. Use the decimal count for the exact token contract. Comparing raw units with a formatted quantity creates an apparent discrepancy even when both represent the same transfer.
Does an unavailable swap quote mean my tokens have disappeared?
An unavailable quote does not establish a change in your token balance. Quote retrieval and token ownership are separate: a route may be unavailable, or a service involved in calculating the estimate may fail. The account balance and any submitted transaction determine whether funds moved. Repeating a quote request alone does not execute a swap.
Is the swap output visible to other people on the blockchain?
The swap’s on-chain transfers are public, so another person can inspect the receiving address and token amounts. A transaction identifier can connect a shared screenshot or discussion to those records. A locally saved quote is separate from the blockchain record, but sharing it alongside account details can reveal which public transaction belongs to you.