Mole

Mole is a cross-chain lending and yield protocol focused on Move ecosystems (Sui and Aptos), offering money-market style deposits, borrowing and leveraged strategies. 1. Basic identification

• Name: Mole Finance (often “Mole” or “Mole.fi”).
• Website: mole.fi (primary UI).
• Docs: docs.mole.fi (technical & user docs).
• Category: DeFi lending / money market plus yield strategy layer on Sui and Aptos.
• Chains: Sui and Aptos only, per docs and ecosystem listings.
• Native token: A governance / incentive token generally referred to as MOLE; token contracts differ per chain (no unified ERC‑20 standard here). Exact token contract addresses are not independently standardized across sources; Not verifiable as of 2026-08-29.
• Launch date: External ecosystem posts and Mole docs suggest mainnet launch in mid‑2024 for Sui and later 2024 for Aptos, but specific block‑timestamped launch dates cannot be independently pinned; Not verifiable as of 2026-08-29. 2. Chains and contract identification Because direct on‑chain/Dune inspection is disabled in this run, contract‑level identification is limited to explorer/analytics + project docs:
• Sui: Mole is listed as a lending protocol in Sui ecosystem overviews and DeFi aggregators, but top‑level “main contract” package IDs (lending pool, comptroller, interest rate model) are not consistently published across independent sources; Not verifiable as of 2026-08-29.
• Aptos: Similarly, Aptos explorers and DeFi listings show Mole activity, but do not converge on a single canonical package ID set for core lending markets; Not verifiable as of 2026-08-29.
• Explorer verification status: Both Sui and Aptos ecosystems support Move module verification, but there is no consistent, third‑party‑verified contract map for Mole beyond Mole’s own docs and UI; all such mappings are therefore unverified marketing claims as of 2026-08-29. 3. Fork lineage and code provenance
• Public docs and ecosystem write‑ups describe Mole as a compound‑style lending market adapted to Move, but do not clearly state it is a direct fork of any named upstream (e.g., Compound, Aave) nor provide a formal fork disclosure.
• No independent audit report specifically mapping Mole’s contracts to a known upstream fork and detailing deltas was found; Not verifiable as of 2026-08-29.
• No records of malicious modifications in Mole forks or incident reports tied to Mole-derived forks were identified in security advisories or major DeFi media; Not verifiable as of 2026-08-29. Given missing on‑chain and audit transparency in public sources, most fine‑grained lineage and contract mapping details remain Not verifiable as of 2026-08-29 and should be treated as unresolved risk items.

Mole’s public presence looks more like an early-stage product site plus repository footprint than a fully mature, self-service yield portal. The strongest verifiable signal is that the project has an active GitHub organization and protocol repository with Sui and Aptos mainnet config files, which suggests real deployment work rather than a pure marketing landing page. What is verifiable:

• There is repository evidence for both Sui and Aptos mainnet configuration files and a protocol codebase, indicating multi-chain support work.
• The project has a GitHub organization with multiple related repos, which is consistent with an operating development effort.
• An audit report references Mole documentation and describes Vault/Fund deposit and withdraw functionality in the protocol design, so the product concept includes live asset flows. What is not verifiable as of 2026-08-29:
• Live user deposits/withdrawals on the website or whether the public portal currently executes them.
• Whether the site is a functional app versus a landing page with embedded docs only.
• Broken links, fake TVL/holder metrics, or template/clone signs from the website itself.
• Whether Mole exposes an open public API. Assessment: the available evidence supports that Mole is a real protocol project with code and audit coverage, but the maturity of the public web portal and the existence of a public open API are not verifiable from the gathered sources.

MoveBit audited the Mole Aptos codebase and reported a total of 10 issues: 0 critical, 0 high, 2 medium, and 8 minor. The report states 7 issues were fixed and 3 were pending at the time of publication; the pending issues were all minor. The audit timeline was 2023-02-07 to 2023-03-09, and the reviewed code was the Aptos repository Mole-Fi/mole-protocol-aptos-dev at commit 53c832d7a597324ec571005b4688431fe4a894d7 (received commit e28045f5aa3b5359d6f75ad9ffe117992a5ad9f8). The report covers code reviewed up to that commit, but bytecode-match / deployed-code correspondence is not verifiable as of 2026-08-29 from the available sources.

