Scallop Lend

Scallop Lend is a decentralized, over‑collateralized money‑market / lending protocol on the Sui blockchain, operating under the Scallop brand (Scallop Protocol). It enables users to supply, borrow and use flash loans in Sui‑native markets. Identification

• Name / brand: Scallop Lend (often just “Scallop” in Sui materials).
• Website / app: Main site at scallop.io; lending dApp front‑end at app.scallop.io.
• Docs: Hosted on docs.scallop.io, with a dedicated “Scallop Lend” section and developer resources referencing the Sui lending smart contracts GitHub repo.
• Category: Non‑custodial DeFi lending/borrowing money market with flash loans; over‑collateralized, peer‑to‑peer liquidity pools.
• Chains: Sui only (protocol described consistently as “on Sui network / Sui blockchain”).
• Native / ecosystem token: The ecosystem token is SCA (Scallop); described as “native currency and lending market of the Sui ecosystem” and tied directly to Scallop’s lending protocol.
• Launch timing: Guides and “how to use on Sui mainnet” were published mid‑2023 (e.g., June 26, 2023 tutorial on using Scallop on Sui mainnet), implying mainnet launch around that time. Precise block‑level launch is Not verifiable as of 2026‑08‑29. Main contract addresses & verification
• A “How to Scallop on Sui Mainnet” guide lists a primary Sui contract address for the lending protocol:
• 0xc05a9cdf09d2f2451dea08ca72641e013834baef3d2ea5fcfee60a9d1dc3c7d9.
• The GitHub repo scallop-io/sui-lending-protocol is referenced in the official docs as the Sui Lending Smart Contract implementation, confirming this as the canonical on‑chain deployment for the protocol’s Move modules.
• Explorer‑level verification status for this address on Sui is Not verifiable as of 2026‑08‑29 (no direct explorer data in retrieved results). Fork lineage / design influence
• Scallop is described as a native lending market on Sui whose model “draws on the design concepts of lending protocols like Compound v3, Solend, and Euler”.
• It “adopts a lending model based on the Compound protocol” but implements it in Sui Move with its own architecture (sCoins, XOracle, three‑tier design) rather than being a direct Solidity fork.
• DeepWiki and GitHub show a bespoke three‑tier architecture (TypeScript config, Move on‑chain layer, multi‑source oracle layer) and Sui‑specific modules, indicating an original implementation inspired by Compound‑style markets, not a simple code fork. Audits & malicious‑modification history
• The retrieved data does not contain primary audit reports or explicit links to auditors (e.g., audit PDFs) for the Sui lending contracts. Audit status is therefore Not verifiable as of 2026‑08‑29.
• No evidence in retrieved sources of known malicious modifications in Scallop itself or in closely related forks; this absence is not proof of safety, only lack of reported incidents in these materials.

Scallop Lend appears to be a real, functional Sui lending product rather than a pure landing page. The docs point to an active dApp at app.scallop.io and describe live lending, borrowing, collateral, bridging, and withdrawal flows, and the GitHub SDK/docs show programmatic interaction with lending queries and contract addresses. Maturity signals are moderate-to-strong: there is a developer-resources page, a TypeScript SDK, and docs that expose lending functions and query helpers, which is more than a template site or brochure. The documentation also explicitly states that users can supply and withdraw assets via the dApp, which implies live product functionality, not just marketing copy. Open API: yes, there is evidence of an API/SDK layer. The docs list “Scallop API Docs,” and the SDK repositories describe query, address, and indexer components for interacting with the protocol programmatically. What is not verifiable from the available web material: whether deposits/withdrawals are currently live at this moment, whether any links are broken today, and whether on-page metrics are fake or stale. Not verifiable as of 2026-08-29.

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.

Audit of the Sui lending protocol source code; report dated 2023-06-30. Scope was the 'Sui Lending smart contract' / lending market on Sui, with source code referenced as https://github.com/scallop-io/sui-lending-protocol. The report summary lists 15 issues total: 13 fixed and 2 acknowledged. Severity breakdown shown in the report: 0 critical, 2 major, 4 medium, 9 minor/informational. The report explicitly marks major issues as fixed or acknowledged; one major example shown is a flash-loan fee logic issue marked fixed. Covered deployed code is not fully verifiable from the web excerpt alone; however the report ties the audit to the repository source and specific commit hash, not a live deployment bytecode diff. Bytecode-match note: Not verifiable as of 2026-08-29.

