Scallop Lend

Scallop Lend is a non‑custodial money market / lending protocol built on the Sui blockchain, offering over‑collateralized lending, borrowing and flash loans. ### Protocol identification

• Name: Scallop Lend / Scallop Protocol
• Website / dApp: scallop.io (main site) and app.scallop.io (lending dApp).
• Docs: Hosted under docs.scallop.io, including Scallop Lend sections and borrowing/flash‑loan docs.
• Category: DeFi lending / borrowing money market on Sui, with flash loans and institutional‑oriented tooling.
• Chains: Sui only (protocol explicitly described as a native lending market on the Sui chain).
• Native token: SCA – described as the native currency and lending market token of the Sui ecosystem and tied to Scallop.
• Launch date: Not explicitly stated in technical repos or docs; ecosystem articles reference the project post‑TGE around 2024–2025, but an exact protocol launch date is Not verifiable as of 2026‑09‑04. ### Main contracts / addresses (Sui) Public GitHub repo scallop-io/sui-lending-protocol exposes the Move implementation but not a simple, canonical list of mainnet object IDs in the README. Docs and integration guides refer to on‑chain components such as Market, Reserve, Obligation, InterestModel, RiskModel, and an oracle system XOracle, but do not map them to specific Sui addresses in the materials retrieved. Without direct explorer lookups or decoded tables, concrete main contract addresses and their verification status are Not verifiable as of 2026‑09‑04. ### Fork lineage and design influences
• A detailed overview notes that Scallop’s lending model draws on design concepts from Compound v3, Solend, and Euler, including tokenized debt (“sCoins”) and flash loans.
• This is described as a model influence rather than a direct contract fork; architecture documentation highlights a custom three‑tier design and bespoke oracle integration, suggesting original implementation rather than a simple fork.
• No evidence in retrieved sources of Scallop Lend being a direct hard fork of a specific upstream protocol, nor of malicious modifications in derivative forks.
• Audit status and whether changes vs. those inspirations were formally audited are Not verifiable as of 2026‑09‑04 (no primary audit PDFs or auditor‑site reports surfaced in the data). Given the lack of on‑chain tooling this turn, any concrete contract IDs, TVL, or deployment timestamps must be treated as Not verifiable as of 2026‑09‑04.

Scallop Lend appears to be a real, functional dApp rather than a pure landing page: its docs point users to an app at app.scallop.io, and the docs include step-by-step lending/borrowing and withdrawal instructions that describe live wallet-connected flows. The project also provides developer tooling, including a Typescript SDK and contract-integration docs, which is consistent with a mature product surface rather than a template site. On UX maturity, the documentation breadth is fairly strong: there are dedicated pages for borrowing, withdrawing, integration, and developer resources, plus references to an SDK and Sui Kit tooling.

That said, the available web evidence does not let this answer verify live deposits/withdrawals end-to-end or check for broken links, fake metrics, or template signs on the current site, so those items are Not verifiable as of 2026-09-04. Open API: there is clear evidence of a developer-facing SDK and contract-integration layer, but not a public, documented open REST API in the material reviewed. So the safest conclusion is that Scallop Lend has developer integration tooling, but a public open API is Not verifiable as of 2026-09-04.

Scallop has an active bug bounty program for smart-contract/security issues. It was announced no later than 2023-09-16 and is still described in the project docs as launching/in force, with later references in 2025 confirming it remains active. The published scope excludes UI bugs, requires reporting directly to Scallop or via HackenProof depending on the program page, and pays rewards in SUI/USDC/SCA.

Severity tiers are: Critical up to $300,000; High up to $30,000; Medium up to $3,000; Low up to $300. A third-party program page also mentions exceptional critical cases up to 20% of protocol loss amount, but this appears as an expanded/partner-hosted rule set and should be treated cautiously. Reported results available in the sources are limited: no public list of payouts or disclosed accepted findings was found, but the program page and later coverage indicate it has been used alongside Scallop security incidents and bounty-related negotiations.

Not verifiable as of 2026-09-04 for total payouts or number of paid reports.

Assessment — Sui only; on-chain exposure percentages unavailable. Dune MCP was unavailable; therefore balances, utilization, wallet concentration, bridge composition, and counterparty exposure are Not verifiable as of September 6, 2026.