I could not verify an active bug bounty program for Mole (mole.fi) from the provided web results alone. None of the results identify Mole specifically, and the results that do describe bug bounty programs are about other projects or generic background, not Mole; therefore, the existence, start date, scope/parameters, and results for Mole are Not verifiable as of 2026-08-29. The only defensible answer is that I found no confirmable evidence of an active Mole bug bounty program in the supplied sources. If you want, I can do a tighter cross-check focused on Mole’s own docs, security page, GitHub, and any Immunefi/HackerOne-style listings to verify whether a program exists and extract its rules and payouts.

Mole is a lending protocol on Sui and Aptos with key dependencies around price oracles, stablecoins/LSTs, and chain infrastructure. On‑chain verification is not possible in this run: Not verifiable as of 2026‑08‑29. ### 1. External protocol & oracle dependencies

• Price oracles: Mole integrates Pyth and Switchboard oracles on Sui/Aptos for asset pricing and liquidation logic. This creates:
• Oracle manipulation risk (low‑liquidity markets, latency, publisher failures).
• Dependency on oracle governance (upgrades, parameter changes).
• If an oracle publishes faulty prices or is attacked, Mole can trigger mass liquidations, bad‑debt creation, or under‑collateralized lending. ### 2. Asset-level counterparty risk Mole supports multiple stablecoins and tokens on Sui/Aptos including USDC/USDT bridges, native ecosystem stablecoins, and volatile tokens/LSTs. Key scenarios:
• Stablecoin depeg / issuer insolvency
• USDC/USDT via bridges or wrapped versions depend on Circle/Tether plus bridge operators. Failure of issuer or bridge → collateral value collapse, Mole accrues bad debt.
• Local ecosystem stablecoins (if used, e.g., Sui or Aptos‑native) have algorithmic/governance risk; depeg can wipe out lenders.
• LST / restaking exposure
• If Mole supports staked or restaked assets tied to Sui/Aptos validators, there is slashing, validator failure, or governance risk; price drops drive liquidations and potential bad debt. ### 3. Bridges & chain infrastructure
• Mole is natively deployed on Sui and Aptos, which are themselves dependent on their validators and consensus.
• Any bridge‑based wrapped asset on Mole inherits: bridge smart‑contract risk, multisig compromise, or operator failure.
• Severe bridge incident or chain halt on Sui or Aptos can freeze Mole positions, prevent liquidations, and crystallize losses. ### 4. Custodians, CEX/MM, and RWA
• No evidence Mole directly relies on centralized custodians, CEXs, MMs, or RWA/SPV issuers beyond the issuer/bridge exposure of supported assets.
• RWA usage in Mole is Not verifiable as of 2026‑08‑29. ### 5. Concentration & governance
• Concentration of collateral in a single stablecoin or LST amplifies impact of a depeg/slash event.
• Governance, if using Mole’s token and/or multisig on Sui/Aptos, introduces key‑person and multisig compromise risk; specific setup Not verifiable as of 2026‑08‑29.

Mole’s custody model is smart-contract custody, not a traditional third-party custodian model. According to its docs, users deposit assets into Mole savings pools, and the protocol lends those deposits to leveraged yield-farming users through smart contracts; borrowers cannot withdraw the borrowed tokens to their own wallets and may only use them inside Mole’s contracts. In practice, custody is organized as follows: 1) users deposit tokens into the protocol; 2) the protocol issues a deposit certificate (for example, mETH) representing the user’s claim; 3) the deposited assets are deployed by Mole’s contracts into cooperative DEX liquidity positions, currently described in the docs as Cetus on Sui. The docs also state that Mole uses liquidation logic to protect savings deposits if leveraged positions move against the borrower, and that withdrawals are available with T+0 settlement. What is not verifiable as of 2026-08-29 from the available sources is whether Mole uses any off-chain custodian, multisig-admin arrangement, or formal segregated custody entity on Sui or Aptos; the provided sources only substantiate the protocol-level smart-contract workflow.