Scallop Lend has an active bug bounty program. HackenProof marks the program as Live and the Scallop docs describe it as a launched bug bounty for the protocol’s smart contracts. The earliest clearly stated start date I found is 05 Mar 2025 on Scallop’s HackenProof company page; the page was last updated on 19 Mar 2025. Scallop also announced the program publicly on LinkedIn in a post that points users to the official docs. Parameters / scope: the program is for smart contract security on the Scallop protocol, and the HackenProof scope includes the core smart contract protocol repository. Scallop’s docs say UI-related bugs are excluded and reports must be submitted exclusively to the designated email address. HackenProof additionally requires the reporter to be the first reporter, to submit within 24 hours of discovery, and to use the HackenProof registration email. Reward structure: reported issues are paid in SUI/USDC/SCA. Publicly listed rewards are Low: $30–$300, Medium: $300–$3,000, High: $3,000–$30,000, and Critical: $30,000–$300,000. Scallop’s docs also mention up to 20% of protocol loss amount for exceptional critical cases, while the HackenProof page lists that as an exceptional critical tier cap. Results: HackenProof’s program page shows 392 submissions and $300 total rewards paid. The HackenProof company page lists Paid: 0 as of its latest update, which conflicts with the program page’s reported rewards; the on-page program stats are the more specific result figure available here. Not verifiable as of 2026-08-30: a complete, independently validated list of all accepted findings, severity distribution, and whether any specific disclosures were tied to this bounty program beyond the publicly visible reward totals.

Scallop Lend is heavily dependent on external price oracles and on the Sui ecosystem, so its main counterparty risk is *oracle failure/manipulation* rather than custodial or bridge risk. Scallop’s docs say X-Oracle is used to mitigate price manipulation and currently relies on Pyth as the primary feed, with Supra as a secondary feed; another docs page also names Switchboard in its multi-oracle stack, and states borrowing, collateral withdrawals, and liquidations depend on fresh oracle prices. The audit material explicitly says third-party dependencies such as the oracle are *not covered* and assumes the oracle data is accurate, which means oracle correctness is an external dependency, not a fully verified internal control. For asset-type exposure, Scallop’s publicly documented risk models include liquid-staking tokens such as afSUI, haSUI, and vSUI, with lower liquidation discounts for afSUI/haSUI because they are expected to track SUI closely. That creates *depeg/correlation risk*: if SUI weakens sharply, or if an LST deviates from SUI, liquidations and bad-debt dynamics can worsen. Scallop also describes risk parameters that cap collateral concentrations by asset, which suggests active management of concentration risk, but the underlying solvency still depends on Sui-market liquidity during stress. I found *no verified evidence* in the gathered sources of direct bridge, custodian, CEX market-maker, or RWA-issuer/SPV dependency for Scallop Lend. Not verifiable as of 2026-08-29. The available sources also do not establish material stablecoin treasury custody, though the lending market clearly interacts with stablecoin-like collateral and pricing on Sui. Two important caveats: the protocol’s own docs present the multi-oracle design as a mitigation, but that is an *unverified marketing claim* absent independent on-chain validation here; and one third-party profile claims Scallop has had a security incident, but the exact scope and relevance to current counterparty risk are not verifiable from the gathered sources alone.

Scallop Lend’s custody is organized primarily through the protocol’s on-chain smart contracts on Sui, not by the protocol itself holding user assets. Suppliers deposit into asset pools and receive sCoins as proof of supply, while borrowers must create an Obligation to record collateral and debt; the docs state that pools and sCoins are autonomous blockchain-based smart contracts and that the original entity does not hold user assets in custody. For borrowing, collateral is stored inside the user’s Obligation object, and the Obligation Key is like a transferable NFT that represents ownership of that obligation. The architecture docs describe a Reserve embedded in Market that manages the underlying balances and the protocol’s asset accounting on-chain. In short, custody is *self-custodial at the user contract/object level* with assets and positions tracked in protocol-managed on-chain objects rather than by a centralized custodian.

Response reported by third-party coverage: Scallop froze the affected contract, said core contracts were secure, and stated that user deposits were not impacted. Reports also say operations resumed after the incident check and that the team promised to cover losses in full; some coverage also mentions an ongoing white-hat style negotiation for fund return.

Scallop Lend on Sui had a reported incident on 2026-04-26 involving a deprecated sSUI rewards/side contract; multiple reports describe it as a flash-loan or side-contract exploit that drained about 150,000 SUI, roughly $142,000 at the time. The affected area was the sSUI spool/rewards pool, while core lending contracts and user deposits were reported as unaffected.

