ClioswapClioswap connects cross-chain asset swaps through Maya Protocol
Clioswap is a crypto swap interface built on Maya Protocol for exchanging supported assets across blockchain networks. A swap sends the selected asset into the protocol and delivers the output to a destination address. Available liquidity, network status, transaction fees, and any affiliate charge affect execution. Compare quotes by the amount received after fees, and verify completion through the confirmed destination transfer. A successful source transaction alone does not establish that the receiving wallet has its funds.
Updated:
Wallet Funding and Destination Readiness
A cross-chain swap requires a supported input asset, enough funds for the source transaction fee, and a receiving address compatible with the selected output network. The wallet must support the transaction that the interface prepares. A matching ticker does not establish network compatibility; the asset and its chain belong together in the selection.
The source wallet authorizes the outgoing transfer. Maya Protocol then processes the swap and sends the output to the specified destination. Completion requires the intended asset to arrive at the intended address on the intended network.
Pool Liquidity and Native Asset Delivery
Maya Protocol exchanges native assets through liquidity pools, allowing supported cross-chain trades without requiring the recipient to accept a wrapped substitute for the selected native output. The available route depends on the protocol’s pools and network conditions. A token appearing in a wallet does not establish that a usable swap pool exists.
Pool availability also differs from chain availability. A network halt can interrupt an otherwise supported route, and the effect depends on which operation stops. A signing halt queues outbound transfers; broader halts can stop trading or observation. Do not send funds while the relevant chain or swap operation is halted; transfers may be delayed or refunded.
What Determines the Amount Received From a Swap?
The amount received reflects pool pricing, liquidity fees, outbound costs, and any affiliate fee included in the transaction, while the source wallet also pays its network fee.
Charges at Different Parts of the Transfer
The fee components have different causes, so an interface percentage cannot describe the complete cost. A reward associated with a swap also belongs in a separate calculation until it becomes a usable balance.
Source and Destination Network Costs
The inbound fee pays for sending funds on the starting network. The outbound charge covers delivery from the protocol. These costs respond to their respective networks, and the outbound charge reduces the swap output. Compare amounts on the same basis to avoid subtracting a fee twice.
Liquidity and Affiliate Charges
Maya Protocol’s liquidity fee depends on the swap size relative to pool depth. An affiliate charge is a separate component that an interface can include. Neither establishes a permanent total fee for every transaction.
Small swaps can leave too little value after delivery costs. A refund also incurs a return transfer charge, so an unsuccessful swap need not restore the entire starting amount. The quote’s recommended minimum accounts for delivery and refund costs; it is specific to the requested swap.
Fresh Quotes and the Commitment Boundary
A fresh quote connects the selected assets and amount to the protocol’s current receiving address, estimated output, and transaction instructions before the wallet authorizes a transfer.
Protocol receiving addresses can change. Reusing an address copied from an earlier swap can send funds somewhere the active route no longer accepts. The transaction memo also carries the requested operation and destination, so a plain transfer to a remembered address does not reproduce the original swap.
A minimum-output limit constrains acceptable execution when the transaction includes it. An estimate alone provides no equivalent protection. Read the limit alongside the quoted output and included fees before authorizing the swap.
The reader can abandon the transfer before signing. Once the wallet signs and broadcasts it, closing the interface does not recall the transaction. Any subsequent recovery depends on the transaction state and applicable protocol behavior.
Destination Confirmation and Transfer Delays
A destination receipt establishes delivery, while source confirmation, protocol observation, and outbound scheduling describe earlier stages that can each contribute to the total wait.
Inbound Confirmation and Protocol Processing
The starting blockchain must include the incoming transaction, and protocol nodes must observe it. Additional confirmation requirements can delay processing to reduce exposure to chain reorganizations. The amount involved and the chain’s behavior affect this interval.
Outbound Scheduling and Receipt
The protocol may schedule an outbound transfer before broadcasting it. The receiving blockchain then needs to confirm that transfer. An elapsed estimate does not establish failure, and sending again can create a second swap while the first remains pending.
Retain the source transaction identifier and the associated outbound record. Those records connect the funds that left the wallet with their destination transfer or refund. A balance display alone can obscure that connection when the wallet contains other transactions.
A Swap Checked Across Both Wallet Records
Consider a hypothetical swap with available pools for the selected input and output assets, active source and destination networks, a compatible receiving address, sufficient network-fee funds, and a quote whose output meets the reader’s chosen minimum. These are assumed conditions for this example, not a claim about a currently available route.
The reader records the selected asset, destination network, quoted output, minimum output, and receiving wallet’s starting balance. Before signing, the wallet’s proposed transaction must agree with those selections. A different destination or missing limit stops the attempt while the funds remain uncommitted.
In this example, the details agree, and the reader authorizes the transfer. The source transaction confirms, while the outbound transfer initially remains pending. The expected result is a destination receipt; the observed result at this point is only a confirmed payment into the protocol.
The outbound transfer later confirms at the intended address. Its asset and amount match the completed swap record and satisfy the chosen minimum. The receiving balance reflects that transfer, with unrelated wallet activity accounted for separately. With delivery verified, the reader does not submit another swap. The source record and destination receipt now explain both sides of the exchange.
Alternative Interfaces and Shared Protocol Constraints
Another Maya-connected interface can differ in wallet support, affiliate charges, and presentation while relying on the same underlying pools and network controls. Changing the interface does not remove a protocol halt or replenish a shallow pool.
Execution choices can also differ. Maya Protocol supports streaming swaps, which divide a trade into smaller parts and allow pool rebalancing between them. Where an interface exposes this option, the potential reduction in liquidity costs comes with a longer execution period. The protocol sends the accumulated output after processing the stream.
A custodial exchange introduces a different arrangement: deposits enter an account, trading happens within that service, and withdrawals follow its rules. For a direct wallet-to-wallet exchange, compare the executable output, receiving network, and custody arrangement. An advertised interface fee alone does not resolve that choice.
Helpful answers about Clioswap
Must I Hold CACAO Before Using a Maya-based Swap?
Maya Protocol does not require users to hold CACAO simply to exchange other supported assets. The starting wallet still needs the funds required to send its transaction, including the applicable source-network fee.
Can a Streaming Swap Return Both the Requested Asset and Part of the Original Asset?
A partially executed Maya streaming swap can deliver successfully swapped output and refund the input that did not swap. The protocol tracks successful and unsuccessful portions during execution. Receiving both assets therefore can reflect partial execution rather than two unrelated transfers. Applicable transfer fees still affect the amounts returned.
Where Does a Maya Swap Refund Go?
Maya Protocol defaults to returning a swap refund to the original sender, although supported transaction instructions can specify a custom refund address. The actual transaction determines which address applies. This matters when the sending address belongs to a service rather than a wallet under the user’s direct control.
Does a Swap Reward Mean That No Gas Was Paid?
A swap reward does not erase the network fee paid when sending the transaction. Clioswap describes a separate reward mechanism associated with gas and affiliate costs. A displayed reward, a claimable balance, and received reward tokens are different states, so reward accounting should remain separate from the swap’s destination receipt.
Which Transaction Details Help Explain a Missing Destination Balance?
The source transaction identifier, intended destination address, output asset, and associated outbound transaction help distinguish an unfinished transfer from a wallet display issue. Maya’s transaction explorer supports tracking swaps and network status. A confirmed outbound record identifies the receiving address and asset more precisely than a general success message.