Mole’s public materials do not describe a formal cryptographic key-management architecture for the protocol itself. What is documented is that Mole is a DeFi protocol on Sui, and that users can interact with its savings pools, leveraged yield farms, and funds; the docs explain strategy and asset-flow mechanics, but not how protocol keys, admin keys, upgrade keys, or custody keys are organized. Based on the available sources, the only defensible answer is that key management is not verifiable as of 2026-08-29 from the retrieved materials. There is no published evidence here of a multisig, timelock, hardware-security-module setup, role separation, emergency-admin structure, or chain-specific key controls for Sui or Aptos. One important note: the sources also show a possible scope mismatch. The protocol site and docs describe Mole primarily as a Sui protocol, while your query lists Sui, Aptos; I could not verify any Aptos deployment or Aptos-specific key governance from the retrieved material.

Mole appears to be a Sui/Aptos DeFi protocol with public GitHub repos and third-party protocol listings, but the available web evidence is insufficient to fully verify its contract-level control surface. The protocol is described on its own site as providing “savings, leveraged yield farms and funds” on Sui, while third-party listings confirm deployment on Sui and Aptos and show TVL concentrated mostly on Sui. For smart-contract and admin risk, the key point is that the currently gathered sources do not expose a complete, independently verified address-by-address architecture map, proxy pattern, timelock, or on-chain role graph. The Aptos audit summary does state that admins can deposit/withdraw in Vaults, update Vault config, withdraw/reduce reserves, create positions and reinvest in Farming, and deposit/withdraw, rebalance, and reinvest in Funds. That means the worst-case centralized-control risk on Aptos includes admin-triggered asset movement and strategy changes if privileged keys are compromised. However, the on-chain verification status of those roles, any proxy/admin implementation, renounced-role state, and timelock delay is Not verifiable as of 2026-08-29. On the Sui side, the gathered sources only confirm that Mole has a Sui contract repository and that the project is marketed as a Sui DeFi protocol. The contract addresses, verified-module status, upgrade authority, pause/withdrawal controls, oracle hooks, and whether users can exit without admin intervention are Not verifiable as of 2026-08-29. Risk callout: if admin or upgrade keys are compromised, the plausible worst case is malicious config changes, forced strategy changes, reserve withdrawal, or contract upgrade to hostile logic on the components where admins control those functions; whether that extends to a full user freeze or rug is Not verifiable as of 2026-08-29. Architecture map (partial):

• Sui: Mole protocol contracts exist; exact roles and upgrade path not verified
• Aptos: Vault / Farming / Fund components with documented admin permissions
• TVL exposure: mostly Sui, with a much smaller Aptos share I cannot reliably provide a verified diagram, proxy-admin type, or timelock measurement from the gathered sources alone.

Mole on Sui/Aptos appears to be run by a largely anonymous, engineer-led team, with only fragmentary and marketing-style founder information available; nothing resembling a traditional, fully disclosed corporate/team profile can be independently validated. Not verifiable as of 2026-08-29. Founders & team disclosure

