Arbitrage Ape is a liquidity desk operating on the Robinhood Chain (EIP-155 chain ID 4663), as stated on its official website and corroborated by third-party API sources. Its native token $AA is deployed at 0xe2dae1c072b9f66bed999873b94798b2152af7e1, viewable on the Robinhood Chain Blockscout explorer. According to its site, the desk runs concentrated-liquidity bands on high-flow token launches, earns pool fees, tracks band principal gains or losses separately, and distributes 60% of the accumulated ‘holder pot’—denominated in USDG—to $AA holders once at least $3,000 is owed; the remaining 40% serves as a reserve. The system claims all operations—including indexing swaps from its own node, minting bands, sweeping fees, closing bands upon price breaches, and payouts—are executed on-chain. The project describes itself as a self-custodial, on-chain liquidity operation where capital remains in a vault controlled by a keeper address (0x0feb08fcf34f5c0e270261bc79bafc0f8eb87f98). Key evaluation questions include: Does the on-chain architecture actually isolate holder payouts from band principal risk, as claimed? What legal or operational recourse exists if the keeper fails to execute payouts, alters payout logic, or misuses the vault? How is the ‘holder pot’ defined and verified on-chain versus off-chain reporting?
Arbitrage Ape positions itself as an on-chain liquidity desk running concentrated-liquidity bands on Robinhood Chain, with payouts to $AA token holders funded from a 60/40 split of a ‘holder pot’—comprising fees, fee-token sales proceeds, and desk trading gains. The mechanism explicitly excludes band principal (i.e., capital gains/losses from the band’s own position) from payouts, assigning losses to fund equity instead. However, no evidence confirms operational execution: the live dashboard at arbitrageape.app shows only placeholder states (‘Waiting for the desk’s first fills…’, ‘Tape loading…’) and no historical payouts, marks, or filled bands as of October 2026. The contract address is verified on Blockscout, but no transaction history, liquidity events, or vault activity is cited or linked in the supplied sources. Claims about custody (‘capital stays in the vault’), oracle use (‘own node indexes every swap’), and payout automation (‘keeper checks every 15 seconds’) remain unverified assertions. No audit, technical documentation, or repository is provided. Market data from API sources reports full token supply and circulating supply but lacks price, volume, or on-chain activity metrics. The absence of verifiable on-chain execution or third-party validation means the core thesis—that this is a functioning, capital-efficient liquidity operation—lacks primary supporting evidence.
What happens if a band loses more than the 40% reserve holds? Losses exceed the reserve, the fund’s equity absorbs them—and the ledger claims to show this transparently. But without any recorded equity marks or realized losses, that claim is untested.
Is USDG truly redeemable on demand? The site states payouts go to holders ‘in USDG’, but USDG is not described, audited, or linked; its stability mechanism, backing, or redemption terms are absent from all sources.
Overall score: 5/10 Confidence: Low