Scallop Lend organizes key management around a capability-style ObligationKey tied to each user position on Sui. An Obligation is the shared on-chain object that stores a user’s collateral and debt, while the ObligationKey stays in the user’s wallet as an NFT-like proof of ownership and is required to mutate that obligation or borrow against it. Users can have multiple independent obligations, and each one has its own key; moving the key to another address transfers control of that obligation, but does not merge or share rights across obligations. In practice, this means Scallop separates *state* from *authority*: the obligation object can appear in transactions, but only the holder of the matching ObligationKey can authorize sensitive actions like borrowing or certain updates. The protocol also allows up to 5 sub-accounts per Sui address, enabling a single user to self-administer multiple isolated positions with separate collateral/debt tracking. For protocol-level administration, Scallop uses on-chain capability objects such as AdminCap, InterestModel/RiskModel capabilities, and shared Market/Reserve objects. According to the architecture docs, Market is shared for global protocol access, while AdminCap is transferred to the deployer to retain governance control over configuration and upgrades. Not verifiable as of 2026-08-30: whether additional off-chain or multisig key management is used for upgrades or treasury operations, because the provided sources only describe the on-chain capability model and user obligation keys.

Scallop Lend on Sui appears to use a multi-signature governed admin model rather than a single EOA, with the admin address holding both AdminCap and UpgradeCap per the protocol’s architectural documentation. The core risk posture is therefore *key-compromise / multi-sig compromise* rather than a publicly documented single-key backdoor; however, the exact on-chain admin address, proxy admin type, and any current timelock delay are not verifiable as of 2026-08-29 from the available evidence. Smart-contract / admin risk assessment

• Verification / architecture: Scallop’s public docs point to a Sui Move lending protocol with separate protocol versioning, upgrade flow, multi-signature governance, whitelist/access control, and emergency freeze controls. The versioning system explicitly pauses protocol operation when the deployed package version and on-chain Version object diverge, and normal operation resumes only after an admin calls upgrade(...) to sync them. That means upgrades are *controlled* and can temporarily freeze user actions by design.
• Upgradeability / proxy: The docs describe package upgrade plus version-object reconciliation, which is an upgradeable pattern, but I cannot verify a classic EVM proxy / ProxyAdmin layout on Sui, nor a Dune-decoded proxy-admin type, as of 2026-08-29. Not verifiable as of 2026-08-29.
• Roles / emergency powers: Documented admin capabilities include adding pause authority, whitelist management, and emergency protocol freeze; the emergency freeze is immediate and persists until governance reverses it. This creates a credible *freeze-risk* if authorized keys are compromised or if governance acts maliciously.
• Timelock / delays: A time-lock mechanism is documented for critical parameter changes via OneTimeLockValue, with changes created first and applied after a delay, but the current effective delay is described in the docs as disabled / set to 0, so there is no meaningful verified safety delay today.
• User exit: If the protocol is not frozen, users should be able to withdraw according to normal market rules; if an emergency freeze or version mismatch is active, user operations can be blocked. Whether users can *always* exit in worst-case admin compromise is Not verifiable as of 2026-08-29.
• Worst case: Compromised admin/upgrade keys could likely pause markets, whitelist/blacklist access, upgrade protocol logic, or trigger an indefinite freeze. I found no evidence of renounced admin roles; Not verifiable as of 2026-08-29. Architecture map (high level) Multi-sig Admin / UpgradeCap / AdminCap -> package upgrade + version sync -> protocol markets Multi-sig Admin / AdminCap -> pause authority / whitelist / emergency freeze Market + Version objects -> user operations allowed only when versions match Main finding: the dominant risk is *governance-controlled freeze/upgrade power*, not an ungoverned rug pattern; but without on-chain verification in this run, exact admin addresses, renouncement status, and current delay settings remain Not verifiable as of 2026-08-29.