• Official docs describe Mole as a DeFi protocol providing savings, leveraged yield farms and funds but do not name any founders or core contributors.
• A DoraHacks hackathon profile for Mole states that “Mole team is composed of a group of engineers… with attainments in encryption algorithms, security and financial technology,” without listing individuals, roles, or biographies.
• The project’s GitHub organization shows no public members, which is consistent with a deliberately non‑disclosed or anonymous dev team. Marketing claim about “Eric” as founder
• A Bitget Wallet dApp listing for Mole states that “The founder, Eric, is a senior blockchain expert and YouTuber,” and attributes prior roles including co‑founding a DEX in Japan (2016), CTO of a decentralized sharing‑economy platform (2017), and later work at a blockchain research institution in Japan leading to creation of Mole.
• This description is not cross‑confirmed by LinkedIn, GitHub, audit reports, or other independent sources, and no matching public persona can be reliably tied to the Mole protocol contracts. As such, this is an unverified marketing claim, not a validated founder profile. Not verifiable as of 2026-08-29. Prior projects, hacks, and credibility
• No independent record of past projects explicitly tied to Mole’s team (e.g., previous DeFi protocols, exchanges, or security incidents) is found in external analytics, media, or audit repositories. Not verifiable as of 2026-08-29.
• No publicly listed audits or bug bounty programs for Mole’s Sui/Aptos deployments are visible in the data examined. Not verifiable as of 2026-08-29. Public vs. anon; office; jurisdiction
• There is no confirmed legal entity, registered office address, or jurisdiction (onshore/offshore) associated with Mole in independent company databases or protocol profiles.
• The available descriptions consistently frame Mole as a DeFi protocol rather than a regulated financial institution or clearly domiciled corporate business. Reality check for institutional use
• Team is effectively anonymous/pseudonymous with no verifiable individuals, track records, or governance structure.
• Corporate setup, jurisdiction, and physical presence are not disclosed and not independently verifiable.
• For institutional risk purposes, Mole should be treated as a purely on-chain, anonymous DeFi project with elevated counterparty/governance risk and no demonstrable off-chain “real business” footprint as of 2026-08-29.

Mole currently has no publicly reported hacks, rugs, or insolvency events, but is a relatively small, new protocol with only moderate external scrutiny and thus non-trivial residual reputation risk. Protocol & product reputation

• Mole is a leveraged yield / savings / fund protocol on Sui and Aptos, integrated with Sui-native protocols like Cetus, Scallop, Bucket, and Haedal.
• Multiple ecosystem overviews (Binance Square, Odaily, Alchemy, The Grid) list Mole as a legitimate Sui/Aptos DeFi protocol and do not flag any incidents or scams.
• Independent DeFi intelligence platforms show TVL around $8.6m, mostly on Sui, and characterize Mole as a yield protocol without known security incidents. Audits & security signaling
• An Aptos-specific audit report is published by MoveBit, covering Mole’s yield farming contracts on Aptos.
• A separate X post celebrates a Beosin audit for “Molecular Protocol ($MOLE)” on Arbitrum, which is a different protocol despite the similar name; this is a name-collision and not a confirmed audit for Mole on Sui/Aptos.
• No evidence from independent sources of completed audits for Sui-side contracts; overall audit coverage appears partial, chain-specific, and not comprehensive. Founders & investors
• A project profile attributes Mole’s founding to “Eric,” described as a senior blockchain expert, YouTuber, and former co-founder/CTO of Japanese crypto and sharing-economy projects, later joining a blockchain research institution in Japan.
• There is no independently verified institutional investor list or formal VC backing disclosed in reputable databases; funding status is unclear. Sentiment, criticisms, and incident history
• Intelligence platforms assign Mole a “B” trust score (64/100) and note “no known security incidents”, but accompany this with standard risk warnings and advice to verify audits.
• Public materials and ecosystem articles do not highlight major criticisms, exploits, governance scandals, or user-loss events.
• Given limited coverage and small TVL, absence of negative news should be treated as limited observability, not proof of robustness. Legal / regulatory / sanctions
• No hits in mainstream crypto news or ecosystem trackers suggesting regulatory actions, sanctions, or fraud investigations related to Mole.
• Formal corporate structure, jurisdiction, and compliance posture are not independently documented, representing an unresolved transparency concern. Key unresolved concerns for institutional risk:
• Partial/opaque audit coverage across chains.
• Limited public information on team identities, governance, and legal entity.
• No on-chain verification available in this run ("Not verifiable as of 2026-08-29").
• Small, emerging protocol with modest trust scores and relatively thin external due diligence.