• Oracles: Scallop documents Pyth as primary and Supra as secondary through its X-Oracle validation layer; its risk page also names Switchboard. This is a documentation inconsistency and should be resolved against deployed package configuration. Simultaneous stale, manipulated, or divergent feeds could cause wrongful liquidations, bad debt, or frozen borrowing/withdrawals.
• Bridge and wrapped-asset dependency: Supported assets include Wormhole-wrapped USDC/USDT/ETH/BTC/SOL and Sui Bridge assets such as sbETH, sbUSDT, and sbwBTC. Bridge validator/message failure, issuer freeze, chain halt, or loss of redemption liquidity could create collateral depegs and liquidation cascades.
• Stablecoin/RWA exposure: Scallop lists USDC, FDUSD, USDY, mUSD, and synthetic stablecoins. USDY introduces issuer/SPV, eligibility, custody, Treasury/bank-deposit, legal-enforcement, and redemption risks; Ondo identifies USDY as a tokenized note issued through its entity structure. Exact Scallop exposure is Not verifiable as of September 6, 2026.
• LST/restaking exposure: afSUI, haSUI, and vSUI are supported; these depend on Aftermath, Haedal, and Volo staking/redemption mechanisms and validator performance. Depeg, delayed unstaking, validator failure, or provider exploit could impair collateral values.
• Custodians/CEX/MMs: No verified evidence was found that Scallop itself holds custodial, CEX, market-maker, or segregated treasury assets. Counterparty liquidity may nevertheless be indirect through bridge operators, token issuers, oracle publishers, and LST providers. Not verifiable as of September 6, 2026. Incident note: A reported April 26, 2026 exploit drained approximately 150,098 SUI from a deprecated sSUI rewards contract; this indicates residual legacy-contract risk, but does not establish an active dependency failure in core lending. Maximum exposure: Not verifiable as of September 6, 2026; no percentage should be inferred without current on-chain balances.

Scallop Lend is organized as a non-custodial, smart-contract lending protocol on Sui: users deposit into on-chain pools, receive sCoins as receipt tokens, and their borrowing/collateral positions are tracked in on-chain Obligation objects rather than held by Scallop itself. Scallop’s docs explicitly state that the deploying entity does not hold user assets in custody, while the architecture description says the on-chain Reserve layer manages underlying balances and token supply, including token custody/accounting for supported assets. Separate asset segregation is only partially verifiable: the protocol supports isolated assets/isolated pools, but a general, protocol-wide guarantee that all assets are segregated from one another is not verifiable as of 2026-09-06.

Withdrawal status is not verifiable as of 2026-09-06; however, the protocol documentation describes standard withdrawal flows and an emergency freeze mode that can reject redeem/withdraw operations when activated.

Scallop Lend: Protocol Logic via Reward Logic Flaw on Sui; loss $142,000 (DeFiLlama hacks registry).

Corrected and rechecked prior finding. On April 26, 2026, an attacker exploited a deprecated V2 sSUI Spool rewards contract on Sui. A missing initialization/validation check for the reward accumulator (last_index) let the attacker fabricate reward points and drain 150,098.06 SUI from the entire sSUI rewards pool in one transaction.

Realised protocol/user reward-pool loss was approximately $142,500; attacker proceeds were approximately the same. Affected: unclaimed sSUI rewards only. Core lending/borrowing pools, principal deposits, and other reward pools were reported unaffected.

Scallop froze the vulnerable contract, coordinated with Blockaid and Mysten Labs to freeze/monitor related addresses and pause additional at-risk contracts, and restored core deposits/withdrawals within roughly two hours. The legacy contract was disabled; a separately verified code patch, version-gating implementation, or comprehensive post-incident review is Not verifiable as of September 6, 2026. Scallop publicly pledged 100% reimbursement from treasury, but completed user payments and any recovered attacker funds are Not verifiable as of September 6, 2026.

Current status: remediation_in_progress because containment and service restoration are evidenced, while reimbursement completion and permanent remediation are not independently confirmed.

Scallop Lend’s key management is capability-based on Sui. Each user position is stored in a shared Obligation object, but ownership and mutation rights are controlled by an owned, transferable ObligationKey that serves as proof of ownership; the key is held in the user’s wallet and is required alongside the Obligation to perform borrow-related actions. Scallop also supports up to 5 sub-accounts per Sui address, allowing users to isolate collateral and debt across multiple positions without repeated approvals, and assets/liabilities can be moved between sub-accounts without approvals once the user has the relevant key.