Scallop appears to be led publicly by Kris Lai (Kriss), who presents himself as Founder/CEO on LinkedIn and is described in third-party profiles as the founder of Scallop and Scallop Pools. His self-reported background is in full-stack development, network security, crypto since 2017, and prior work on a Solana-based precursor called Scallop Pools before extending to Sui in 2022. Reality check: the team is only partially transparent. The public sources identify Kris Lai and one additional team figure, Joe Zhuang (CMO), while other personnel appear only as LinkedIn profiles without independent corroboration; there is no clearly verifiable full team roster in the sources provided. I found no independently verifiable evidence of a real office, legal entity structure, or whether operations are onshore/offshore; Not verifiable as of 2026-08-29. On credibility, the available evidence is mostly self-presentation plus platform directories and interviews, not hard operational proof. Kris claims hackathon wins and a Sui Foundation grant; LinkedIn also repeats awards and roles, but these remain weakly independent unless cross-checked against event or foundation records, which are not present here. I found no sourced evidence of prior hacks, criminal incidents, or adverse outcomes tied to the founders in the material provided; Not verifiable as of 2026-08-29. So the best read is: public founder-led project, partially doxxed, with some visible industry participation, but limited independently verified corporate transparency. That makes it look more like a real operating DeFi team than a pure web front, but the office/legal-structure question remains unverified.

Scallop Lend has a generally positive market reputation on Sui as a leading lending protocol, with third-party analytics describing it as the top lending protocol in the ecosystem and an institutional-grade money market. Its sentiment is mixed rather than cleanly bullish: the same risk analysis flags moderate risk from single-chain concentration and a younger-chain security environment. On founders and investors, public coverage says the protocol was initiated by Kris Lai in 2021, and that it completed a $3M strategic financing round with participation from THE CMS, 6MV, KuCoin Labs, Blockchain Founders Fund, and investment from the Sui Foundation. Those claims are reported in secondary sources, not directly in primary disclosures here. On audits, one profile states Scallop has not published audit reports, while another article claims it has undergone three security audits. These sources conflict, so the audit status is not fully verifiable from the available results. On criticisms and incident history, there is a documented April 2026 oracle-manipulation / flash-loan exploit affecting a deprecated V2 rewards contract, with losses reported around $42K and covered by the team; other summaries cite a related $142K-$150K incident figure. The existence of a security incident is therefore credible, but the exact loss amount is inconsistent across sources. I found no credible evidence in the provided results of fraud, rug-pull, insolvency, or sanctions allegations. Legal or regulatory actions were also not verifiable as of 2026-08-29. Unresolved concerns are mainly the protocol’s heavy dependence on Sui, oracle surface exposure, and inconsistent public reporting on audits and incident magnitude.

Scallop Lend on Sui is an over‑collateralized, pooled money‑market protocol: users supply assets to earn interest and borrow against collateral, with protocol revenue primarily from borrower interest and flash‑loan fees. Strategy & assets in/out

• Model is similar to Compound‑style lending: suppliers deposit assets into shared liquidity pools and receive interest‑bearing sCoins (Scallop Market Coins) representing claims on the pool.
• Borrowers post collateral and draw loans from these pools, with positions tracked via obligation structures in the on‑chain Move contracts.
• It supports standard Sui ecosystem tokens; per GitHub it is “an over collateralized lending protocol on SUI network.” Yield sources: organic vs subsidized
• Core yield is organic: variable interest paid by borrowers to suppliers based on per‑asset interest curves and utilization.
• The protocol additionally earns flash‑loan fees: 0.1% of the flash‑loan amount is allocated to the protocol as income.
• Some ecosystem campaigns (e.g., Sui Foundation funding and WAL/Binance wallet activities) have boosted growth, but those are external incentives, not the core rate engine. Risk profile: market‑neutral vs directional, leverage
• At protocol level, risk is mostly market‑neutral spread between borrow and supply rates; individual users can be directional via collateral choices.
• Architecture includes per‑asset risk models, supply/borrow limits, and interest curves, controlling leverage and asset‑level risk.
• Looping/leverage is mechanically possible (borrow same asset, re‑deposit), but risk parameters can cap this via LTV and borrow caps.
• External price exposure comes via oracle feeds integrated in the protocol’s three‑tier architecture. Lock‑ups, withdrawals, mechanics
• Deposits are non‑custodial and generally withdrawable at any time, subject to pool liquidity and health‑factor constraints.
• Protocol supports flash loans requiring same‑transaction repayment.
• Users can manage positions via up to 5 sub‑accounts per Sui address. Fees, gates, protocol revenue
• Revenue streams (per DeFiLlama and docs):
• Interest spread from borrowing activity.
• Liquidation‑related fees when under‑collateralized positions are liquidated.
• Flash‑loan fee of 0.1% to the protocol.
• DeFiLlama tracks “Fees” (interest and liquidation) and “Revenue” (share to treasury), confirming a treasury take‑rate model. Collateral model & risk controls
• Over‑collateralized: borrowers must maintain collateral above debt thresholds.
• Risk/interest models are configured off‑chain (TypeScript) and enforced on‑chain (Move), including LTVs, borrow caps, and fee parameters per asset. TVL, by chain, trend, APY history
• DeFiLlama shows Scallop Lend TVL ≈ $21.17m, 100% on Sui as of its latest update; older reports cited ~$130–146m TVL in March 2025, indicating a significant downtrend.
• Product is single‑chain (Sui) in DeFiLlama’s breakdown.
• APYs are variable, derived from utilization‑based interest curves; public data indicates high fee/revenue spikes (e.g., ~$79,920 revenue in 24h, March 2025), implying volatile but demand‑driven rates. On‑chain verification of exact current TVL, APY term structure, and per‑market utilization is Not verifiable as of 2026‑08‑30 under current constraints.

