Skip to the article
Tokenbearing

Crypto protocols, markets and policy

TeleSwap approval is limited to a token and spender

A TeleSwap approval is scoped to a token, chain and spender; an unlimited ERC-20 allowance can expose that token’s full balance, but not every asset.

Tokenbearing Editorial5 min read#9fceed

TeleSwap approval is limited to a token and spender

No: a teleswap approval does not give one contract permission to spend every asset in your wallet. For an ERC-20 token, an approval records an allowance for a specific spender on a specific chain. If that allowance is unlimited, the spender may be able to move the full balance of that token held by your address on that chain, subject to the token contract’s rules.

TeleSwap’s published unwrap flow describes checking the allowance and requesting an approval for the amount when the existing allowance is too low. The contract address comes from the transaction inputs; the documented flow uses a BurnRouter on base networks or an EthConnector on cross-chain routes. The protocol’s own teleswap.net reference is useful context, but the wallet confirmation is where you inspect the actual chain, token, spender and amount before signing.

What does a TeleSwap approval authorize?

A TeleSwap ERC-20 approval authorizes one spender address to transfer one token from your address on one EVM network, up to the remaining allowance. In the standard ERC-20 flow, the token contract stores that allowance when you call approve(spender, amount). The approved contract can later call transferFrom to move the token within that limit.

The allowance is separate from a wallet connection and from the swap or unwrap transaction. Connecting a wallet exposes its public address and lets an application prepare requests; it does not itself create an ERC-20 allowance. The approval transaction changes token-contract state. The later TeleSwap transaction uses the permission to take the specified input token as part of the operation.

Scope matters. An allowance for USDT does not authorize a transfer of USDC, ETH or an NFT. An allowance on one EVM chain does not apply to the same token contract on another chain. Nor does an ERC-20 approval grant access to Bitcoin held at a Bitcoin address. TeleSwap’s BTC-to-EVM wrap flow has a different signing path; the ERC-20 allowance question concerns token input on the EVM side, such as an unwrap.

Can an unlimited allowance still expose my whole balance?

Yes, but only the approved token within that allowance’s scope. An unlimited allowance is a very large spending limit, commonly represented by the maximum value an ERC-20 contract accepts. If the spender remains able to use it, it may transfer the entire balance of that token from your address, even if the balance grows after approval. It cannot use that allowance to take unrelated tokens or native ETH.

A finite allowance limits the amount the spender can transfer in total before another approval is needed. If you approve only the amount required for a transaction, the permission does not automatically expand to cover later deposits. The trade-off is another approval transaction, and its network fee, if you later want to spend more. If an allowance is set higher than the transaction amount, the unused portion can remain active after the swap.

TeleSwap’s published CLI flow says it checks the existing allowance and approves the transaction amount when the allowance is short. That describes the CLI implementation; it does not establish what every wallet interface, route or version of the web application will request. Read the amount shown in the wallet prompt rather than assuming the requested limit from the product name.

Which details should I check before signing?

Check the token, network, spender address and allowance amount in the wallet’s approval screen. These details determine what the approval can do. For an unwrap, the input token and source network should match the route you selected, and the spender should match the contract indicated by the transaction request. If the wallet does not show enough information to identify these fields, do not infer them from a logo or a connected-site name.

  • Token: Confirm the contract address or verified token identity, not just its ticker.
  • Network: Confirm the chain selected for the approval; allowances are recorded on-chain.
  • Spender: Check the contract address that receives permission. An application name is not the spender.
  • Amount: Prefer a limit that covers the intended transaction without leaving a larger allowance than you want.

Approvals also persist independently of whether the application remains open. Completing an unwrap does not necessarily clear unused allowance, and disconnecting a wallet does not revoke on-chain permission. You can inspect and revoke an allowance with a wallet or chain tool that reads token approvals; revoking generally requires a new transaction and network fee. A revoked or depleted allowance must be set again before a later transaction can use that token.

What is the practical answer for a TeleSwap user?

A TeleSwap approval is not a blanket wallet permission. Its reach is bounded by the approved token, the chain and the named spender. The meaningful edge case is an unlimited or oversized allowance: it can leave that spender able to move more of the approved token than the current transaction needs. For most users, the tighter choice is the smallest allowance that covers the planned operation, provided the wallet exposes a clear amount and the request matches the intended route.

What remains route-specific is the exact contract address and amount presented at signing. Those are transaction details, not properties that can be established from the word “TeleSwap” alone. Review the live wallet prompt each time; the approval screen determines the permission you are actually granting.