Shib ShibaSwap supports token swaps and liquidity management through v1 LP tokens and v2 NFT positions.

Pool balances connect trades with liquidity ownership

Both ShibaSwap versions connect swaps with liquidity provision through token pools, where active liquidity supports trading between the pool’s assets. A swap transfers an input asset into the pool route and returns its output asset. Liquidity providers supply assets the pools use, then hold a representation of their position. Each pool has a token pair, identified by the token contracts on its network.

The wallet owner controls the request, including amounts and spending permission. ShibaSwap’s router handles the chosen trade path, while pool contracts calculate exchanges and update their accounting. A connected-wallet label identifies the account an interface is using. Allowances and pool positions have their own contract records.

Position records separate v1 pool shares from v2 price ranges

Fungible shares in v1

A v1 deposit supplies both pool assets at equal value and creates fungible LP tokens representing the provider’s share. The pool uses the constant-product relationship, x * y = k , where x and y represent token reserves. Deposits cover the full price range. Removing liquidity redeems the LP share for underlying pool assets. Because swaps change reserves, the token composition and value of the withdrawal can differ from the deposit. Equal token counts are unnecessary; equal value depends on the pool’s asset prices.

NFT positions in v2

ShibaSwap v2 represents individual liquidity positions as NFTs. Each position records its pool and price range. Its owner can increase or decrease liquidity and collect accrued fees for that position.

Range selection and swap fees

Concentrated liquidity allocates assets within the selected interval. The position can earn swap fees while the market price remains inside that range. Moving outside it stops new fee earning from swaps until the price returns. An out-of-range label describes eligibility to earn new swap fees; it does not calculate the position’s overall profit or loss.

Position value and impermanent loss

The NFT identifies a particular position, including its range and fee tier. Its displayed liquidity value reflects exposure to the pool’s assets. Choosing a range changes where liquidity participates; it does not fix a future withdrawal value. Token price changes can produce impermanent loss, meaning the pool position can underperform holding the same assets directly.

What does a ShibaSwap token approval authorize?

A ShibaSwap token approval grants a specified contract permission to spend an ERC-20 token up to the approved allowance. The approve function names the spender and allowance, while allowance reports the remaining authorized amount. Approval does not itself swap tokens or create a liquidity position. The operation requiring that permission follows its own transaction parameters. Existing sufficient allowance can satisfy the requirement without another approval.

Permission belongs to the combination of token owner, token contract and spender. Approving a router does not automatically authorize every staking or bridge contract. The wallet owner chooses whether to grant the requested amount and checks the spender before signing. The ERC-20 standard lets a later approval replace the allowance for that spender. Wallet interfaces may handle allowance changes differently, so an approval request should identify the exact contract and amount.

Quotes separate swap fees from network costs

A swap quote combines the selected route with pool pricing, while network gas pays for executing the transaction. Each ShibaSwap v1 pool charges a 0.3% fee on swap inputs. In v1, fees accumulate in pool reserves; LP holders receive their share when removing liquidity. A v2 quote reflects the fee tier of the selected pool; the version name alone does not specify one universal trading fee.

Price impact describes how the requested trade changes the pool price relative to its liquidity. Slippage tolerance limits acceptable execution changes after the quote. A trade can have substantial quoted price impact before any later movement occurs. For an exact-input trade, minimum received is the output floor. An exact-output trade instead uses a maximum input.

Ordinary Ethereum execution uses ETH for gas, while Shibarium uses BONE. Keep that gas balance separate from the token amount offered to the swap or deposit. Approving a token also consumes network execution resources when the approval is an on-chain transaction. A low pool fee does not establish a low total cost, because route complexity and network demand affect the gas charge.

Higher slippage tolerance permits a lower minimum output for an exact-input swap or a higher maximum input for an exact-output swap. It does not add liquidity or reduce the price impact already present in the quote.

View image file

Contract records show transaction results

On Ethereum, a transaction receipt reports success or failure of the top-level call, so the operation behind that receipt matters. Approval success concerns the allowance change; liquidity-transaction success concerns the pool position. For a swap, token transfer records identify the assets and amounts moved. Token decimals translate raw contract units into the amounts a wallet displays.

Position monitoring follows the representation the deposit created. With v1, the LP-token balance records a share of its particular pool. With v2, the NFT identifies the individual position and its configured range. A pool asset balance left in the wallet is different from the assets represented inside a liquidity position. Likewise, an estimated position value cannot show whether a planned withdrawal has executed.

The wallet owner controls later approvals and management requests; contracts determine whether submitted parameters meet their execution rules. A successful swap already changed the holdings. Exchanging back is another trade with another quote. Changing an interface display cannot reverse those transfers. A liquidity withdrawal returns assets under the position’s pool rules.

Match pool exposure to the intended use

A token exchange fits a task requiring the output asset, such as a later transfer on the selected network. Liquidity provision keeps exposure to pool assets while earning fees from eligible swaps. The two choices change available wallet balances differently. Distinguish tokens intended for a payment, a governance lock or a direct SHIB burn from tokens allocated to pool liquidity.

Concentrated liquidity adds a price-range decision to the choice of pair and pool. Its custom interval can suit liquidity offered at selected prices, provided the market stays inside that interval for swap-fee earning. A v1 position supplies full-range liquidity and uses fungible LP shares. Neither position type promises that fee income will offset changes in the assets’ relative prices.

Holding the assets directly keeps them outside the pool’s liquidity accounting. It requires no LP share or NFT position to manage. Pool positions earn trading fees when their liquidity participates in swaps. Direct holdings retain the original token balances until another transaction changes them.