Assessment (as of September 6, 2026): HIGH smart-contract/admin risk. Sui does not use an EVM-style proxy here; upgradeability is package-based through an UpgradeCap. Sui states that the UpgradeCap holder can authorize upgrades, change compatibility policy, or make the package immutable. Published Sui mainnet registry (not independently re-verified): core package 0x07871c…f6ac7; core UpgradeCap/versionCap 0x590a40…8a07; protocol object 0xefe8b3…fddf; market 0xa75797…939d; AdminCap 0x09689d…777c; obligation-access store 0x733e30…59c9. The registry also identifies Pyth/xOracle components and separate package upgrade caps. Admin powers identified in the audit: modify interest/risk-model delays and parameters; add/remove whitelist addresses; register and update assets; configure limiters; set incentive and flash-loan fees; activate/deactivate base or collateral assets; withdraw protocol revenue; and add/remove obligation lock/reward keys.

The audit classified this centralization issue as Major — Acknowledged, not fixed. Architecture: Users → Market/shared protocol object → sCoin mint/redeem Users → Obligation + ObligationKey → collateral/borrow/repay/liquidation Market → risk/interest models + limiters + asset registry Market → xOracle/Pyth → pricing AdminCap → configuration/revenue/access controls UpgradeCap → package upgrades Exit and failure analysis: user-facing mint/redeem and collateral-withdrawal paths are documented, but uninterrupted exit under adverse admin configuration or depleted liquidity is not guaranteed. A compromised AdminCap could freeze or impair markets, whitelist hostile actors, manipulate risk/interest/limiter settings, alter fees, affect oracle-related configuration, or withdraw protocol revenue. A compromised UpgradeCap could deploy materially different logic.

Direct withdrawal of all user principal by AdminCap is not established by the reviewed audit. Not verifiable as of September 6, 2026: current cap owners, multisig status, proxy-admin type, pause/withdrawal/upgrade/oracle/strategy implementation in the live package, renounced roles, on-chain timelock delay/execution history, and whether users can always exit. Dune was unavailable; no Dune query/execution IDs exist. No current deployment-specific unresolved High/Critical count can be verified; the 2023 audit reported 0 Critical and no High category, but this does not validate the live deployment.

A February 2025 security audit/formal verification is referenced by independent coverage as covering core lending logic, accounting, access control, liquidation logic, precision calculations, balance management, collateral valuation, parameter changes, and '100% API-standard verification coverage' for externally callable functions. The available result does not provide a PDF report with a standard issue table, so critical/high/medium findings and fix status are not verifiable as of 2026-08-29. Covered deployed code / bytecode-match is also not verifiable from the result set.

Auditor: Asymptotic. Report date: December 2, 2025. Scope, critical/high/medium findings and fix status: Not verifiable as of September 5, 2026; the auditor’s customer index confirms the report and date but the report itself was not retrievable. Covers deployed code: Not verifiable as of September 5, 2026. Link: https://asymptotic.tech/customers/

Asymptotic, described as an official audit/verification partner of the Sui Foundation, conducted a comprehensive formal verification of Scallop Lend’s core lending protocol on Sui. Public coverage (PANews, Cryptorank, Coinness, and other news/announcements) states that Asymptotic mathematically verified the correctness of the protocol’s core financial logic and achieved 100% API‑standard verification coverage for externally callable functions.

A later MoveBit report is listed by Scallop for the core lending/borrowing contracts.

Second published OtterSec version for the same Sui lending engagement and commit; it conflicts with the 14-finding version.

Zellic security assessment of Scallop Move modules and oracle/whitelist libraries on Sui.

MoveBit audit of Scallop’s Sui lending market.

Scallop’s own security page lists multiple audit PDFs including a “Scallop – Zellic Audit Report” and other audits, and later communications reference OtterSec and a full Sui Foundation audit in February 2025. However, individual Zellic/OtterSec/Sui‑Foundation audit reports for Scallop Lend on Sui are not fully accessible in the retrieved snippets, and their precise scopes, issue breakdowns, and code coverage cannot be reconstructed from secondary mentions alone. All details below are therefore partial and must be treated cautiously.

