Baptswap Documentation
ProtocolCommunity
  • General Information
    • 👋Introduction to Baptswap
      • Made to Stand Out
    • Get Started on Aptos
      • Create a Wallet
      • Get Aptos Coins
      • Connect Your Wallet to Baptswap
    • Create Your Own Token
  • Baptswap Concepts
    • 🧬Concepts
      • 🔄Exchange
        • How to Trade
        • Liquidity Pools
          • How to Add/Remove Liquidity
      • 💸Fee-on-Transfer
        • Fee-on-Transfer Glossary
      • 🥩Reward Pools
      • 🚀Token Deployer Tool
      • 🪙The BAPT Token
  • Socials
    • Contact Us
    • Careers
    • Click Here For Help
      • Troubleshooting Errors
      • General FAQ
  • Technical References
    • Smart Contracts
    • Technical References
      • Protocol Overview
        • How Baptswap Works
        • Ecosystem Participants of Baptswap
        • Smart Contracts
        • Glossary
      • Core Concepts
        • Swaps
        • Pools
        • Flash Swaps
      • Advanced Topics
        • Fee Structure on Baptswap
        • Understanding Returns
        • Copy of Security
    • Tokenomics
      • Governance
    • Token Integration Issues
    • API
      • Subgraph
    • Security
  • Legal
    • Terms of Use
    • Legal Disclaimer
    • Brand And Logos
Powered by GitBook
On this page
  1. Technical References

Token Integration Issues

Fee-on-transfer tokens will not function on the future v3 contracts.

PreviousGovernanceNextAPI

Last updated 1 year ago

Fee-on-transfer Tokens

Fee-on-transfer tokens will not function with our router future v3 contracts. As a workaround, the token creators may create a customized router. We will not be making a router that supports fee-on-transfer tokens in the future for v3.

However, the fee-on-transfer support will continue on the v2 contracts. The v2 contracts will still be available on Baptswap after the implementation of the future v3 contracts, where the two concepts will work seamlessly alongside each other within the same protocol.

​