Maya Protocol: native-asset cross-chain swaps, CACAO fees and settlement

Maya Protocol—often referenced as MAYAChain—is an independent decentralized cross-chain liquidity protocol, not the similarly named Mayan Finance product already covered elsewhere in FXBrokers.ai. It uses native protocol liquidity and CACAO as a settlement/routing asset so a user can swap supported assets on distinct chains without a centrally hosted crypto exchange balance. The swap passes through protocol pool pricing, blockchain vault operations and outbound delivery; supported asset status and pool reserves determine what the network can actually execute.[2][6][7][5]

This is not the same as a bridged-token IOU swap or a single-chain AMM with an external wrapped asset. The documented design moves economic value through the protocol’s liquidity accounting and the validator network’s observed inbound/outbound transactions. A user chooses source chain, input asset, destination chain and receiving address. If a chain is unavailable, a pool suspended or a gas balance insufficient, the nominal route can fail even when a third-party aggregator lists the corresponding token symbols.[2][6][7][5]

MAYAChain documents several distinct cost mechanisms: an inbound fee for the source chain, liquidity/slip cost when the exchange crosses pool reserves, an optional affiliate fee where a front end routes its referral, and an outbound fee on the destination chain. Pool slip is related to trade size against available pool depth, so a percentage observed on a small transaction should not be extrapolated to a large one. A front end may label its service fee separately; the quote should display final received units rather than only a nominal midmarket value.[3][4][5]

The streaming-swap documentation cites potentially lower execution fees, including a minimum on the order of five basis points under certain routes, but that is not a universal total trade fee or a guarantee of zero gas. Breaking a large transaction into multiple parts can reduce pool price impact while increasing time and exposure to changing conditions. The correct all-in measurement is source tokens committed compared with destination tokens actually delivered, adjusted for market exchange rate at the time, the chosen affiliate route and both chains’ network costs.[3][4][5]

Funding a Maya trade means sending an approved source-chain asset to the proper protocol vault/router with the correct memo or transaction parameters. A bank transfer or card purchase is not a native MAYAChain customer funding rail. The blockchain sender address, network and asset contract must exactly match the route. Even when the sender wallet is capable of producing a transaction, the protocol can require inbound confirmations before processing and available liquidity in the destination pool before an outbound transfer is constructed.[4][5][6]

The published wait-time guide separates source confirmation, observation, internal exchange and outbound settlement. These phases can total seconds in favorable cases or materially longer during congestion or streaming swaps. The user should not create a second funding transaction merely because a website timer expires; first inspect the source transaction and explorer. On-chain memos, destination addresses and supported chain identifiers require particular care. Wrong-chain or unsupported-asset transfers may not be refundable through community support.[4][5][6]

MAYAChain is not a centralized brokerage app in which users see a segregated custodial ledger balance waiting to be withdrawn. A wallet transfer initiates a protocol-mediated exchange through shared vault and liquidity mechanisms. This introduces chain observer, validator, key-management, pool and economic-security exposures alongside source and destination wallet risks. Control of a private wallet before and after the swap does not eliminate the fact that protocol contracts or vaults handle the asset during execution.[6][2][7]

Liquidity providers deposit assets into protocol pools and take on inventory rebalancing, impermanent-loss-like exposure and price-deviation effects. The underlying security asset CACAO has its own volatility and incentive role. The existence of public blockchain records and open-source contracts is useful for verification but not evidence of risk-free reserve coverage, an independent financial-statement audit or guaranteed redemption. A chain failure, malicious token issuer, network halt or pool suspension can prevent the expected outcome.[6][2][7]

Technically anyone with an appropriate supported-chain wallet may be able to construct a Maya swap, but that does not establish lawful service availability in every jurisdiction. The protocol’s active pools, chain halts and available integrations determine whether a user can complete a specific route at that time. A community front end may also have separate country restrictions. Different chains require native gas or appropriate spending permissions and can have very different confirmation times.[2][5][7]

An OTC institution or retail user should not assume that Maya offers a local-currency bank account, regulated client segregation or fiat settlement. Interface quote differences can arise from affiliate settings, route selection and slippage constraints, making a cross-site fee comparison difficult without matching source asset, quantity, timestamp and destination. A supported token is not a due-diligence endorsement of the asset issuer or its tokenomics.[2][5][7]

