Maya Protocol (CACAO)

Maya Protocol (CACAO): Native Cross-Chain Swaps Without Wrapped Assets

Maya Protocol is a Cosmos SDK-based decentralised liquidity protocol designed to let users exchange native assets across blockchains without custodial intermediaries, bridges, or wrapped representations. Its stated design is closely related to THORChain while adding a feature called Liquidity Nodes.

Maya Protocol’s role in cross-chain liquidity

Maya Protocol is recorded as a decentralised finance protocol, a smart contract platform, and a Layer 1 project. Its stated purpose is to provide liquidity for swaps between native assets held on different blockchains. Rather than limiting users to tokens issued on one network, Maya describes a system for exchanging the underlying assets themselves across supported chains.

The project describes itself as a Cosmos SDK-based protocol and a friendly fork of THORChain. That relationship is presented as a design starting point rather than proof that every component or operational detail is identical. Maya says it maintains backward compatibility with THORChain while adding features of its own, including Liquidity Nodes.

How Maya describes its native-asset swap model

The central design claim is that Maya does not peg or wrap assets and does not rely on bridges. In this model, a user is intended to swap native assets rather than receiving a synthetic or wrapped version that represents an asset locked elsewhere. This distinction matters because the user’s exposure is tied to the protocol’s cross-chain swap process rather than to a separate wrapped-token issuer or bridge contract.

Maya also describes the swap process as non-custodial and permissionless. The stated user model is self-custody: participants retain control of their assets until they submit a transaction, while the protocol coordinates liquidity across chains. The description does not specify the complete transaction sequence, supported assets, settlement rules, fee structure, or the conditions under which a swap may fail, so those practical details require separate confirmation.

Liquidity Nodes and the protocol’s relationship with THORChain

Liquidity Nodes are the main project-specific addition named in the description. Maya presents them as a feature intended to complement the THORChain-derived design, but public materials does not explain their architecture, responsibilities, eligibility requirements, rewards, or relationship to liquidity providers. It therefore remains unclear from this record how Liquidity Nodes affect liquidity depth, transaction execution, network security, or governance.

The project’s stated backward compatibility with THORChain suggests an intention to preserve familiarity or interoperability with parts of that ecosystem. However, project materials does not identify particular THORChain integrations, shared infrastructure, formal partnerships, or technical compatibility guarantees. Those distinctions matter when assessing how much of Maya’s operating model is inherited and how much is specific to Maya Protocol.

CACAO’s stated place in the ecosystem

CACAO is the protocol’s named token symbol, but project materials does not assign it a specific function. It does not say whether CACAO is used for transaction fees, liquidity incentives, node operation, governance, settlement, collateral, or another purpose. Readers should therefore separate the existence of the token from any assumption about utility.

The same limitation applies to the intended participant groups. Maya’s non-custodial and permissionless positioning points toward users seeking cross-chain swaps and operators or providers supporting protocol liquidity, but the description does not define those roles in operational terms. It also does not identify supported blockchain networks, token pairs, deployment dates, supply rules, issuance mechanics, or distribution arrangements.

Self-custody claims and operational dependencies

Maya says its design can reduce exposure to centralised and counterparty risks by avoiding custodial control, bridges, and wrapped assets. These are project claims about the intended risk profile, not a guarantee that the protocol has no material dependencies. A cross-chain swap system can still depend on its code, validators or node operators, liquidity availability, supported-chain reliability, transaction finality, and the accuracy of its routing and settlement logic.

public materials does not state that Maya has completed an audit, obtained legal approval, undergone a security review, or demonstrated a particular level of adoption. It also does not describe incident history, governance processes, emergency controls, or recovery procedures. These omissions are especially relevant for a protocol that coordinates transactions across multiple blockchain environments.

Recorded historical context for CACAO

YearBull’s recorded observation window runs from 30 December 2025 to 14 September 2026, with 254 observations. During that window, the token’s 30-day recorded return was 0% and its 90-day recorded return was 5.07%; these are historical observations, not forecasts or explanations of the project’s performance.

The token reached a best sequential rank of 5 and a worst sequential rank of 2,098 in the recorded series. Its average Bull Score was 57.5, the dominant cycle label was Early, and the recorded drawdown from the window high was 20.33%. These observations describe market behaviour in the specified period only. They do not establish the success of Maya’s cross-chain mechanism, the quality of its liquidity, or the practical value of CACAO’s currently unspecified role.

Key takeaways

• Maya Protocol describes a Cosmos SDK-based system for native cross-chain swaps without wrapped assets or bridges.
• The project presents its model as non-custodial, permissionless, and compatible with self-custody.
• Maya identifies Liquidity Nodes as a feature added to its THORChain-derived design, but their operation is not explained in public materials.
• CACAO is the named token, while its utility, supply model, distribution, and role in network activity remain unspecified.
• The project’s claims about reduced centralised and counterparty exposure do not remove dependencies on code, liquidity, node operations, and supported chains.
• Recorded market observations provide context for CACAO but do not verify the protocol’s technical or economic claims.

Risks and unresolved questions

• The description does not identify supported blockchain networks, native assets, swap routes, settlement mechanics, or transaction failure procedures.
• Liquidity Nodes are named but their technical function, incentives, operator requirements, and effect on security or liquidity are not documented here.
• CACAO’s utility, issuance, supply, allocation, governance role, and relationship to fees or liquidity remain unresolved.
• No audit, security assessment, incident history, governance process, or emergency response model is stated.
• The protocol may depend on available liquidity, node performance, supported-chain finality, and the reliability of cross-chain transaction coordination.