Mole is a yield-focused DeFi protocol on Sui and Aptos that combines savings, leveraged yield farms, and funds. Independent sources describe it as providing leveraged yield farming, hedge-fund-style strategies, and savings; the protocol’s own site says it offers savings, leveraged yield farms, and funds. Economic model: users deposit assets into savings or farm products; the protocol then deploys those assets into DEX liquidity / farming strategies, with leverage supplied from borrowing pools. The Chinese docs also describe funds flowing from lending pools into leveraged yield farms and then into DEX market-making, indicating a strategy stack built around LP yield capture rather than pure directional speculation. Yield source: primarily trading fees / LP incentives / farming rewards from integrated venues, especially Cetus on Sui, plus borrow-rate spread where savings pools fund leveraged positions. This points to a mix of *organic* yield (swap fees, LP revenue) and *potentially subsidized* yield where external incentives are present; however, the exact subsidy share is Not verifiable as of 2026-08-30. Exposure style: the protocol is best characterized as market-neutral or semi-neutral for some strategies, because the docs emphasize long/short and hedged market-risk approaches, but it also supports leveraged LP/farming, which carries directional and impermanent-loss exposure. Explicit use of restaking is Not verifiable as of 2026-08-30. Lock-ups / withdrawal / fees / gates / limits / protocol revenue / collateral: Not verifiable as of 2026-08-30 from the sources reviewed. The available material does not provide reliable details on withdrawal mechanics, fee schedule, deposit caps, revenue split, or collateral rules. TVL and chain mix: DeFiLlama reports about $8.63m TVL total, with Sui $8.32m and Aptos $306,958; that implies roughly 96.4% Sui and 3.6% Aptos. A second analytics page reports a similar split of Sui ~$8.50m (98.1%) and Aptos ~$161.84k (1.9%), which is directionally consistent but not identical. I cannot reconcile the discrepancy without on-chain verification, so the gap itself is the finding. APY history / volatility / sustainability: the protocol pages reviewed do not provide a trustworthy APY time series. Some third-party descriptions mention high-yield strategies, but APY history and sustainability are Not verifiable as of 2026-08-30. Contradiction callout: the protocol site suggests a broader product set and marketing language around hedging and high returns, while independent sources confirm only the general product categories and TVL; precise economic parameters remain unverified.

Not verifiable as of 2026-08-29. The available web results identify Mole as a DeFi protocol on Sui and Aptos, and DefiLlama reports TVL of $8.63m split across Sui ($8.32m) and Aptos ($306,958), but these are TVL figures, not a treasury/reserves disclosure, and they do not provide reserve addresses, custody arrangement, reserve policy, or attestations. The protocol site itself shows a TVL number of $9,340,720.47, which conflicts with DefiLlama’s figure, but neither source provides a reserve breakdown or on-chain treasury verification here. No Dune on-chain reserve/balance query is available in this run, so on-chain balances, controller addresses, and composition are not verifiable from the provided evidence.

Mole appears to be a points-based DeFi lending protocol on Sui and Aptos without a live fungible governance/utility token as of 2026‑08‑30. Not verifiable as of [2026‑08‑30] via on-chain due to Dune MCP unavailability. ### Existence of native token

• Mole’s site, docs, and recent materials emphasize Mole Points earned via lending/borrowing, campaigns, and referrals, with references to a “future token” or “Mole Token” but no deployed, tradable ERC‑20/Sui/Aptos fungible token is shown.
• No reliable listings on major aggregators (CoinGecko, CoinMarketCap, DefiLlama) for a Mole-branded native token on Sui or Aptos; search results are either unrelated or generic.
• Therefore, as of today: Mole has no verifiably live native token contract on Sui or Aptos suitable for TVL/market-cap style tokenomics analysis. ### Required tokenomics fields (current status) Because no live token is verifiable, the following items are Not verifiable as of [2026‑08‑30]:
• Token name/ticker and contract address: Not verifiable as of [2026‑08‑30].
• Total vs circulating supply; market cap; FDV: Not verifiable as of [2026‑08‑30].
• Token utility and governance role; revenue share; buybacks/burns; staking rewards: Only discussed in broad, future-oriented language as part of Mole Points → token expectations; these are unverified marketing claims.
• Emissions schedule; unlock schedule; whether unlocks occurred on-chain: Not verifiable as of [2026‑08‑30]. No credible vesting/unlock calendar found.
• Allocations to team/investors/treasury/community: Not verifiable as of [2026‑08‑30]. No detailed token distribution published by independent sources.
• Top-holder concentration and insider wallets: Not verifiable as of [2026‑08‑30]. Requires contract existence plus on-chain tooling.
• Mint/blacklist/fee-switch functions and controllers: Not verifiable as of [2026‑08‑30]. No audited token contract. ### DEX liquidity and listings
• No major DEX (Cetus, Kriya, Turbos, Pontem, etc.) shows a Mole-branded fungible token pool with meaningful liquidity on Sui or Aptos in independent analytics.
• Therefore DEX liquidity depth and main listings for a Mole native token are effectively zero/non-existent as of [2026‑08‑30]. Risk takeaway: Mole currently operates more like a points/loyalty-based lending protocol awaiting a future token launch. Any tokenomics descriptions from Mole itself should be treated as unverified marketing claims until a concrete contract address, distribution, and on-chain history are available and independently analyzed.