Scallop Lend appears to be a publicly led, non-anonymous team rather than an anon-only protocol. The clearest public founder profile is Kris Lai / Kriss, whose LinkedIn says he is Founder & CEO of Scallop and whose own interview says he started as a full-stack developer, then a network security engineer, earned an EC-Council CEH credential, and began building DeFi products in 2021; a LinkedIn company page also describes Scallop as founded in 2021 with 1–10 employees. Independent profile pages also name Kris Lai (CEO) and Donnie Chen (CTO) as co-founders.

There is some inconsistency in public bios: one founder interview says Scallop began as "Scallop Pools" on Solana in early 2021 and later expanded to Sui in 2022, while another directory-style source lists Scallop as a Sui DeFi lending project founded in 2021. Publicly stated achievements include Sui Foundation grant support and hackathon placements, but those are self-reported or ecosystem-published claims rather than independently verified operating-history evidence. Reality check: the project has visible code on GitHub, security-partner branding, and a HackenProof program, which supports that it is a real software project, not just a marketing site. However, I could not verify a real office, onshore/offshore incorporation, or audited corporate structure from the provided sources. Not verifiable as of 2026-09-04.

Scallop Lend has a generally *positive but qualified* reputation in Sui DeFi: it is repeatedly described as one of the leading lending protocols on Sui, but independent risk coverage still flags *moderate risk* from single-chain concentration and a relatively young security environment. The strongest concrete downside in the available sources is a reported security incident that Hindenrank and DIA both note, with losses reported around $142k–$150k; one source says the protocol compensated users and froze the affected contract, but that compensation claim is not independently verified here. On the positive side, multiple sources say Scallop was the first DeFi project funded by the Sui Foundation and that it raised $3 million in strategic financing, with participation from named investors such as THE CMS, 6MV, KuCoin Labs, Blockchain Founders Fund, and the Sui Foundation.

The protocol is also described as having undergone audits, with Scallop’s own audit page listing Zellic and other reports, while third-party writeups cite OtterSec and MoveBit; however, the exact audit scope and recency are not fully verifiable from the search results alone. I did not find credible evidence in the provided results of fraud, rug-pull, insolvency, sanctions, or active legal/regulatory enforcement against Scallop. The unresolved concerns are mainly operational and reputational: single-chain dependence on Sui, prior exploit history, and reliance on protocol/press claims for some funding and compensation details.

Economic model (Sui only). Scallop Lend is an over-collateralized money market: users supply supported assets (including SUI, stablecoins and bridged assets) and receive interest-bearing sCoins; borrowers post collateral and draw pool liquidity. Supply yield is primarily borrower interest, with rates determined by utilization/tri-linear rate models—not a directional trading strategy. Yield classification. Lending yield is economically organic to the extent it comes from borrower interest. Borrower-side reward APRs have existed, so any reward component is subsidy-dependent; current organic/subsidized split is Not verifiable as of September 6, 2026.

DeFiLlama currently reports $0 incentives, but this is an aggregator snapshot and does not prove historical absence of incentives. Exposure and leverage. The base lender strategy is market-neutral with respect to the supplied asset, but lenders retain the asset’s price exposure (e.g., SUI/USD). Borrowers can create leveraged/looped exposure by repeatedly supplying and borrowing, subject to collateral weights, borrow weights, utilization and outflow limits. No native restaking or external yield strategy was verified.

Flash loans are available at a stated 0.1% fee. Collateral, liquidation and withdrawals. Collateral earns no supply yield. Risk level at or above 100% can trigger incremental “soft liquidation”; liquidation penalties are split between liquidator reward and protocol reserve. Suppliers generally withdraw by redeeming sCoins, but redemption can fail when pool liquidity/reserves are insufficient; no fixed lock-up is documented. Fees, gates and revenue. Borrow fees are asset-category dependent: 0.3% for main assets and 1% for emerging/isolated assets; protocol revenue also comes from a share of borrowing interest, liquidation reserve, and 0.1% flash-loan fees.

Borrowing/withdrawal outflow caps and asset supply caps can gate liquidity. TVL/APY snapshot. DeFiLlama reports approximately $9.88m TVL, 100% on Sui, $2.21m active loans, average supply APY 1.42%, and TVL down 6.7% over 30 days; product-level TVL and APY volatility/history are Not verifiable as of September 6, 2026. Dune comparison and on-chain TVL are Not verifiable as of September 6, 2026 because Dune MCP was unavailable. Risk conclusion: sustainability depends mainly on borrower demand and utilization; the current low average APY and falling TVL indicate modest carry and potentially weak demand, not a proven high-yield strategy.

