Maya Protocol / MAYAChain
MAYAChain is Maya Protocol’s decentralized cross-chain liquidity network for native-asset swaps. On August 18, 2026, an attacker chained multiple accounting and state-handling flaws in a single batched transaction, created an unfunded balance in a thin liquidity pool and extracted Bitcoin and other assets. MAYAChain trading was halted while fixes and recovery work proceeded.
Bridge facts
- Canonical name
- Maya Protocol / MAYAChain
- Type
- Interoperability Protocol
- Status
- Paused
- Confidence
- High
- Primary chains
- Bitcoin, Ethereum, Arbitrum, Unknown
- Primary assets
- BTC, ETH, Unknown
- Operator
- Maya Protocol contributors / MAYAChain node operators
- Ecosystem
- Maya Protocol
- Launch date
- Unknown
- End date
- Unknown
- Terminal reason
- Not applicable / unknown
- Last reviewed
- 2026-09-09
- Last verified
- 2026-09-09
Incident cases
MAYAChain 2026 chained accounting exploit2026-08-18
On August 18, 2026, an attacker used a single transaction containing 23 messages to chain multiple MAYAChain accounting and state-handling defects. The sequence triggered a false theft condition and an unfunded slash-subsidy credit in the thin ARB.LINK pool, after which the attacker gained near-total pool ownership and extracted Bitcoin and other assets. Maya halted MAYAChain trading for containment and recovery work.
Evidence records
- MAYAChain IntroductionMaya Protocol · Tier 1 · Unknown
- Maya Protocol exploit drains bitcoin and other assets as pool value drops by $11 millionCoinDesk · Tier 1 · 2026-08-19
- Web3 Security: Term Finance & MAYAChain ExploitsBlockSec · Tier 1 · 2026-08-25
- harden outbound matching, native txID uniqueness and theft-slash subsidyMaya Protocol / MAYANode · Tier 1 · 2026-08-18
Official URL status
Official URL recorded as live: https://docs.mayaprotocol.com/mayachain-dev-docs/introductionHelp maintain bridge history
Support incident linkage, lifecycle updates, evidence preservation, broken-link replacement, and corrections.
Report a correction
Report missing evidence, incorrect dates, outcome changes, recovery details, reimbursement status, or broken links. GitHub Issues are preferred for structured review; the Google Form is available if you do not use GitHub.