Not verifiable as of 2026-08-30. The available web sources identify Scallop Lend as a Sui lending protocol, but none of the retrieved results provide a verifiable reserve/treasury address list, custody setup, reserve policy, attestation, or on-chain balances. Third-party TVL pages only report aggregate protocol TVL, not treasury reserves. A GitHub architecture note describes an embedded Reserve object that manages underlying_balances, cash, debt, and revenue, which indicates how protocol accounting is structured, but it does not establish the actual treasury size or address-controlled balances. The protocol’s token-distribution claims mention a 5% liquidity reserve and 7% treasury allocation, but this is only a protocol-supplied or secondary summary claim and is not independently verified here. I could not confirm any custody signer, multisig, reserve wallet, or attestation from the retrieved sources.

Scallop Lend on Sui does not have a separate “Scallop Lend token”; it uses the Scallop protocol token SCA on Sui for ecosystem utility. On‑chain verification is not possible in this run: Not verifiable as of 2026‑08‑30. ### Native token

• Name / ticker: Scallop, SCA.
• Chain: Sui (SCA is a Sui ecosystem token; exact contract object ID on Sui is Not verifiable as of 2026‑08‑30).
• Scallop positions SCA as its native token for the Scallop DeFi suite (Lend, Swap, etc.), not a separate asset just for Lend. ### Supply, market cap, FDV
• Public trackers (CoinGecko/CMC style) show SCA as listed, but detailed figures (total vs circulating supply, market cap, FDV) specific to Sui deployment are Not verifiable as of 2026‑08‑30. ### Token utility & governance
• SCA is used for governance of Scallop protocol decisions and can be staked; it is also referenced as a rewards / incentive token in the ecosystem.
• Scallop Lend uses SCA for liquidity mining / incentive programs for lenders/borrowers on Sui; exact reward rates and emission curves are Not verifiable as of 2026‑08‑30. ### Revenue share, buybacks, burns, staking
• No independent evidence of direct revenue share, buybacks, or burn mechanisms tied to Scallop Lend cash flows.
• Staking rewards and protocol fee routing to SCA holders are discussed in high‑level marketing materials only → unverified marketing claim. ### Emissions & unlocks
• No independently confirmed emission schedule (vesting curve by tranche) for SCA dedicated to Scallop Lend.
• No reliable evidence that announced unlocks vs actual on‑chain movements can be checked without Dune/on‑chain tools → Not verifiable as of 2026‑08‑30. ### Allocations
• Generic categories (team, investors, community, ecosystem) are mentioned, but no audited breakdown with percentages is available from independent sources → unverified marketing claim. ### Holder concentration & control features
• Top‑holder concentration, insider wallets, and presence of mint, blacklist, or fee‑switch functions in the SCA Sui contract are Not verifiable as of 2026‑08‑30. ### Liquidity & listings
• SCA is tradable on Sui DEXs (e.g., Cetus, Turbos) and on at least one centralized exchange; depth and pair‑level liquidity on Sui are Not verifiable as of 2026‑08‑30. Key risk takeaway: current public data on SCA tokenomics for Scallop Lend on Sui is fragmented and largely marketing‑driven; critical items (contract controls, unlocks, holder concentration) cannot be validated without on‑chain access.

For Scallop Lend on Sui, a Bitcoin move below $10,000 would be a *severe collateral stress event* if the protocol has meaningful BTC-backed borrowing exposure, because an ~85%+ BTC drawdown would sharply increase borrower LTVs and likely force liquidations across undercollateralized positions. However, Scallop-specific on-chain exposure, liquidation thresholds, reserve buffers, and the share of its TVL tied to BTC collateral are Not verifiable as of 2026-08-30 in the sources provided, so the protocol’s actual loss path cannot be quantified from this run. What can be said from the stress-case literature is:

• BTC at $10,000 implies a crisis-grade collapse, not normal volatility, and would usually require systemic deleveraging and liquidity stress.
• In BTC-collateralized lending, such a price move typically pushes loans through margin-call zones and then into liquidation if borrowers do not add collateral fast enough.
• If liquidations are widespread, the main risks are forced-sale slippage, temporary insolvency of underwater positions, and operational strain on liquidators/oracles rather than BTC price discovery alone. For Scallop Lend specifically, the key unanswered items are which assets are used as collateral on Sui, how much BTC exposure exists, and where the liquidation thresholds sit. Those are Not verifiable as of 2026-08-30 from the available sources.

For Scallop Lend on Sui, a 20% depeg of the largest collateral asset would trigger liquidation only for positions whose safety margin no longer clears the protocol’s risk threshold; Scallop states that positions become liquidatable when risk level exceeds 100%, and that liquidation is soft (only the debt portion above the threshold is sold incrementally). What can be stated from the available sources:

• Scallop’s risk model uses asset-specific collateral factors and liquidation factors; for example, the docs list SUI at 85% collateral factor and 90% liquidation factor, with other assets such as afSUI, haSUI, and vSUI having different parameters.
• Because liquidation is triggered by the post-depeg collateral value relative to debt, a 20% price drop in the largest collateral asset can be translated into a proportional reduction in collateral value, but the actual protocol impact depends on live exposure, borrower leverage, and the current collateral mix.
• The exact amount of accounts that would become liquidatable, the liquidation volume, and any loss to lenders are Not verifiable as of 2026-08-29 from the provided web sources alone. Operational implication:
• If the largest collateral asset is, for example, SUI, a 20% depeg would move its value to 80% of par, which is below the 85% collateral factor and also below the 90% liquidation factor shown in Scallop’s model; positions using that asset near max borrow would therefore be the first stressed.
• Scallop’s documented soft liquidation design means the protocol attempts to restore health by liquidating only the minimum necessary collateral rather than fully closing the position. A precise stress number for the protocol-wide exposure requires current on-chain balances and debt distributions, which are Not verifiable as of 2026-08-29 in this run.

For Scallop Lend on Sui, an insolvency-style stress event is not described as a separate counterparty-default waterfall; the documented loss path is borrower insolvency / undercollateralization, which triggers soft liquidation rather than protocol-wide loss mutualization. If the *top counterparty* means the largest borrower or the most exposed account, the expected loss path is: collateral value falls or debt value rises, the position’s risk level reaches 100%+, and liquidators repay only the portion needed to restore health. The loss is absorbed first by the borrower’s collateral, not by other users; the protocol’s liquidation penalty is split between the liquidator’s reward and the protocol reserve. The docs do not describe any explicit insurance fund, default fund, or mutualized backstop that would compensate lenders for a borrower default, so compensation to lenders is not verifiable as of 2026-08-29. The impact path through the smart contracts is: oracle update (Pyth/Supra via X-Oracle) feeds new prices into borrow/withdraw/liquidation checks; if health falls below threshold, the liquidation flow is enabled; liquidators execute partial repayment and collateral sale; the position is rechecked until it returns to healthy status. Scallop states liquidation is incremental and stops once the account is healthy again, so the protocol aims to prevent full-collateral seizure in ordinary liquidation events. If the question instead means insolvency of a *third-party protocol counterparty* (not a borrower), that specific default path is Not verifiable as of 2026-08-29 from the available sources.

For a committed fraud by the DAO or owners stress scenario, I found no verifiable evidence that Scallop’s DAO or owners committed fraud. The available sources describe a smart-contract exploit against a deprecated side contract, not insider fraud or deliberate misappropriation by the protocol’s controllers. What is verifiable is that Scallop publicly said the incident affected a side/deprecated rewards contract related to the sSUI spool rewards pool, while core lending operations and user deposits were reported as unaffected. Independent reporting also describes the loss as an exploit involving flash-loan/oracle manipulation and an uninitialized variable, not a governance or owner-driven theft. There is also evidence that Scallop’s bug-bounty scope treats direct theft from user funds or treasury as critical, which is consistent with a protocol concerned about such risks, but this does not establish that fraud occurred. So the appropriate risk classification is: Not verifiable as of 2026-08-30 for committed fraud by the DAO or owners. The documented incident is better categorized as technical exploit / contract vulnerability, not proven fraud by insiders.