As of September 6, 2026, Scallop Lend’s liquid reserves, liabilities, wallet balances, and reserve composition are Not verifiable as of September 6, 2026. Dune/on-chain verification was unavailable in this run, so no current USD balance sheet or latest-block snapshot is reported. Architecture and custody: Scallop’s Sui lending contracts use a shared Market object and per-asset reserve accounting; supplied assets are represented by interest-bearing MarketCoin/sCoin positions, while borrowing creates user obligations. This is protocol accounting, not evidence of a separately disclosed treasury wallet.

The official package-address registry identifies the mainnet core object, market object, and admin capability, but does not provide lending-reserve wallet balances or a treasury custody policy. Composition: Supported markets include SUI, USDC, wUSDC, wUSDT, wETH, CETUS, afSUI, haSUI, vSUI, SCA, wBTC, and wSOL; actual reserve amounts and USD values are Not verifiable as of September 6, 2026. Control and reserve policy: The documented SCA treasury allocation is distinct from Scallop Lend’s lending reserves. Scallop lists a Treasury SCA control address (0xfbc3117f547089a29e1cf197994d0ecf628e72babc6a3bf850f311533384cf99) and treasury/revenue multisig budget addresses, but these are token treasury-control records, not proof of custody of deposited lending assets. Attestations: No independent reserve attestation or liabilities attestation was identified. Not verifiable as of September 6, 2026. Contradiction / finding: Marketing or token-allocation treasury disclosures must not be conflated with Lend liquidity reserves. No independently verified current treasury size was found.

Scallop Lend on Sui does have a native token: SCA. However, on‑chain verification via Dune is Not verifiable as of 2026‑09‑04. ### Basic token info

• Name / ticker: Scallop token (SCA).
• Chain: Sui.
• Token type: Move token deployed on Sui (exact contract address Not verifiable as of 2026‑09‑04; public explorer records are fragmentary and inconsistent for SCA, so I will not guess). ### Supply, market cap, FDV
• Public tokenomics materials describe fixed total supply (no continuous mint), but specific numbers differ between sources and are not independently confirmed on Sui explorers; therefore total supply, circulating supply, market cap and FDV are Not verifiable as of 2026‑09‑04.
• Any figures shown on CEX/aggregator listings for SCA should be treated as aggregator estimates, not on‑chain truth. ### Utility and governance
• Protocol utility: SCA is described as a utility and governance token for Scallop’s DeFi suite (including Scallop Lend on Sui).
• Governance: Marketing materials state SCA will be used for protocol governance (votes on parameters, new markets, etc.), but concrete governance contracts/DAO structure on Sui are Not verifiable as of 2026‑09‑04.
• Economic utility: SCA is referenced for staking rewards, fee discounts and ecosystem incentives, but the exact mechanisms (which contract pays what, in which asset) are not clearly documented in independent sources and remain unverified marketing claims. ### Revenue share, buybacks, burns, staking
• No independent documentation confirming that Scallop Lend’s protocol revenue is shared with SCA holders, used for buybacks, or systematically burned.
• Staking and reward APYs for SCA appear on marketing pages and exchange listings, but these are unverified marketing claims; the underlying on‑chain reward logic on Sui is Not verifiable as of 2026‑09‑04. ### Emissions and unlocks
• Several external articles mention vesting and unlock schedules for SCA tied to team/investor allocations, but they do not link to Sui addresses or on‑chain vesting contracts; thus emissions and whether announced unlocks happened on‑chain are Not verifiable as of 2026‑09‑04. ### Allocations and holder concentration
• Typical buckets (team, investors, community, treasury, ecosystem) are described in tokenomics infographics, but these are unverified marketing claims with no independent mapping to Sui wallet addresses.
• Top-holder concentration, insider wallets, and control of mint/blacklist/fee‑switch functions are Not verifiable as of 2026‑09‑04. ### Liquidity and listings
• SCA is listed on several centralized exchanges (e.g., KuCoin and others) according to recent listings announcements, but these refer primarily to non‑Sui trading infrastructure; the depth of SCA liquidity on Sui DEXs (e.g., Cetus/Turbos) is Not verifiable as of 2026‑09‑04. Overall: You should treat all quantitative SCA tokenomics (supplies, unlocks, yields, revenue share) as unverified marketing claims unless and until they are tied to specific Sui contracts and wallets and checked on‑chain.