Under a Bitcoin move below $10,000, the main stress effect on Mole is likely indirect, not protocol-specific: a sharp BTC drawdown would normally reduce risk appetite, DeFi liquidity, and collateral values across crypto markets, which can pressure a yield protocol’s deposits and TVL. However, for Mole itself, the available web data only verifies its current deployment on Sui and Aptos and a TVL concentration of roughly $8.32M on Sui and $306,958 on Aptos; the protocol-level stress outcome under a BTC crash is Not verifiable as of 2026-08-29 from the available sources. The clearest chain exposure is Sui-dominated: about 96.5% of visible TVL is on Sui and about 3.5% on Aptos, so any market shock would likely transmit first through the Sui side of the protocol rather than evenly across both chains. There is no source in the provided results that documents Mole’s collateral composition, liquidation mechanics, hedging design, or BTC-linked exposures, so a direct estimate of losses, insolvency risk, or user withdrawal behavior under BTC < $10,000 is Not verifiable as of 2026-08-29.

Not verifiable as of 2026-08-29. I could not find a source that quantifies Mole’s largest-collateral 20% depeg loss for Sui and Aptos using on-chain data or a protocol risk report. The only Mole-specific result found was DeFiLlama’s aggregate TVL page and a docs page stating that dual-stable token farms are difficult to liquidate except in an extreme black-swan event, but neither provides a 20% collateral-depeg stress number. If you want, I can still give a conservative qualitative read: a 20% depeg in the largest collateral would be a severe stress event for any lending or leveraged-farm design, but for Mole specifically the loss magnitude, insolvency exposure, and chain split between Sui and Aptos are not verifiable from the available sources.

For Mole, a top counterparty insolvency scenario is only partially verifiable from the sources I found, because the docs explain liquidation and fee routing but do not disclose a full default waterfall, backstop fund size, or chain-specific loss socialization rules. The clearest documented path is: if a leveraged position’s debt ratio breaches the liquidation threshold, Mole liquidates the position, returns enough value to the savings pool to keep lender principal safe, and distributes any residual value to the leveraged-yield user after fees.

• Expected loss path: The insolvent counterparty’s position is liquidated; proceeds first satisfy the loan/savings pool, then remaining value goes to the leveraged position after liquidation fees.
• Who absorbs the loss: The docs imply the leveraged position holder absorbs residual losses from adverse price movement; the savings pool is intended to be protected by liquidation mechanics.
• Compensation / recovery: Liquidation fees are charged; one doc says 1% rewards liquidators and 4% goes to the Mole Foundation for ecosystem and security reserve purposes, which may provide operational support but is not explicitly stated as an insured compensation fund.
• Smart-contract impact path: Price move → debt ratio rises → liquidation threshold breached → Mole liquidates → debt/repayment is settled against the savings pool → leftover value, if any, is returned to the leveraged user. Important limitation: A full “counterparty insolvent” stress result for Sui vs. Aptos is Not verifiable as of 2026-08-29 from the sources found, and I could not confirm separate on-chain exposure or per-chain loss absorption rules from non-protocol sources. The protocol’s own docs strongly emphasize liquidation safety, but that is still an unverified marketing claim unless backed by independent review.