Scallop Lend’s documented yield risks are tied to oracle pricing and liquidation mechanics, not to a disclosed “primary yield source” that can be independently stress-tested as negative over 30 days. Scallop states that it uses Pyth, Switchboard, and Supra oracles, and that incorrect prices or manipulation can trigger wrongful liquidations; it also says an Insurance Fund is intended to protect against unforeseen losses from untimely liquidations and oracle issues. The project’s GitHub describes Scallop as an over-collateralized lending protocol on Sui, which supports the view that borrower interest is the main economic source of lender yield, but the repository does not provide a 30-day yield series or a breakdown showing whether any primary source turned negative. Because no credible 30-day negative-yield evidence was provided in the search results, the stress finding is: Not verifiable as of 2026-08-29. If you want a formal stress note, the defensible interpretation is a *market/liquidation stress* scenario rather than a negative yield-source scenario, since the available materials discuss oracle and liquidation risk rather than yield negativity.

Scallop Lend on Sui has highly centralized governance, with core contracts and operations controlled by the core team and their entities; there is no evidence of a mature, on‑chain lending DAO comparable to major Ethereum protocols. Because Dune/on‑chain is unavailable in this run, all on‑chain governance aspects (voting power concentration, exact admin roles, multisig composition, timelocks) are: Not verifiable as of 2026‑08‑30. ### Control of development, contracts, frontend, funds

• Core team / company control: Public documentation and external overviews describe Scallop as a DeFi money market built on Sui, led by a founding team and backed by investors, with no evidence of token‑holder‑controlled protocol governance comparable to Compound/Aave.
• Admin / upgrade authority: External protocol descriptions indicate contracts use admin roles controlled by the team (or a team‑controlled multisig); there is no clear documentation of these roles being delegated to a community DAO.
• Frontend & infrastructure: The primary app frontend (Scallop Lend dApp) is operated via Scallop’s official domain and infra controlled by the project team; no independent community frontends are documented.
• Funds / reserves: Risk/TVL dashboards show protocol reserves and user deposits held in the smart contracts; ultimate control over parameters and upgrades lies with the team, given the absence of a formalized governance module. ### Governance / DAO structure
• DAO status: There is no evidence of a functioning on‑chain governance system (governance token with proposals, votes, and execution) for Scallop Lend on Sui in external analytics or governance aggregators.
• Proposal process: No formal proposal framework (e.g., governance forum, SIP process, on‑chain proposal contracts) is documented outside the project’s own materials. Any governance‑like process appears to be de facto, via team decisions.
• Voting concentration & top holders: Not verifiable as of 2026‑08‑30. ### Timelock / multisig structure
• Timelock: No independent confirmation of timelock contracts or enforced upgrade delays for Scallop Lend.
• Multisig signers & threshold: Not verifiable as of 2026‑08‑30. ### Legal entity / ToS
• Company control & jurisdiction: Third‑party listings describe Scallop as a project with a core company/team but do not provide a verified legal entity name, jurisdiction, or registration number. These are therefore Not verifiable as of 2026‑08‑30.
• Terms of Service: Any ToS or user agreement appears to be hosted only on Scallop’s own website; absent independent verification, all such claims are unverified marketing claims.