Scallop Lend documents two BTC-relevant stress points: its lending system relies on oracle pricing, and it warns that if multiple oracles are wrong at the same time, wrongful liquidations can occur. It also says the Insurance Fund reserve is intended to protect against unforeseen losses from untimely liquidations within insured pools. Under a BTC move below $10,000, the main protocol risk is not a special “Bitcoin-specific” rule but *collateral devaluation* and the resulting liquidation pressure on any positions that use BTC as collateral.

Scallop’s own materials do not provide the BTC collateral factor, liquidation threshold, or pool-level exposure needed to quantify how much debt would be at risk, so the size of the impact is Not verifiable as of 2026-09-04. What can be said from the available sources is that an extreme BTC crash is consistent with a scenario where oracle-driven liquidations accelerate, and if liquidations are poorly timed or oracle prices are wrong, the Insurance Fund may be drawn on to absorb losses in insured pools. Because no on-chain or pool-specific exposure data was available in this run, the protocol-level loss estimate, chain split, and TVL-at-risk remain Not verifiable as of 2026-09-04.

The most important practical takeaway is that a BTC sub-$10,000 shock would likely stress Scallop Lend through *margin/liquidation mechanics* rather than direct protocol insolvency, but the magnitude of the stress cannot be quantified from the sources provided.

Scallop Lend’s liquidation framework is soft/liquidation-by-partial-repayment, so a 20% collateral depeg does not automatically imply full protocol insolvency; it mainly determines whether accounts cross the liquidation threshold and how much of each underwater position can be repaid in each call. The liquidation cap in the protocol documentation is 20% of total outstanding debt per liquidation call, which limits how much debt can be repaid at once even in a stress event. For a largest-collateral depeg of 20%, the key risk driver is the affected asset’s collateral factor vs. liquidation factor.

For example, the documented SUI parameters are 85% collateral factor and 90% liquidation factor; a 20% price drop on a position that was previously close to maximum LTV can push the account below the liquidation threshold and make it eligible for soft liquidation. The docs also state that liquidation occurs when collateral value falls below the required threshold, and that liquidators only sell the amount needed to restore health. What is not verifiable as of 2026-09-04 from the provided sources is the actual on-chain distribution of collateral by asset on Sui, so the portfolio-level impact of a 20% depeg cannot be quantified here.

That means the share of total TVL/exposure tied to the largest collateral, and the resulting expected bad debt or liquidation volume, is Not verifiable as of 2026-09-04. Practical interpretation: if the largest collateral asset is the one that depegs 20%, the stress outcome is likely a wave of partial liquidations, with the protocol’s 20% per-call liquidation cap slowing deleveraging and reducing immediate collateral stripping, but positions with thin buffers can still become unhealthy quickly.

For a top-counterparty insolvency stress scenario, Scallop Lend’s loss path is a borrower-default / liquidation path rather than a CCP-style mutualized waterfall. The protocol documents soft liquidation: when a position’s risk level reaches 100% or higher, only the portion needed to restore health is sold, and liquidation continues incrementally until the account is healthy again. The protocol also states that an Insurance Fund reserve protects against unforeseen losses caused by untimely liquidations within insured pools. Expected loss path: if the borrower/counterparty cannot meet obligations, collateral is sold to repay debt; if collateral sale is insufficient or delayed, the insured pool’s loss is intended to be covered by the Insurance Fund reserve.

The user’s residual loss is thus primarily borne first by the borrower’s collateral, then by the insurance reserve if the pool is insured; otherwise, any shortfall is Not verifiable as of 2026-09-04. Who absorbs it: liquidators execute the sale, the borrower absorbs collateral loss, lenders are repaid from the liquidation proceeds, and the insurance reserve is the stated backstop for certain insured-pool losses. Compensation: Scallop says it does not fully wipe out collateral; it only liquidates the debt portion that causes unhealthiness, limiting borrower loss compared with full liquidation. That is an *automatic risk-mitigation mechanism*, not discretionary compensation. Impact path through smart contracts: oracle prices from Pyth (primary) and Supra (secondary) feed the account’s health/risk calculation; once unhealthy, the liquidation logic triggers, liquidators sell collateral, debt is repaid, and the position is iteratively restored to healthy status. The exact insurance-fund claim flow, reserve sizing, and any protocol-wide loss-allocation sequence are Not verifiable as of 2026-09-04 from the available sources.