For the stress scenario “committed fraud by the DAO or owners”, I found no verifiable evidence in the supplied results that Mole’s DAO, founders, or owners have committed fraud. The only directly relevant source is an Aptos audit report for Mole, which supports that the project has been reviewed for security issues, but it does not establish fraud or exonerate the team from governance misconduct. The protocol site describes Mole as a DeFi protocol on Sui, and a third-party intelligence page says it has no known security incidents, but that is an aggregator claim and not proof against insider fraud. Given the available evidence, the correct classification is: Not verifiable as of 2026-08-29. If you need a risk judgment for underwriting or exposure limits, treat insider fraud / malicious governance as an unresolved tail risk rather than a confirmed event.

For Mole, the primary yield source negative 30d stress case is not verifiable as of 2026-08-29 from the available web results. The only protocol-specific result I found is a third-party DeFi intelligence page showing Mole with TVL Change (30d): N/A, which does not establish whether the core yield source itself was negative over the last 30 days. Because the available results do not include on-chain data, protocol analytics with a 30-day yield decomposition, or independent reporting for Mole on Sui and Aptos, I cannot confirm a negative 30-day primary yield source for the protocol. The search results also include general explanations of negative SEC 30-day yield, but those are only definition references and are not evidence about Mole’s actual yield performance. Assessment:

• Status: Not verifiable as of 2026-08-29
• Reason: No reliable protocol-specific source in the provided results breaks out Mole’s primary yield source over the last 30 days on Sui or Aptos
• Implication for risk review: Treat the stress scenario as unconfirmed rather than validated; if this is meant to test whether primary yield has turned negative, the present evidence is insufficient to say yes or no If you want, I can next map Mole’s likely yield components by chain and identify which ones would be the most sensitive to a 30-day negative regime.

Mole’s public materials confirm the protocol exists on Sui and Aptos, but they do not disclose enough to verify who controls dev, contracts, frontend, or funds, nor whether governance is real or symbolic. The most defensible conclusion is that critical-control facts are not verifiable from the available sources as of 2026-08-29. What is verifiable:

• Mole describes itself as a DeFi protocol for savings, leveraged yield farms, and funds, and its docs say it lends savings deposits to leveraged-yield users through smart contracts.
• Public aggregators list Mole on Sui and Aptos, with TVL concentrated on Sui (about 96%+ on the cited aggregate pages).
• The project has a public GitHub repository, which indicates some code is published, but repository presence alone does not establish governance control or independence. What is not verifiable as of 2026-08-29:
• DAO reality vs symbolism; proposal process; voter concentration; top holders; timelock; multisig signers, threshold, and signer independence.
• Who controls development, smart-contract admin powers, frontend deployment, and treasury/funds.
• Any company-controlled structure: legal entity, jurisdiction, registration number, directors, or terms of service.
• The user requested Dune-based voting/concentration analysis, but on-chain verification is unavailable in this run, so those metrics remain Not verifiable as of 2026-08-29. Source quality note: the strongest available source here is the protocol’s own docs/site for product description; however, control/governance claims from protocol-owned materials would remain unverified marketing claims unless corroborated by independent governance records, explorer data, or on-chain analysis, which is unavailable in this run.

Mole is a DeFi yield protocol on Sui and Aptos, but its detailed legal and regulatory profile is only partially documented and largely Not verifiable as of 2026-08-30 due to limited independent coverage. ### 1. Legal entity & jurisdiction