The first investigation step for a missing output is not to assume a swap failed. Check the source transaction hash and the protocol explorer, confirm that an inbound transaction was observed, identify whether the swap is waiting for pool execution and then find the destination outbound transaction. Streaming orders require checking partial progress rather than only a single fill. Timeouts, suspended pools and chain congestion can produce statuses that look like failures in a generic wallet interface.[4][5][7]

Community/project support can guide users through published steps but generally cannot reverse final source-chain settlement or reissue a missing private key. Preserve source and destination hashes, memo, amount, token identifier, timestamp, wallet address, UI quote and routing service if one was used. Do not provide a mnemonic or signing key to a supposed recovery agent. There is no researched guaranteed deadline or monetary compensation standard for all failures.[4][5][7]

Maya Protocol is a decentralized exchange protocol that relies on validator operations rather than a universally identified customer contracting company. Neither its published technical material nor an individual community interface establishes a matched regulator licence number for bank deposits, custodial exchange balances or derivatives products. No issuer-level official legal entity is invented for the structured profile. One app may be built by a registered company elsewhere, but that is not evidence that the underlying protocol itself is authorized to take retail fiat deposits.[2][6]

Local crypto transfer, promotion, financial-instrument and tax rules can still apply to participants and commercial interface providers. Describing MAYAChain as decentralized does not mean security or legal obligations disappear. Likewise, comparing its onchain swaps to Mayan Finance without name disambiguation can produce an accidental duplicate: they use distinct protocols and brands, and this profile records that difference explicitly.[2][6]

The brand refers to MAYAChain, its CACAO security/routing asset and a decentralized liquidity protocol. There is no confirmed single incorporated global operator that can truthfully be listed as counterparty to every swap, so no fictitious legal entity is supplied. This is an editorially independent subject from Mayan Finance, which has a separate trading interface and protocols. The company/brand naming distinction is preserved in the title, metadata and research ledger so future packs do not conflate them.[2][6][7]

Operator

MAYAChain distributed validator network

Exchange model

Decentralised

Service scope

Decentralized layer-1 cross-chain swaps between supported native assets, bridged through CACAO and validator-managed liquidity pools. Distinct from the previously profiled Mayan Finance cross-chain swap application.

Client types

Retail clients; Professional clients

Pricing publication

Public and quoted pricing

Other names

MAYAChain; Maya

Headquarters

Distributed protocol

Pricing scope

Inbound network charges, size-sensitive liquidity/slippage fee, optional affiliate fee and outbound destination gas; quote-based. Streaming swaps alter execution path and minimum advertised bps is conditional.

Funding scope

Direct supported blockchain wallet sends/receives, including required network gas, memo/route and liquidity conditions. No direct GBP/EUR/USD fiat funding established.

Custody and asset handling

Assets interact with protocol vaults and liquidity pool/validator mechanisms during cross-chain settlement; self-custody wallet inputs, not a hosted custodial customer balance. Protocol and consensus failure risk remains.

Client eligibility

Users with supported-chain wallets and allowed assets may use protocol interfaces subject to local law, pool status, liquidity and compatible wallet security. No fiat bank onboarding established.

Support

Protocol documentation, community/developer channels and blockchain transaction explorers; no centralized bank chargeback or discretionary refund guarantee.

Authorisation and registration scope

Decentralized open blockchain exchange architecture; no named universal licensed exchange counterparty or matched regulator number verified. Validator ecosystem is not a bank-deposit protection scheme.

Exchange metadata checked 26 Oct 2026Source 1Source 2Source 3Source 4Source 5Source 6Source 7Source 8

A centralized book can show a ladder of bids and asks while a Maya route quotes a pool-calculated exchange rate after traversing CACAO, source/destination costs and optional streaming. A quoted output is a conditional calculation, not an unconditional promise to pay. In thin liquidity, splitting execution may improve effective output but lengthen duration; price drift can reverse that advantage. Compare live estimates using exactly the same asset, destination and net output rather than a generic advertised fee percentage.[3][4][6]

Users should preserve both inbound and outbound blockchain records for tax reconciliation, as the wallet may show separate chain events rather than a single familiar exchange fill. Protocol oracles, validators and smart-contract security are materially different from the solvency and client-money risk of a centralized exchange. The review does not imply a tested swap or independently audited lifetime volume rank; it describes the published protocol mechanics as of 26 October 2026.[3][4][6]