For the DAO/owners fraud stress scenario, I found no verifiable evidence that Scallop Lend’s DAO or owners committed fraud. The available reporting instead describes a smart-contract exploit on a deprecated side/rewards contract, with Scallop stating that core contracts and user deposits were unaffected and that losses were covered/resumed operations. What is verifiable is a security loss event, not insider fraud: multiple reports say roughly $142k / 150,000 SUI was drained via flash-loan/oracle manipulation and a deprecated contract path.

However, these sources do not establish that the DAO or owners intentionally misappropriated funds, directed the attack, or conducted a fraudulent treasury action. There is also no evidence in the provided results of a governance attack, malicious proposal, treasury drain, or owner-controlled rug pull. Accordingly, the fraud risk case for Scallop Lend is Not verifiable as of 2026-09-04 from the supplied sources.

If you want the adjacent stress case, the verifiable incident is external exploit / legacy-contract failure, not committed fraud by insiders.

Scallop Lend’s primary yield source negative 30d is not verifiable as of 2026-09-04 from the provided web results. The available sources only confirm that Scallop Lend is an overcollateralized lending protocol on Sui, with interest-rate/utilization mechanics and an insurance fund, but they do not provide a 30-day yield decomposition, APY history, or chain-level revenue data for the primary yield source. For a stress scenario, the defensible institutional reading is: if the protocol’s main yield comes from lending spread / borrower interest, a 30-day negative primary yield would imply yield compression or net negative carry at the strategy level, while liquidation and insurance-fund mechanisms may mitigate some credit-loss tail risk but do not themselves prove positive yield.

However, the magnitude of that effect is Not verifiable as of 2026-09-04 because no independent on-chain or analytics source in the results shows the relevant 30-day figures. What can be stated with confidence is limited to protocol structure: Scallop Lend is an overcollateralized lending protocol on Sui, and it uses utilization-based rate dynamics plus an insurance fund for unforeseen losses in insured pools.

Assessment — as of September 13, 2026: Scallop Lend appears team/company-controlled rather than controlled by an independent DAO. Development is maintained by the Scallop GitHub organization; deployment documentation exposes AdminCap and upgrade-cap objects, while the repository documents deployment using a deployer secret key. The frontend is operated through app.scallop.io and the Terms identify Scallop Labs Ltd., Republic of Seychelles as the service provider.

The Terms do not disclose a registration number or directors. User custody is non-custodial, but the same Terms state that Scallop-controlled multisignatures hold powers to change interest/risk parameters, pause or limit markets, set fees, withdraw accrued protocol revenue, force deleveraging, and upgrade contract code. They expressly state there is no enforced delay before these powers take effect. DAO status/process: veSCA governance voting is documented as “coming soon”; no live, independently verified proposal-and-execution process was found.

Therefore the DAO appears symbolic/not operational for protocol control. Voting concentration and top holders via Dune: Not verifiable as of September 13, 2026. On-chain verification is unavailable in this run. Multisig: Scallop discloses multisignature control and lists several team/treasury multisig addresses, but threshold, complete signer sets, signer independence, and current control of each contract capability are Not verifiable as of September 13, 2026.

The documentation also labels parameter-change delay fields as zero, indicating no active protocol timelock in the documented configuration. Risk conclusion: Company/team control is substantive, not merely frontend control. Upgrade and administrative powers can affect user positions and protocol-held assets without a token-holder governance vote; this supports admin_can_drain=true under the stated risk definition, although direct arbitrary withdrawal of user principal was not independently verified. Structured fields:

• timelock: false
• timelock_delay_hours: 0
• multisig_threshold: null
• multisig_owners: null
• admin_can_drain: true
• emergency_bypass: true
• dao_governance: false

Scallop Lend is a DeFi lending protocol built on Sui, marketed as part of the broader Scallop ecosystem (which also includes a centralized exchange). Legal and regulatory information is fragmented and mostly tied to the Scallop CeFi entity rather than the on‑chain lending protocol. Legal entity & jurisdiction