• Public web information does not clearly identify a registered corporate entity, jurisdiction of incorporation, or directors associated with Mole.
• No obvious company registry entries, foundation registrations, or formal disclosures are visible in major jurisdictions.
• Result: Legal structure, domicile, and governance are Not verifiable as of 2026-08-30. ### 2. Terms of Service / user restrictions
• Mole’s main site focuses on product description (yield, strategy, etc.) and does not prominently surface a detailed Terms of Service, risk disclosure, or jurisdictional restrictions page in the primary navigation or footer.
• No clear age, residency, or “U.S. persons prohibited” language is visible from public-facing pages without deeper account-level access.
• Result: ToS and geographic/user restrictions are Not verifiable as of 2026-08-30. ### 3. KYC / AML
• As a non-custodial yield protocol on Sui/Aptos, Mole appears to allow wallet-based access with no obvious KYC onboarding flow exposed at the interface level.
• No public statements or policies on AML controls, sanctions screening, or transaction monitoring are readily visible.
• Result: Operational KYC/AML framework is Not verifiable as of 2026-08-30. ### 4. Regulatory classification
• No clear self-classification (e.g., “software only,” “non-custodial protocol,” or treatment as an investment product) is apparent in publicly accessible materials.
• No licenses (e.g., VASP, MiCA, broker-dealer, investment manager) are disclosed in reachable documents.
• Result: Regulatory status and licensing are Not verifiable as of 2026-08-30. ### 5. Enforcement, warnings, court cases, sanctions
• Searches across major jurisdictions (U.S., EU, UK, Singapore, HK) did not surface:
• Regulatory warnings, consumer alerts, or enforcement actions naming Mole.
• Court cases or litigation specifically referencing Mole.
• Listings on major sanctions databases.
• Result: No public enforcement actions or sanctions found; absence of evidence is not proof of compliance. Not verifiable as of 2026-08-30. ### 6. Data protection / privacy
• No standalone privacy policy or data protection notice (GDPR, PDPA, etc.) is easily identifiable.
• Result: Data protection framework is Not verifiable as of 2026-08-30. ### Institutional risk takeaway For institutional use, Mole currently presents elevated legal and regulatory uncertainty: unverified legal entity, unclear ToS and KYC/AML stance, and no visible licensing or compliance disclosures. All key legal risk parameters require direct confirmation from the team and/or external counsel before material exposure.

I could not verify whether Mole’s stablecoin ever depegged, how many times it happened, or the last depeg date/% from the provided web results alone. The search results only contain general articles about stablecoin depegs and do not reliably identify Mole’s specific stablecoin or its on-chain price history, so the correct answer is: Not verifiable as of 2026-08-29.

Mole’s top risks appear to be: 1) smart-contract / code vulnerability risk on Aptos, because the audit found 10 issues including 3 confirmed and 1 medium issue, with the audit explicitly listing access-control, denial-of-service, integer/rounding, and business-logic checks as part of its review scope; 2) liquidation and strategy risk, because Mole’s own docs say leveraged yield positions can be liquidated if the position drops enough, and market-neutral farming can still suffer short-term losses of 0.5%-5% in the first two weeks; 3) audit coverage / residual risk, because the available audit result is only for Aptos, so equivalent security assurance for Sui is not verifiable as of 2026-08-29; 4) token / integration risk, because the audit flags token-registration and token-limit-related issues (e.g., TinyCoin upper-bound checks and tokens not registered), which can break assumptions in asset handling; 5) TVL / adoption concentration risk, because the only third-party estimate in the provided results shows about $8.6M TVL across two chains (Sui and Aptos), implying a relatively small footprint and potentially higher sensitivity to shocks or liquidity exits.

Mole’s top strengths are: (1) product breadth — it offers savings, leveraged yield farms, and funds, giving users multiple risk/return profiles in one protocol; (2) dual-chain deployment — it operates on both Sui and Aptos, which can broaden reach and liquidity; (3) leveraged yield farming without traditional overcollateralization — its docs say leverage is sourced from savings pools rather than direct wallet borrowing, which is positioned as more efficient; (4) support for both AMM and CLMM strategies — the docs describe Mole as the first asset management protocol on Sui to support both, expanding strategy coverage; and (5) automation/AI-driven management — Mole says it uses algorithms to optimize price ranges, auto-adjust positions, and compound returns, reducing manual management burden. These are the clearest strengths supported by the available sources, while some claims are self-published and should be treated as unverified marketing claims.