Scallop Lend is a lending protocol on Sui, integrated into the broader Scallop ecosystem (which also offers a CeFi-style exchange and card product). On-chain verification is not possible in this run: Not verifiable as of 2026-08-30. 1. Entity, jurisdiction, and legal structure Open web information indicates Scallop operates via Scallop Group entities with a CeFi arm licensed in Lithuania (EMI/virtual asset service provider) and/or other EU jurisdictions, but Scallop Lend on Sui is positioned as a DeFi protocol rather than a regulated deposit-taker or broker-dealer. There is no clear, independently confirmed corporate entity that is legally responsible *specifically* for Scallop Lend smart contracts on Sui; governance appears more “project team–driven” than DAO-based. 2. Terms of Service, user restrictions Scallop’s general platform ToS (for CeFi products) references jurisdictional restrictions (e.g., prohibitions on sanctioned countries and possibly U.S. persons), and reserves rights to block access where local law requires. There is no independently archived, protocol-specific Scallop Lend ToS for Sui; front-end access terms and exact geo-blocking policy for Scallop Lend are Not verifiable as of 2026-08-30. 3. KYC / AML posture The CeFi exchange / card side of Scallop requires full KYC and claims AML compliance under EU rules (as a VASP/EMI partner). For Scallop Lend on Sui, there is no evidence of on-chain KYC or permissioned pools; likely pseudonymous, permissionless access via wallet with no KYC at the protocol layer, though front-end access could be IP- or account-gated. This is an inference based on typical DeFi design and available descriptions, not direct protocol documentation. 4. Regulatory classification and disclosures Public materials frame Scallop Lend as a non-custodial lending/borrowing protocol, not as a bank, securities broker, or investment fund. There is no regulator-issued classification (e.g., from EU/ESMA, UK FCA, MAS) specifically addressing Scallop Lend on Sui. Not verifiable as of 2026-08-30. 5. Warnings, enforcement, sanctions, litigation Searches show no official enforcement actions, sanctions listings, or court cases naming Scallop Lend or its core entities from major regulators (OFAC, EU, UK, U.S. SEC/CFTC) or public court databases. Not verifiable as of 2026-08-30. 6. Data protection / privacy Scallop’s CeFi web platform provides a standard GDPR-style privacy policy (data controller role, user rights to access/erasure, etc.). There is no separate privacy policy for Scallop Lend’s Sui front end; how wallet metadata, IPs, and analytics are processed for DeFi users is Not verifiable as of 2026-08-30. Key risk takeaway: legal responsibility for Scallop Lend smart-contract risk on Sui is structurally separated from any regulated CeFi entity, with unclear recourse, no clear investor-protection regime, and unknown enforceability of ToS for DeFi users.

Not verifiable as of 2026-08-29. The provided search results do not identify which stablecoin Scallop Lend used on Sui, and none give protocol-specific on-chain evidence for Scallop Lend’s collateral/stablecoin history. The only solid conclusion from these results is that *stablecoins in general* have depegged multiple times across the market, but that does not answer whether the stablecoin used by Scallop Lend depegged, how many times, or the last depeg magnitude. If you want, I can help narrow this down by checking Scallop Lend’s docs, markets, and historical product pages for the exact stablecoin name, then assess any public depeg history from independent sources.

Top risks for Scallop Lend on Sui are: (1) Oracle / liquidation risk — Scallop relies on Pyth, Switchboard, and Supra, and its own docs say correlated oracle failures can still produce wrong prices and wrongful liquidations. (2) Smart contract / legacy-contract risk — the protocol’s docs acknowledge ongoing development and changing code, while independent coverage reports a 2026 exploit that hit a deprecated rewards contract rather than core lending logic, showing old modules can remain attack surface. (3) Chain concentration risk — Scallop is Sui-native and heavily exposed to Sui ecosystem, liquidity, and network risk; third-party risk analyses flag single-ecosystem concentration as a major concern. (4) Liquidation / market volatility risk — as an over-collateralized lender, sharp collateral moves can trigger forced liquidations and bad debt if market liquidity is thin. (5) Operational / regulatory risk — the docs explicitly note insufficient information disclosure, evolving design, and unclear or unsettled regulatory status in many jurisdictions.

Scallop Lend’s main strengths are its Sui-native design, institutional-grade risk framework, capital-efficient lending mechanics, composability, and security-oriented architecture. In practice, that means the protocol is built specifically for Sui’s fast, low-cost, parallel execution environment, which is a structural advantage for lending and liquidation-heavy DeFi workflows. Top 5 strengths:

• Sui-native performance fit: Scallop is purpose-built for Sui, and third-party profiles describe Sui’s high throughput and low latency as a direct enabler for Scallop’s lending experience.
• Institutional-grade risk controls: Multiple sources describe Scallop as emphasizing professional-grade risk management, including collateral/borrow weight controls, collateral segregation, and liquidation protections.
• Capital efficiency and advanced lending design: Scallop uses a trilinear interest-rate model and market mechanisms intended to improve utilization and borrowing incentives, which supports more efficient lending markets.
• Composability across Sui DeFi: Scallop’s sCoins and related primitives are described as composable across other Sui applications, making the protocol more useful as infrastructure rather than a standalone app.
• Security emphasis: Public descriptions highlight Sui Move’s asset model, multi-oracle risk mitigation, and external audits as part of Scallop’s security posture. A useful caution: several of these claims come from protocol-adjacent or aggregator sources rather than on-chain verification, so they should be treated as *documented positioning* rather than independently verified performance outcomes.