• Public materials reference Scallop as a company with operations in the UK and EU, but they do not clearly distinguish an entity specifically responsible for Scallop Lend on Sui.
• No definitive, independently verified corporate registry entry for a "Scallop Lend" entity or a foundation dedicated to the Sui protocol could be located. Given this, the protocol’s operating entity and governing jurisdiction are Not verifiable as of 2026-09-04. Terms of Service / user restrictions
• Scallop’s main platform ToS (CeFi) includes geographic restrictions (e.g., U.S. and certain sanctioned jurisdictions) and typical crypto-exchange conditions.
• There is no separately verifiable, binding ToS specific to Scallop Lend on Sui; any such documents are either not public or not clearly linked to the protocol front end. Thus, protocol-level user restrictions are Not verifiable as of 2026-09-04. KYC / AML
• Centralized Scallop exchange requires full KYC in line with typical exchange practice.
• On-chain Scallop Lend appears to be accessible via wallet connection and does not obviously enforce KYC at smart-contract level; independent confirmation (e.g., from audits or code analysis) is missing.
• There is no public description of on-chain AML controls (screening, blacklists) specific to Scallop Lend. Therefore, KYC/AML design for the lending protocol is Not verifiable as of 2026-09-04. Regulatory classification / enforcement / sanctions
• No records in major regulator databases (FCA, SEC, ESMA, MAS, etc.) mentioning "Scallop Lend" or enforcement actions tied specifically to the protocol were found.
• No listings of Scallop or Scallop Lend on major sanctions databases (OFAC, EU) were found.
• No court cases involving Scallop Lend as defendant or subject could be located in public case databases or independent reporting. Data protection
• Any GDPR/PDPA-style privacy framework applies to the CeFi operation, which collects personal data.
• For Scallop Lend, interaction appears wallet-based; absence of a clear privacy policy tied to the dApp front end means data protection posture is Not verifiable as of 2026-09-04. Risk takeaway (legal vs protocol use)
• Users are likely interacting with an unclearly documented DeFi protocol, where the legal entity and jurisdiction responsible for smart contracts, possible recovery, or compliance are not transparently disclosed.
• This increases counterparty / regulatory uncertainty risk, particularly for institutional users requiring clear legal wrappers, licensing status, and dispute-resolution venues.

No exact GLEIF LEI record for 'Scallop Lend'. OFAC SDN screening of 'Scallop Lend': no match. SEC litigation and administrative release feeds: no mention.

Scallop Lend does not appear to issue its own stablecoin; the gathered sources describe it as a lending protocol on Sui that uses assets such as USDC / native USDC and mints sCoins like sUSDC as receipt tokens, not a protocol-native stablecoin. I could not verify any depeg event for the stablecoin used by Scallop Lend from the available web sources, so depeg_count, last_depeg_date, and max_depeg_pct are Not verifiable as of 2026-09-06. Because no depeg was verifiable, stable is also Not verifiable as of 2026-09-06.

Scallop’s highest risks are smart-contract failure, oracle error, liquidation stress, privileged operational control, and inadequate loss absorbency. The April 26, 2026 exploit of a deprecated sSUI rewards contract demonstrates that legacy components can remain callable and economically relevant even when core lending markets are unaffected. Current on-chain exposure, utilization, and reserve adequacy: Not verifiable as of September 5, 2026.

Scallop Lend’s top strengths are: institutional-grade positioning, security architecture, high composability, Sui-native performance advantages, and advanced money-market features. The protocol is consistently described as a next-generation money market for Sui with a focus on institutional-quality risk control and usability.

• Institutional-grade design: Scallop is marketed as a lending protocol built for professional and larger-capital users, with an explicit focus on risk control and product stability.
• Security-first architecture: Sources highlight its use of Sui Move smart contracts, asset segregation/collateral separation, and conservative liquidation/risk management as core security advantages.
• High composability: Scallop is designed as a modular DeFi primitive, with components that other protocols, wallets, and apps can integrate, and its sCoins are described as composable across Sui DeFi.
• Sui network advantages: Because it is built on Sui’s object-centric model, Scallop can benefit from parallel execution, low fees, and fast settlement, which support efficient lending and borrowing workflows.
• Feature depth: Beyond basic lending, Scallop offers flash loans, sub-accounts for position isolation, a trilinear interest-rate model, and collateral segregation, which broaden its utility for both retail and advanced users. One caveat: many “strength” claims come from protocol descriptions and ecosystem media rather than on-chain verification in this run, so treat them as *source-backed but not independently on-chain verified*.