# Transaction times and fees ## Fees Squid currently charges no fees. The user will only pay gas fees on source and destination chains. It is possible for our partners to charge fees via our SDK or API. Partners can elect a % fee they would like to charge, and Squid will receive a portion of this fee. ### Source Chain transactions #### EVM Fees are comprised of the following and are paid in Native Gas * Gas amount needed for any swaps, approvals and transfers * If the "from token" is the Native gas token, this amount is also added to the gas payment * The execution fees for the destination chain #### Cosmos Cosmos transactions are different to EVM transaction as the destination chain gas fees are taken out of the bridge token. e.g for a route that is Osmo:Osmosis > ETH:Ethereum, usually the bridge token will be axlUSDC, and this is where the GMP (bridge) fee will be taken from. If the route is axlWETH > WETH the fee will be taken in WETH.\ Gas payment for source chain will be only the amount needed for the execution on the Cosmos chain, all IBC relaying comes at 0 cost. ### General message passing fees (swap on destination chain) Just like the source chain transactions, the amount gas charged is calculated base off how many swaps, transfers and approvals there are. For transactions where there is a swap on the destination chain, fees are paid using the Native token on the source chain. This fee is paid to Axelar's relayers, who trustlessly pass messages and proofs across chains. Axelar's relayers hold gas on every chain and provide a pricing API which Squid calls to get the expected gas price for a trade. For example if the destination trade will probably cost 50 cents of AVAX in gas, then Squid will instruct the user to pay Axelar's gas service 50 cents worth of Moonbeam, as per the pricing which Axelar gives our backend. ### CCTP Noble Fees CCTP bridge is not considered a transfer and there is no fee for this. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.squidrouter.com/additional-resources/architecture/transaction-times-and-fees.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.